Subject: bug#19152: closed (Re: bug#19152: bug#19013: 25.0.50; Suggestions for M-x commands)

From: [email-masked] (GNU bug Tracking System)
Date: Fri, 28 Nov 2014 23:16:02 +0000

Your bug report

#19152: 25.0.50; "You can run the command `debug-on-entry' with M-x deb-o RET"

which was filed against the emacs package, has been closed.

The explanation is attached below, along with your original report.
If you require more details, please reply to [email-masked].

-- 
19152: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=19152
GNU Bug Tracking System
Contact [email-masked] with problems

Subject: Re: bug#19152: bug#19013: 25.0.50; Suggestions for M-x commands
From: Stefan Monnier <[email-masked]>
To: Ivan Shmakov <[email-masked]>
Cc: [email-masked]
Date: Fri, 28 Nov 2014 18:15:13 -0500
List-Id: <debbugs-submit.debbugs.gnu.org>

>>> M-x beginning-of-visual-line RET; then, after some time, – M-x <up>
>>> RET – the same message gets shown, even though M-x <up> is for sure
>>> shorter than M-x b-v.

> Sounds like a plain bug.

Should be fixed now,

        Stefan

Subject: 25.0.50; "You can run the command `debug-on-entry' with M-x deb-o RET"
From: Drew Adams <[email-masked]>
To: [email-masked]
Date: Sat, 22 Nov 2014 19:14:23 -0800 (PST)
List-Id: <debbugs-submit.debbugs.gnu.org>

Please remove such silly messages, which do not tell users about a *key
sequence* bound to the command they entered.

(Not to mention that you didn't even put "M-x deb-o RET" between `...'.)

This is not progress.  Noise, not help.  What were you thinking?

In GNU Emacs 25.0.50.1 (i686-pc-mingw32)
 of 2014-10-20 on LEG570
Bzr revision: 118168 [email-masked]
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
 `configure --enable-checking=yes,glyphs CPPFLAGS=-DGLYPH_DEBUG=1'