From: Andy Moreton <andrewjmoreton@gmail.com>
To: bug-gnu-emacs@gnu.org
Subject: bug#8479: 24.0.50; Strange error message upon M-z M-z
Date: Mon, 11 Apr 2011 23:10:12 +0100 [thread overview]
Message-ID: <82fwpozbgb.fsf@gmail.com> (raw)
In-Reply-To: <87bp0clqtz.fsf@fencepost.gnu.org>
On Mon 11 Apr 2011, David Kastrup wrote:
> Type M-z M-z and you get the following error back trace and message:
>
> Debugger entered--Lisp error: (wrong-type-argument characterp 134217850)
> call-interactively(zap-to-char nil nil)
`zap-to-char' (in simple.el) has interactive spec:
(interactive "p\ncZap to char: ")
Looking at `call-interactively' (in callint.c):
--8<---------------cut here---------------start------------->8---
case 'c': /* Character */
/* Prompt in `minibuffer-prompt' face. */
Fput_text_property (make_number (0),
make_number (SCHARS (callint_message)),
Qface, Qminibuffer_prompt, callint_message);
args[i] = Fread_char (callint_message, Qnil, Qnil);
message1_nolog ((char *) 0);
/* Passing args[i] directly stimulates compiler bug */
teml = args[i];
visargs[i] = Fchar_to_string (teml);
break;
--8<---------------cut here---------------end--------------->8---
Looking at the help for `read-char':
--8<---------------cut here---------------start------------->8---
If the user generates an event which is not a character (i.e. a mouse
click or function key event), `read-char' signals an error. As an
exception, switch-frame events are put off until non-character events
can be read.
If you want to read non-character events, or ignore them, call
`read-event' or `read-char-exclusive' instead.
--8<---------------cut here---------------end--------------->8---
Perhaps `call-interactively' should be using `read-char-exclusive' so
that the second M-z is ignored ?
AndyM
next prev parent reply other threads:[~2011-04-11 22:10 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-04-11 16:01 bug#8479: 24.0.50; Strange error message upon M-z M-z David Kastrup
2011-04-11 16:56 ` Eli Zaretskii
2011-10-07 6:59 ` Glenn Morris
2011-10-07 12:17 ` Eli Zaretskii
2011-10-08 21:07 ` Glenn Morris
2011-04-11 22:10 ` Andy Moreton [this message]
2011-04-12 5:15 ` Kevin Rodgers
2011-04-12 6:00 ` Eli Zaretskii
2011-04-14 2:05 ` Kevin Rodgers
2011-04-15 1:17 ` Stefan Monnier
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=82fwpozbgb.fsf@gmail.com \
--to=andrewjmoreton@gmail.com \
--cc=bug-gnu-emacs@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).