unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: not quite understanding input methods
Date: Mon, 30 Aug 2021 15:13:25 -0400	[thread overview]
Message-ID: <94711961-81b0-dc21-dca0-d92726a7428f@piermont.com> (raw)
In-Reply-To: <838s0ikawo.fsf@gnu.org>


On 8/30/21 15:08, Eli Zaretskii wrote:
>> Date: Mon, 30 Aug 2021 15:00:21 -0400
>> From: "Perry E. Metzger" <perry@piermont.com>
>>
>> Having thought about this, is `read_char` actually going to be called
>> under these circumstances? Remember that I've bound "<f19>" to a
>> function that inserts a character into the buffer, and it is that
>> character in the buffer that is in the quail rule. I may be confused
>> about how all of this works, of course.
> Before a key sequence bound to a command causes that command to be
> invoked, it (the key sequence) must be read, and that's the job of
> read_char.  Only after F19 is read, Emacs calls the command to which
> you bound it, and that command inserts a character into the buffer.
>
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.


Perry





  reply	other threads:[~2021-08-30 19:13 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 [this message]
2021-08-30 19:19               ` Stefan Monnier
2021-08-30 19:26                 ` Perry E. Metzger
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

  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=94711961-81b0-dc21-dca0-d92726a7428f@piermont.com \
    --to=perry@piermont.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    /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).