unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Perry E. Metzger" <perry@piermont.com>
To: Juri Linkov <juri@linkov.net>, Yuri Khan <yuri.v.khan@gmail.com>
Cc: Emacs developers <emacs-devel@gnu.org>
Subject: Re: not quite understanding input methods
Date: Wed, 1 Sep 2021 08:58:46 -0400	[thread overview]
Message-ID: <348756cf-6924-b390-01f5-9541ac56ca92@piermont.com> (raw)
In-Reply-To: <871r686abe.fsf@mail.linkov.net>

On 9/1/21 03:23, Juri Linkov wrote:

> Emacs 28 has the input method "Compose" corresponding to XKB's Compose
> in leim/quail/compose.el, but many useful key sequences in this
> input method don't work because of the artificial limitation
> to ASCII-only chars in read_char.
>
I've been looking at this a bit. If you simply lift the limitation in 
read_char everything downstream fails. It appears that the limitation is 
partially caused by the fact that quail.el expects to be able to create 
dense keymaps of size limited to 255, though that might not be the only 
problem.  Note that fixing this won't be overly difficult, but it would 
need to be fixed in anything that can supply a `input-method-function` 
that is hooked by read_char.

(BTW, as a pure aside: why aren't keymaps hash tables? Is that purely 
historical?)

(FYI, I fear that after the last few days of reading I may be the expert 
on how all of this works, which is terrifying because I feel completely 
lost in the code. It's a maze. It's pretty rare that I see a part of 
Emacs that I feel should be nuked from orbit, but the input subsystem 
feels that way; a rewrite would be required to make it actually 
comprehensible, but a rewrite would also break enormous amounts of stuff 
that people depend on.)


Perry





  parent reply	other threads:[~2021-09-01 12:58 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
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 [this message]
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=348756cf-6924-b390-01f5-9541ac56ca92@piermont.com \
    --to=perry@piermont.com \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    --cc=yuri.v.khan@gmail.com \
    /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).