From: Visuwesh <visuweshm@gmail.com>
To: James Thomas <jimjoe@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: Questions about Quail
Date: Sat, 23 Jul 2022 17:49:42 +0530 [thread overview]
Message-ID: <87zgh0aun5.fsf@gmail.com> (raw)
In-Reply-To: <87r12c83ea.fsf@gmx.net> (James Thomas's message of "Sat, 23 Jul 2022 17:08:53 +0530")
[சனி ஜூலை 23, 2022] James Thomas wrote:
>> The ibus input method does not care about the character before point, it
>> only checks the keystrokes hmm... I will wait for user feedback™ to
>> decide which is better.
>>
>>> In that web keyboard, try typing hj (கப) then backspace (க) and type h
>>> again: you will get க்க.
>>
>> I.e., whilst you get க்க in my input method, you get கக in the ibus
>> one.
>
> Hmm. One possible solution (albeit a bit complicated), to get the
> non-ibus behaviour, is to use the update-translation-function to never
> end a translation that reaches up to the last 2 input characters: ie
> keep the input pending (unless the last one is not any of the valid
> input characters), and programatically insert the translation of any
> remaining input character beyond the control-flag.
>
> But that would work for only one level of backspace. If you have a
> simpler implementation with the use of state (or checking the character
> before point directly?) that might be better.
Yep, checking the character before point is the easiest solution. I
tried to keep track of the last character inputted but that quickly got
hairy and unnecessarily complicated. The current update-translation-function
checks the character before point and the key that was pressed to set
the quail-current-string appropriately.
next prev parent reply other threads:[~2022-07-23 12:19 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-07-17 4:56 Questions about Quail Visuwesh
2022-07-17 6:43 ` Visuwesh
2022-07-23 4:21 ` James Thomas
2022-07-23 7:31 ` Visuwesh
2022-07-23 7:55 ` James Thomas
2022-07-23 8:21 ` Visuwesh
2022-07-23 8:38 ` Visuwesh
2022-07-23 9:02 ` Visuwesh
2022-07-23 11:38 ` James Thomas
2022-07-23 12:19 ` Visuwesh [this message]
2022-07-23 13:29 ` James Thomas
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zgh0aun5.fsf@gmail.com \
--to=visuweshm@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=jimjoe@gmx.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).