[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
all-completions broken in 20.7.1?
From: |
Luc Teirlinck |
Subject: |
all-completions broken in 20.7.1? |
Date: |
Fri, 7 Feb 2003 20:46:59 -0600 (CST) |
Thierry Legras wrote:
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")
???
>From the documentation string of `all-completions', I do not get the
impression that you are supposed to pass an array as the second
argument. If you use, say, an obarray instead, you get the expected
result:
ELISP> (emacs-version)
"GNU Emacs 21.3.50.26 (i686-pc-linux-gnu, X toolkit)\n of 2003-02-07
on swt40.swt.com"
ELISP> (all-completions "" [foo] nil) ;; incorrect argument: array.
("foo" "dired-free-space-args" "PC-complete-word"
"scroll-bar-drag-position" "nodelete" "r" "latin-iso8859-3"
"mark-marker" "buffer-read-only") ;; nonsensical answer
;; (granted, error message would be better)
ELISP> (setq ob (make-vector 1 0))
[0]
ELISP> (intern "foo" ob)
foo
ELISP> ob
[foo]
ELISP> (all-completions "" ob nil) ;; correct argument: obarray
("foo") ;; correct answer.
Sincerely,
Luc.
- all-completions broken in 20.7.1?,
Luc Teirlinck <=