[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#44466: 27.1; quail input fails at read-only boundary
From: |
Eli Zaretskii |
Subject: |
bug#44466: 27.1; quail input fails at read-only boundary |
Date: |
Sun, 08 Nov 2020 05:29:12 +0200 |
> From: Evgeny Zajcev <lg.zevlg@gmail.com>
> Date: Sun, 8 Nov 2020 01:24:26 +0300
> Cc: dick <dick.r.chiang@gmail.com>, 44466@debbugs.gnu.org
>
> What I want with that patch is that if some key is pressed on read-only area
> in non-read-only buffer, then
> quail should do what it does as if buffer marked as read only, i.e. no input
> method translations are done, and
> all single char bindings continue to work.
When an input method is used in a read-only buffer, Emacs barfs
because it doesn't allow inserting text into such a buffer. It
doesn't insert the untranslated character, as what your patch did.
> Possible we need to check front-stickyness of the char at point along with
> 'read-only property:
>
> ..
> (and (get-char-property (point) 'read-only)
> (get-char-property (point) 'front-sticky)))
Does this solve the problem in this case?
- bug#44466: 27.1; quail input fails at read-only boundary, dick, 2020/11/05
- bug#44466: 27.1; quail input fails at read-only boundary, Eli Zaretskii, 2020/11/07
- bug#44466: 27.1; quail input fails at read-only boundary, Evgeny Zajcev, 2020/11/07
- bug#44466: 27.1; quail input fails at read-only boundary,
Eli Zaretskii <=
- bug#44466: 27.1; quail input fails at read-only boundary, Evgeny Zajcev, 2020/11/08
- bug#44466: 27.1; quail input fails at read-only boundary, Eli Zaretskii, 2020/11/08
- bug#44466: 27.1; quail input fails at read-only boundary, lg . zevlg, 2020/11/08
- bug#44466: 27.1; quail input fails at read-only boundary, Eli Zaretskii, 2020/11/08
- bug#44466: 27.1; quail input fails at read-only boundary, lg . zevlg, 2020/11/08
- bug#44466: 27.1; quail input fails at read-only boundary, Eli Zaretskii, 2020/11/14