unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Kevin Rodgers <ihs_4664@yahoo.com>
Subject: Re: Qs on obarrays
Date: Wed, 12 Oct 2005 12:23:11 -0600	[thread overview]
Message-ID: <dijkak$d97$1@sea.gmane.org> (raw)
In-Reply-To: <DNEMKBNJBGPAOPIJOOICCEFECNAA.drew.adams@oracle.com>

Drew Adams wrote:
 > Actually, I don't bother creating a new obarray, after all. I just use an
 > alist  (easier to manipulate) and redefine the predicate to work with 
that:
 >
 > (all-completions "" my-alist (lambda (elt) (commandp (intern (car 
elt)))))
 >
 > Or, more generally (what I really do):
 >
 > (when (arrayp minibuffer-completion-table)
 >   (setq minibuffer-completion-predicate
 >         `(lambda (elt)
 >             (funcall ',minibuffer-completion-predicate
 >                      (intern (car elt))))))
 > (setq minibuffer-completion-table
 >       my-alist) ; Built by filtering `minibuffer-completion-table'.
 > ...
 > (all-completions "" minibuffer-completion-table
 >                  minibuffer-completion-predicate)

I wouldn't recommend setq'ing minibuffer-completion-table and
-predicate.  Those variables (plus -confirm) are let-bound by Emacs' own
higher level completion functions, and I think it'd be cleaner if you
did the same -- or just set your own my-completion-table and -predicate
variables, since you're passing their values explicitly to
all-completions anyway.

-- 
Kevin Rodgers

  reply	other threads:[~2005-10-12 18:23 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.10964.1129078391.20277.help-gnu-emacs@gnu.org>
2005-10-12  1:32 ` Qs on obarrays Pascal Bourguignon
2005-10-12  2:02   ` Drew Adams
2005-10-12 16:17   ` Kevin Rodgers
2005-10-12 17:14     ` Drew Adams
2005-10-12 18:23       ` Kevin Rodgers [this message]
2005-10-12 20:24         ` Drew Adams
2005-10-12 15:53 ` Stefan Monnier
2005-10-12  0:52 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='dijkak$d97$1@sea.gmane.org' \
    --to=ihs_4664@yahoo.com \
    /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.
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).