From: Richard Stallman <rms@gnu.org>
To: emacs-devel@gnu.org
Subject: [schierlm@gmx.de: Misleading error message when defining empty keyboard macro and no keyboard macro has been defined yet.]
Date: Mon, 09 Jul 2007 10:29:48 -0400 [thread overview]
Message-ID: <E1I7uFI-0001mM-PO@fencepost.gnu.org> (raw)
Would someone please DTRT, then ack?
------- Start of forwarded message -------
X-Spam-Status: No, score=0.0 required=5.0 tests=UNPARSEABLE_RELAY
autolearn=failed version=3.1.0
Date: Sun, 08 Jul 2007 21:14:16 +0200
From: Michael Schierl <schierlm@gmx.de>
MIME-Version: 1.0
To: bug-gnu-emacs@gnu.org
Content-Type: text/plain; charset=ISO-8859-15
Subject: Misleading error message when defining empty keyboard macro and no
keyboard macro has been defined yet.
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
- - Start emacs with -Q
- - Press <f3> and immediately <f4>
Result (in echo area):
Only one keyboard macro defined.
Huh? In fact, there are only *zero* keyboard macros defined (if you do
not count the empty one that has been ignored).
Expected result:
Ignore empty macro
[full *Messages* are below.]
In GNU Emacs 22.1.1 (i386-mingw-nt5.1.2600)
of 2007-06-02 on RELEASE
Windowing system distributor `Microsoft Corp.', version 5.1.2600
configured using `configure --with-gcc (3.4) --cflags -Ic:/gnuwin32/include'
Important settings:
value of $LC_ALL: nil
value of $LC_COLLATE: nil
value of $LC_CTYPE: nil
value of $LC_MESSAGES: nil
value of $LC_MONETARY: nil
value of $LC_NUMERIC: nil
value of $LC_TIME: nil
value of $LANG: DEU
locale-coding-system: cp1252
default-enable-multibyte-characters: t
Major mode: Lisp Interaction
Minor modes in effect:
encoded-kbd-mode: t
tooltip-mode: t
tool-bar-mode: t
mouse-wheel-mode: t
menu-bar-mode: t
file-name-shadow-mode: t
global-font-lock-mode: t
font-lock-mode: t
blink-cursor-mode: t
unify-8859-on-encoding-mode: t
utf-translate-cjk-mode: t
auto-compression-mode: t
line-number-mode: t
Recent input:
<f3> <f4> M-x r e p o r t - e <tab> <return>
Recent messages:
Loading encoded-kb...done
For information about the GNU Project and its goals, type C-h C-p.
Loading kmacro...done
Defining kbd macro...
Keyboard macro defined
Ignore empty macro
Only one keyboard macro defined.
Loading emacsbug...
Loading regexp-opt...done
Loading emacsbug...done
_______________________________________________
bug-gnu-emacs mailing list
bug-gnu-emacs@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-gnu-emacs
------- End of forwarded message -------
next reply other threads:[~2007-07-09 14:29 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-09 14:29 Richard Stallman [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-07-17 3:34 [schierlm@gmx.de: Misleading error message when defining empty keyboard macro and no keyboard macro has been defined yet.] Richard Stallman
2007-07-17 9:27 ` martin rudalics
2007-07-17 17:55 ` Michael Schierl
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=E1I7uFI-0001mM-PO@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@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).