From: Stefan Monnier <monnier@iro.umontreal.ca>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Input for TTY menus
Date: Thu, 19 Sep 2013 15:21:17 -0400 [thread overview]
Message-ID: <jwvsix0hbbf.fsf-monnier+emacs@gnu.org> (raw)
In-Reply-To: <83vc1wlsp3.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 19 Sep 2013 18:47:04 +0300")
>> read_char won't handle the arrow keys. To handle the arrow keys you
>> need to use read_key_sequence
> Thanks. This means I'll probably need to clone some small subset of
> the code in command_loop_1 after it calls read_key_sequence, in order
> to process the key sequence, right?
I don't think there's much to do there, but clearly you'll want to do
something with the sequence, indeed. Although you might like to simply
setup your keymaps in such a way that you can just use
read_key_sequence_cmd (which should usually be the same as (key-binding
<keys>), except when the keymaps are dynamic and might change between
the time they were read by read_key_sequence and the call to
key-binding) to know what operation to perform.
>> (probably after setting up some overriding-terminal-local-map).
> What would be the purpose of overriding-terminal-local-map in this
> case?
The key sequences read by read_key_sequence depend on the currently
active keymaps to decide when a key sequence is complete (i.e. when to
stop reading subsequent events).
Stefan
next prev parent reply other threads:[~2013-09-19 19:21 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-09-19 13:38 Input for TTY menus Eli Zaretskii
2013-09-19 13:52 ` Masatake YAMATO
2013-09-19 14:33 ` Stefan Monnier
2013-09-19 15:47 ` Eli Zaretskii
2013-09-19 19:21 ` Stefan Monnier [this message]
2013-09-23 13:18 ` Eli Zaretskii
2013-09-23 14:43 ` Stefan Monnier
2013-09-21 14:56 ` Eli Zaretskii
2013-10-17 5:34 ` Darren Hoo
2013-10-17 15:49 ` Eli Zaretskii
2013-10-18 4:55 ` Darren Hoo
2013-10-18 6:49 ` Eli Zaretskii
2013-10-18 7:37 ` Darren Hoo
2013-10-18 9:13 ` Eli Zaretskii
2013-10-18 10:39 ` Darren Hoo
2013-10-18 13:38 ` Eli Zaretskii
2013-10-18 13:40 ` Eli Zaretskii
2013-10-19 18:38 ` Darren Hoo
2013-10-19 18:58 ` Darren Hoo
2013-10-19 19:07 ` Darren Hoo
2013-10-20 9:32 ` Jan Djärv
2013-10-18 14:11 ` Eli Zaretskii
2013-10-18 15:12 ` Stefan Monnier
2013-10-18 15:28 ` Eli Zaretskii
2013-10-18 18:17 ` Stefan Monnier
2013-10-19 8:40 ` Eli Zaretskii
2013-10-19 13:45 ` Stefan Monnier
2013-10-18 17:41 ` chad
2013-10-18 17:43 ` chad
2013-10-18 18:14 ` Eli Zaretskii
2013-10-18 19:26 ` Jan Djärv
2013-10-18 20:04 ` Stefan Monnier
2013-10-19 7:35 ` Eli Zaretskii
2013-10-19 9:43 ` Eli Zaretskii
2013-10-19 13:40 ` Stefan Monnier
2013-10-19 14:45 ` Eli Zaretskii
2013-10-19 15:25 ` Stefan Monnier
2013-10-19 16:32 ` Eli Zaretskii
2013-10-19 8:58 ` Jan Djärv
2013-10-19 9:01 ` Eli Zaretskii
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=jwvsix0hbbf.fsf-monnier+emacs@gnu.org \
--to=monnier@iro.umontreal.ca \
--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).