From: Drew Adams <drew.adams@oracle.com>
To: 16677@debbugs.gnu.org
Subject: bug#16677: 24.3.50; Wrong type argument: char-or-string-p, 67108923
Date: Thu, 6 Feb 2014 18:57:20 -0800 (PST) [thread overview]
Message-ID: <2ba9d857-f8b1-4f0b-8640-41229d998838@default> (raw)
emacs -Q
C-q C-;
Gives the cited error message. It should give a more user
interface-level error, saying something to the effect that the key
sequence you used does not correspond to a character.
Note: in Emacs 20, this just inserts the escape character (^[), which is
wrong. In Emacs 22, it just inserts the semicolon character (;), which
is also wrong.
Emacs 23 got it right, but it did not make the extra effort to give the
user an error message that s?he deserves: something more helpful than a
low-level barf message (even if that message might be comprehensible to
a knowledgable Emacs user).
Emacs can do better than that - this is, after all, a command, i.e.,
something that users use directly.
(I discovered this by accident, when my fingers slipped.)
In GNU Emacs 24.3.50.1 (i686-pc-mingw32)
of 2014-02-02 on ODIEONE
Bzr revision: 116242 rudalics@gmx.at-20140202130041-n967dw77nw7ztvy9
Windowing system distributor `Microsoft Corp.', version 6.1.7601
Configured using:
`configure --prefix=/c/Devel/emacs/binary --enable-checking=yes,glyphs
'CFLAGS=-O0 -g3' LDFLAGS=-Lc:/Devel/emacs/lib
CPPFLAGS=-Ic:/Devel/emacs/include'
next reply other threads:[~2014-02-07 2:57 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-02-07 2:57 Drew Adams [this message]
2014-02-07 3:55 ` bug#16677: 24.3.50; Wrong type argument: char-or-string-p, 67108923 Juanma Barranquero
2014-02-07 8:01 ` Eli Zaretskii
2014-02-07 10:52 ` Juanma Barranquero
2014-02-07 11:15 ` Juanma Barranquero
2014-02-08 10:20 ` Juri Linkov
[not found] <<2ba9d857-f8b1-4f0b-8640-41229d998838@default>
[not found] ` <<CAAeL0STsVYYLN+AVaGkA-NAcV5WKyHevGrcdMjBntVWC5Oy=Eg@mail.gmail.com>
[not found] ` <<83ppmzxseg.fsf@gnu.org>
2014-02-07 17:02 ` Drew Adams
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=2ba9d857-f8b1-4f0b-8640-41229d998838@default \
--to=drew.adams@oracle.com \
--cc=16677@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).