From: dieter@duenenhof-wilhelm.de (H. Dieter Wilhelm)
To: 19152@debbugs.gnu.org
Subject: bug#19152: 25.0.50; "You can run the command `debug-on-entry' with M-x deb-o RET"
Date: Sun, 23 Nov 2014 12:15:53 +0100 [thread overview]
Message-ID: <87y4r26uc6.fsf@vsl28t2g.ww011> (raw)
In-Reply-To: <fa3f8363-7119-4704-af56-ddbc3a7f9ab1@default>
Drew Adams <drew.adams@oracle.com> writes:
> Please remove such silly messages, which do not tell users about a *key
> sequence* bound to the command they entered.
Actually I find these messages very instructive for people like me,
which had no idea about this (new with Emacs-25?) abbreviation ability!
> (Not to mention that you didn't even put "M-x deb-o RET" between `...'.)
`This could be an unmentioned improvement.' ;-)
> This is not progress. Noise, not help. What were you thinking?
In the contrary I appreciate such messages very much because they remind
me to become more efficient.
*But* above hint is not optimal! It should have
been for example `M-x d-o- <RET>' and not: M-x deb-o RET!
^^^^^^^^^^
So bug#19152 is for real, since the hints are not yet conforming to key
binding conventions and might return an ambiguous and not optimal
(regarding to speed) key sequence.
Thank you for the key binding hints
Dieter
--
Best wishes
H. Dieter Wilhelm
Darmstadt, Germany
next prev parent reply other threads:[~2014-11-23 11:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-23 3:14 bug#19152: 25.0.50; "You can run the command `debug-on-entry' with M-x deb-o RET" Drew Adams
2014-11-23 11:15 ` H. Dieter Wilhelm [this message]
2014-11-23 15:36 ` Lars Magne Ingebrigtsen
2014-11-23 15:54 ` H. Dieter Wilhelm
2014-11-23 15:41 ` Jay Belanger
2014-11-23 16:14 ` H. Dieter Wilhelm
2014-11-23 16:16 ` Drew Adams
[not found] ` <mailman.14373.1416741437.1147.bug-gnu-emacs@gnu.org>
2014-11-23 18:54 ` Alan Mackenzie
2014-11-23 18:59 ` Ivan Shmakov
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=87y4r26uc6.fsf@vsl28t2g.ww011 \
--to=dieter@duenenhof-wilhelm.de \
--cc=19152@debbugs.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).