From: Hikaru Ichijyo <ichijyo@macross.sdf.jp>
To: help-gnu-emacs@gnu.org
Subject: Re: Which key combos are not possible in remote Emacs session because terminal interferes?
Date: Sun, 08 Feb 2015 20:20:24 -0600 [thread overview]
Message-ID: <8xxh9uvesgn.fsf@village.keycorner.org> (raw)
In-Reply-To: mailman.19501.1423361792.1147.help-gnu-emacs@gnu.org
Bob Proulx <bob@proulx.com> writes:
> When using a local graphical interface every key press and release is
> individually available for use. Therefore any combination is
> possible.
Yes, true. On Linux/X11/x86, I'm able to get "Super" from the Windows
key. This seems to be already preconfigured, as I didn't have to do
anything to get that behavior. My convenience key bindings that I've
setup with the Super key are only available when I'm in X though because
of the behavior your describing.
[...]
> At one time the meta key set the "high" bit. ASCII is a 7-bit
> encoding leaving the 8th bit available to be set. This now conflicts
> with use of UTF-8 unicode and AFAIK this is no longer used anywhere by
> anyone who cares about UTF-8 due to this. I do not miss it.
>
> Most terminals now encode the meta key as an escape sequence sending
> the ESC character followed by the desired character. M-w for example
> (holding down Alt on a US-PC keyboard and pressing w) will be encoded
> as an ESC w two character sequence. This often needs explicit
> configuration. XTerm for example needs this resource set explicitly
> or it will instend send the 8-bit value yielding different results.
>
> XTerm*metaSendsEscape:true
>
> Some people undoubtedly like the 8-bit Alt key behavior. For example
> it allows typing in many glyphs using the Alt key instead of the
> Compose or AltGr keys using the international input methods. It is a
> personal preference but I prefer to have a working meta key for emacs
> and I can enter the non-ascii characters using the Compose key.
I've found that on Linux, (unlike the Super/Windows key), use of
Alt/Meta over SSH works transparently and as expected both in xterm
windows and on the VTY console. I don't know which mechanism they're
using to achieve that, "high-bit" or sending an ESC first, but it works,
and I like it. I didn't have to do anything myself to configure it to
act this way.
> Without a working meta key they would send all M- sequences by sending
> ESC explicitly first. ESC w is the same to emacs as M-w. Any C-M-
> something or M-C- something sequences will be ESC followed by the C-
> something character. For example C-M-r would be ESC C-r.
I remember the bad old days of having to do that in a terminal program
while connected by dialup modem to a machine that had Emacs on the
site end. Escape-this, Escape-that...Escape play a D-minor seventh
diminished guitar chord while holding down the right pedal and humming a
traditional Nepalese song and waving your arms. Having a real Meta key
that works over remote session is nicer. :)
--
He that would make his own liberty secure must guard even his enemy from
oppression; for if he violates this duty, he establishes a precedent
that will reach to himself.
--Thomas Paine
next prev parent reply other threads:[~2015-02-09 2:20 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-07 7:48 Which key combos are not possible in remote Emacs session because terminal interferes? Chris Seberino
2015-02-07 8:15 ` Eli Zaretskii
2015-02-08 2:16 ` Bob Proulx
2015-02-08 18:04 ` Philipp Stephani
[not found] ` <mailman.19501.1423361792.1147.help-gnu-emacs@gnu.org>
2015-02-09 2:20 ` Hikaru Ichijyo [this message]
2015-02-09 4:12 ` Chris Seberino
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=8xxh9uvesgn.fsf@village.keycorner.org \
--to=ichijyo@macross.sdf.jp \
--cc=help-gnu-emacs@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.
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).