From: Drew Adams <drew.adams@oracle.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 11325@debbugs.gnu.org
Subject: bug#11325: 24.1.50; regression: bad order for `substitute-command-keys' with keymap
Date: Sun, 9 Feb 2014 21:09:05 -0800 (PST) [thread overview]
Message-ID: <66bde929-3dd7-4eed-b006-2e6e7a5abe30@default> (raw)
In-Reply-To: <87a9dza7gl.fsf@building.gnus.org>
> > Then it was broken differently in Emacs 24, which puts `e..f'
> > first in the list, but restores `0..9' to its rightful place.
>
> Isn't the main problem here that it even tries to do a two-letter
> range?
You could argue that also. But there is no ambiguity in such a
notation, given that if `e .. f' were a multiple-key sequence
then it would be handled differently (via `Prefix Key').
Anyway, that is not what this bug report is about. But yes,
if we got rid of that notation then presumably `e' and `f' would
go back to their rightful places alphabetically.
> Seems awfully odd to me:
Being out of order is odd. That is what this bug thread is about.
next prev parent reply other threads:[~2014-02-10 5:09 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 15:11 bug#11325: 24.1.50; regression: bad order for `substitute-command-keys' with keymap Drew Adams
2012-09-17 0:02 ` Drew Adams
2014-02-10 4:59 ` Lars Ingebrigtsen
2014-02-10 5:09 ` Drew Adams [this message]
2016-04-28 14:43 ` Lars Ingebrigtsen
2016-04-28 15:00 ` Lars Ingebrigtsen
2016-04-29 16:35 ` Lars Ingebrigtsen
2022-01-31 16:32 ` Lars Ingebrigtsen
2022-01-31 16:38 ` bug#11325: [External] : " Drew Adams
2021-10-20 21:32 ` Stefan Kangas
2021-10-21 3:11 ` Lars Ingebrigtsen
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=66bde929-3dd7-4eed-b006-2e6e7a5abe30@default \
--to=drew.adams@oracle.com \
--cc=11325@debbugs.gnu.org \
--cc=larsi@gnus.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 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.