From: Richard Stallman <rms@gnu.org>
Cc: bug-gnu-emacs@gnu.org
Subject: Re: all-completions broken in 20.7.1?
Date: Sun, 09 Feb 2003 07:39:24 -0500 [thread overview]
Message-ID: <E18hqk0-0003b2-00@fencepost.gnu.org> (raw)
In-Reply-To: <3E43BFDC.9060101@nmu.alcatel.fr> (message from Thierry Legras on Fri, 07 Feb 2003 15:17:00 +0100)
all-completions function returns scarry things: i started a naked emacs
with -q option, then just evaled (all-completions "" [foo] nil), result is:
The second argument should be an alist or an obarray or a function.
[foo] is not valid as any of those.
Today, if I eval (using C-j) the following in *scratch*, I get:
?S => 83
?SPC => 83
I think this simply fails to notice that there were junk letters `PC'
after the expression that it read.
'(?SPC) => (83 PC)
but if I do
M-: ? S P C RET
I get
list: Trailing garbage following expression
so the current character syntax really is pretty obscure.
That does check for junk that it did not read.
The difference in behavior is simply that.
Since it is not reasonable practice to use a character constant
followed by a symbol and not put a space between, I think it would be
ok to define something like ?SPC. But I am not sure we need to do
this. If we do it, we should first release an Emacs version where
it is an error to write ?<LETTER><LETTER>.
next prev parent reply other threads:[~2003-02-09 12:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 14:17 all-completions broken in 20.7.1? Thierry Legras
2003-02-09 12:39 ` Richard Stallman [this message]
[not found] ` <mailman.1693.1044794368.21513.bug-gnu-emacs@gnu.org>
2003-02-10 19:48 ` Kevin Rodgers
2003-02-10 21:07 ` Andreas Schwab
-- strict thread matches above, loose matches on Subject: below --
2003-02-08 2:46 Luc Teirlinck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E18hqk0-0003b2-00@fencepost.gnu.org \
--to=rms@gnu.org \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.