unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Drew Adams" <drew.adams@oracle.com>
Cc: 11325@debbugs.gnu.org
Subject: bug#11325: 24.1.50; regression: bad order for `substitute-command-keys' with keymap
Date: Sun, 09 Feb 2014 20:59:38 -0800	[thread overview]
Message-ID: <87a9dza7gl.fsf@building.gnus.org> (raw)
In-Reply-To: <FE385EB467D44FCA9B368B25DA2B90DE@us.oracle.com> (Drew Adams's message of "Tue, 24 Apr 2012 08:11:42 -0700")

"Drew Adams" <drew.adams@oracle.com> writes:

> 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?
Seems awfully odd to me:

(substitute-command-keys "\\{dired-mode-map}")
"key             binding
---             -------

e .. f		dired-find-file

C-c		Prefix Command
RET		dired-find-file
C-o		dired-display-file
C-t		Prefix Command
ESC		Prefix Command
SPC		dired-next-line
!		dired-do-shell-command
#		dired-flag-auto-save-files
$		dired-hide-subdir
%		Prefix Command
&		dired-do-async-shell-command
(		dired-hide-details-mode
*		Prefix Command
+		dired-create-directory
-		negative-argument
.		dired-clean-directory
0 .. 9		digit-argument


-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/





  parent reply	other threads:[~2014-02-10  4:59 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 [this message]
2014-02-10  5:09   ` Drew Adams
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

  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=87a9dza7gl.fsf@building.gnus.org \
    --to=larsi@gnus.org \
    --cc=11325@debbugs.gnu.org \
    --cc=drew.adams@oracle.com \
    /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).