From: Eli Zaretskii <eliz@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: ESC vs Meta for shifted keys
Date: Thu, 12 Apr 2018 14:31:36 +0300 [thread overview]
Message-ID: <834lkg3bl3.fsf@gnu.org> (raw)
In-Reply-To: <cd48f916-f376-43bf-b173-79caff49f9dd@default> (message from Drew Adams on Wed, 11 Apr 2018 14:58:23 -0700 (PDT))
> Date: Wed, 11 Apr 2018 14:58:23 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
>
> > I think it's just a bug: when left-word and right-word were introduced
> > only one pair of bindings was updated and not the other.
>
> I'm not sure it's a bug. My guess is that it was by design
> (for whatever reason). Perhaps Eli or someone else can
> enlighten us.
>
> I kinda doubt it was an oversight. All of those bindings
> are together, and the person who changed the Meta bindings
> likely searched for `forward-word', not "[M-right]" or
> "(kbd "M-<right>")"...
I don't remember why I bypassed ESC <right> etc. Maybe I wanted to
change as few bindings as possible. Maybe I thought users of R2L
script are unlikely to invoke these commands via ESC. Maybe I just
made a mistake.
If someone is annoyed by the difference (which should only be visible
in bidirectional text), feel free to make ESC do the same as Meta in
this case.
next prev parent reply other threads:[~2018-04-12 11:31 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-10 13:28 ESC vs Meta for shifted keys Robert Pluim
2018-04-10 13:42 ` Stefan Monnier
2018-04-10 13:57 ` Robert Pluim
2018-04-10 23:11 ` Bob Proulx
2018-04-11 12:34 ` Stefan Monnier
2018-04-11 19:54 ` Bob Proulx
2018-04-11 21:10 ` Stefan Monnier
2018-04-11 21:58 ` Drew Adams
2018-04-12 8:49 ` Robert Pluim
2018-04-12 14:52 ` Drew Adams
2018-04-12 14:57 ` Robert Pluim
2018-04-12 16:02 ` Drew Adams
2018-04-12 16:16 ` Robert Pluim
2018-04-12 16:35 ` Yuri Khan
2018-04-12 16:53 ` Eli Zaretskii
2018-04-12 16:48 ` Eli Zaretskii
2018-04-12 11:31 ` Eli Zaretskii [this message]
[not found] <mailman.11969.1523366938.27995.help-gnu-emacs@gnu.org>
[not found] ` <86tvsiaoe3.fsf@zoho.com>
2018-04-10 23:26 ` Bob Proulx
2018-04-10 23:40 ` Bob Proulx
2018-04-15 0:30 ` Tim Johnson
[not found] ` <mailman.12411.1523752244.27995.help-gnu-emacs@gnu.org>
2018-04-15 0:50 ` Emanuel Berg
2018-04-15 15:50 ` Tim Johnson
2018-04-16 12:52 ` Robert Pluim
[not found] ` <mailman.11999.1523402811.27995.help-gnu-emacs@gnu.org>
2018-04-15 1:06 ` Emanuel Berg
2018-04-15 4:13 ` Bob Proulx
[not found] ` <mailman.12416.1523765608.27995.help-gnu-emacs@gnu.org>
2018-04-15 20:04 ` Emanuel Berg
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=834lkg3bl3.fsf@gnu.org \
--to=eliz@gnu.org \
--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).