From: "Perry E. Metzger" <perry@piermont.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: not quite understanding input methods
Date: Mon, 30 Aug 2021 15:26:56 -0400 [thread overview]
Message-ID: <5dc8bffc-a4d9-96e3-c05d-e6b0e52708c0@piermont.com> (raw)
In-Reply-To: <jwvv93mbv4q.fsf-monnier+emacs@gnu.org>
On 8/30/21 15:19, Stefan Monnier wrote:
>> Yes, but the point at which the character that's inserted into the buffer is
>> present is after the Quail input method was invoked by read_char. Again, I'm
>> finding the stack of things involved in the input method getting invoked
>> rather difficult to follow, but it feels like Quail doesn't actually look
>> backwards in the buffer and thus could care less that I inserted
>> a particular character there. That said, I don't truly get how all this
>> works yet, there's no documentation and a heap of twisty code involved.
> There might be multiple obstacles involved (e.g. multiple places that
> assumes the chars are all <127), so it'll be important to test things
> bit by bit. E.g. check that with no patch the `input-method-function`
> is not called at all when you press F19, then check that with
> your patch `input-method-function` *is* called when you press F19.
>
> Once that is done, the rest of the hacking should all be doable at the
> Lisp level, but it may involve tracing through the quail code, indeed.
The fact that `read_char` is a 1300 line function all on its own doesn't
make it particularly easy to tease apart the logic. :( :( :(
Perry
next prev parent reply other threads:[~2021-08-30 19:26 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-30 17:24 not quite understanding input methods Perry E. Metzger
2021-08-30 17:37 ` Stefan Monnier
2021-08-30 17:45 ` Perry E. Metzger
2021-08-30 18:00 ` Stefan Monnier
2021-08-30 18:22 ` Eli Zaretskii
2021-08-30 18:34 ` Perry E. Metzger
2021-08-30 18:39 ` Eli Zaretskii
2021-08-30 18:43 ` Perry E. Metzger
2021-08-30 18:37 ` Perry E. Metzger
2021-08-30 19:00 ` Perry E. Metzger
2021-08-30 19:08 ` Eli Zaretskii
2021-08-30 19:13 ` Perry E. Metzger
2021-08-30 19:19 ` Stefan Monnier
2021-08-30 19:26 ` Perry E. Metzger [this message]
2021-08-30 19:31 ` Eli Zaretskii
2021-08-30 20:12 ` Stefan Monnier
2021-08-30 19:28 ` Eli Zaretskii
2021-08-30 20:29 ` André A. Gomes
2021-09-01 5:44 ` Yuri Khan
2021-09-01 7:23 ` Juri Linkov
2021-09-01 7:43 ` Yuri Khan
2021-09-01 8:37 ` tomas
2021-09-01 9:14 ` Joost Kremers
2021-09-01 13:17 ` Perry E. Metzger
2021-09-01 12:05 ` Eli Zaretskii
2021-09-01 12:35 ` João Távora
2021-09-01 13:19 ` André A. Gomes
2021-09-01 14:05 ` João Távora
2021-09-01 13:03 ` André A. Gomes
2021-09-01 13:02 ` Perry E. Metzger
2021-09-02 12:00 ` Maxim Nikulin
2021-09-02 13:03 ` Filipp Gunbin
2021-09-01 12:58 ` Perry E. Metzger
2021-09-01 12:51 ` Perry E. Metzger
2021-09-01 13:29 ` Partially answering my own question (was Re: not quite understanding input methods) Perry E. Metzger
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=5dc8bffc-a4d9-96e3-c05d-e6b0e52708c0@piermont.com \
--to=perry@piermont.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.