From: Thierry Legras <Thierry.Legras@alcatel.fr>
Subject: all-completions broken in 20.7.1?
Date: Fri, 07 Feb 2003 15:17:00 +0100 [thread overview]
Message-ID: <3E43BFDC.9060101@nmu.alcatel.fr> (raw)
This bug report will be sent to the Free Software Foundation,
not to your local site managers!!
Please write in English, because the Emacs maintainers do not have
translators to read other languages for them.
In GNU Emacs 20.7.1 (sparc-sun-solaris2.8, X toolkit)
of Tue Aug 29 2000 on steel
configured using `configure --prefix=/opt/sfw'
Please describe exactly what actions triggered the bug
and the precise symptoms of the bug:
Hi,
all-completions function returns scarry things: i started a naked emacs
with -q option, then just evaled (all-completions "" [foo] nil), result is:
("foo" "scroll-bar-drag-position" "nodelete" "r" "latin-iso8859-3"
"mark-marker" "buffer-read-only")
???
Cheers,
Thierry.
Recent input:
M-: down-mouse-2 mouse-2 down-mouse-1 mouse-1 backspace
backspace backspace backspace backspace backspace backspace
backspace backspace backspace f o o C-e return menu-bar
help-menu report-emacs-bug
Recent messages:
For information about the GNU Project and its goals, type C-h C-p.
("foo" "scroll-bar-drag-position" "nodelete" "r" "latin-iso8859-3"
"mark-marker" "buffer-read-only")
Loading emacsbug...
Loading emacsbug...done
Loading dabbrev...
Loading dabbrev...done
Scanning `*scratch*'
Scanning ` *Minibuf-0*'
Scanning ` *Minibuf-1*'
No dynamic expansion for `all-com' found
next reply other threads:[~2003-02-07 14:17 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-07 14:17 Thierry Legras [this message]
2003-02-09 12:39 ` all-completions broken in 20.7.1? Richard Stallman
[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
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=3E43BFDC.9060101@nmu.alcatel.fr \
--to=thierry.legras@alcatel.fr \
/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).