unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: bug-gnu-emacs@gnu.org
Subject: all-completions broken in 20.7.1?
Date: Fri, 7 Feb 2003 20:46:59 -0600 (CST)	[thread overview]
Message-ID: <200302080246.UAA28156@eel.dms.auburn.edu> (raw)

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.

             reply	other threads:[~2003-02-08  2:46 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-02-08  2:46 Luc Teirlinck [this message]
  -- strict thread matches above, loose matches on Subject: below --
2003-02-07 14:17 all-completions broken in 20.7.1? Thierry Legras
2003-02-09 12:39 ` 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

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=200302080246.UAA28156@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --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).