From: Al Petrofsky <al@petrofsky.org>
Cc: emacs-devel@gnu.org
Subject: Re: Changes to make the C-x @ commands work with function keys
Date: Tue, 12 Feb 2002 09:56:51 -0800 [thread overview]
Message-ID: <200202121756.JAA08706@radish.petrofsky.org> (raw)
In-Reply-To: <Pine.SUN.3.91.1020212104343.4485I-100000@is> (message from Eli Zaretskii on Tue, 12 Feb 2002 10:44:22 +0200 (IST))
> From: Eli Zaretskii <eliz@is.elta.co.il>
> On Mon, 11 Feb 2002, Al Petrofsky wrote:
>
> > Below are some changes that make the C-x @ commands work with function
> > keys.
>
> Sorry, I don't understand: this seems to work already. For example,
> "C-x @ c <right>" invokes <C-right>. What am i missing?
You must be running on a window system, where pressing right generates
a single <right> event. On a tty, pressing right generates something
like ESC O C. In 21.1, the C-x @ sequences modify just the single
event that follows (i.e. ESC), rather than modifying the translated
event that would follow after function-key-map processing.
> (Btw, I always wondered how can this be useful for the Ctrl modifier,
> since "C-x" requires Ctrl at least with `x'. Is there an assumption
> that the user can arrange for some key to generate "C-x", but cannot
> use Ctrl otherwise?)
Yes. An uncustomized tty will generate C-x when you type C-x, but
will not generate C-right when you type C-right. Termcap/terminfo
don't even provide a way to state what the byte sequence for C-right
would be. With the changes I proposed, the user can at least make a
private arrangement between his tty and emacs.
-al
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-02-12 17:56 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-02-12 1:38 Changes to make the C-x @ commands work with function keys Al Petrofsky
2002-02-12 8:44 ` Eli Zaretskii
2002-02-12 16:40 ` Stefan Monnier
2002-02-12 17:56 ` Al Petrofsky [this message]
2002-02-13 6:11 ` Eli Zaretskii
2002-02-13 15:39 ` Richard Stallman
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=200202121756.JAA08706@radish.petrofsky.org \
--to=al@petrofsky.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).