From: Stefan Monnier <monnier@iro.umontreal.ca>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: emacs-devel@gnu.org
Subject: Re: Non-ASCII chars in quail rules
Date: Sun, 31 Aug 2014 08:38:24 -0400 [thread overview]
Message-ID: <jwvd2bg4z19.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <20140830184844.797d7340@jabberwock.cb.piermont.com> (Perry E. Metzger's message of "Sat, 30 Aug 2014 18:48:44 -0400")
> (Indeed, input-method-function seems to be restricted to passing along
> information about printable ASCII (or at least, it documents itself
> as only dealing with octal 040 to 0176), and directly via
> read-char/read-event.)
There's no doubt that it won't work for function keys under a tty
(where those function keys are transmitted as "escape sequences", which
Emacs translated back into "function key" via input-decode-map which
happens *after* input decoding).
Maybe it could be made to work for that case as well, but for now
I think we should focus on the GUI case, where those problems
shouldn't appear.
> I think I'll dig at it for a while longer.
Do you have a recipe to reproduce your current problem?
Stefan
next prev parent reply other threads:[~2014-08-31 12:38 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-08-29 14:18 Non-ASCII chars in quail rules Perry E. Metzger
2014-08-30 1:13 ` Stefan Monnier
2014-08-30 22:48 ` Perry E. Metzger
2014-08-31 12:38 ` Stefan Monnier [this message]
2014-08-31 14:00 ` Perry E. Metzger
2014-08-31 21:29 ` Perry E. Metzger
2014-09-03 2:23 ` Stefan Monnier
2014-09-03 11:43 ` Perry E. Metzger
2014-09-03 13:19 ` Stefan Monnier
2014-09-03 21:59 ` Perry E. Metzger
2014-09-04 0:02 ` Stephen J. Turnbull
2014-09-04 13:57 ` Perry E. Metzger
2014-09-04 14:17 ` Stephen J. Turnbull
2014-09-04 15:20 ` Perry E. Metzger
2014-09-04 15:37 ` Eli Zaretskii
2014-09-04 22:52 ` Stephen J. Turnbull
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=jwvd2bg4z19.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.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 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.