From: "Drew Adams" <drew.adams@oracle.com>
To: <emacs-devel@gnu.org>
Subject: RE: read-file-name-predicate
Date: Wed, 7 Mar 2007 09:35:44 -0800 [thread overview]
Message-ID: <EIENLHALHGIMHGDOLMIMGEJJCPAA.drew.adams@oracle.com> (raw)
In-Reply-To: <E1HOzu5-0008Gj-AS@fencepost.gnu.org>
> `read-file-name-predicate' has an external,
> Lisp behavior: During completion, Lisp code can check what
> the predicate is or even change the predicate. Shouldn't that
> be documented?
>
> I see no reason to document it at present.
> It is meant for internal use only.
How is it different from `minibuffer-completion-predicate'? I see the two as
parallel.
Without this variable, how can you do, for file-name completion, what you
might do for non-file-name completion using
`minibuffer-completion-predicate'? Why document one but not the other?
next prev parent reply other threads:[~2007-03-07 17:35 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-07 6:00 read-file-name-predicate Drew Adams
2007-03-07 14:39 ` read-file-name-predicate Stefan Monnier
2007-03-07 15:11 ` read-file-name-predicate Juanma Barranquero
2007-03-07 16:31 ` read-file-name-predicate Drew Adams
2007-03-07 16:49 ` read-file-name-predicate Eli Zaretskii
2007-03-07 17:14 ` read-file-name-predicate Drew Adams
2007-03-08 4:19 ` read-file-name-predicate Eli Zaretskii
2007-03-08 3:16 ` read-file-name-predicate Richard Stallman
2007-03-08 11:16 ` read-file-name-predicate Kim F. Storm
2007-03-08 3:16 ` read-file-name-predicate Richard Stallman
2007-03-07 17:26 ` read-file-name-predicate Richard Stallman
2007-03-07 17:35 ` Drew Adams [this message]
2007-03-08 17:40 ` read-file-name-predicate Richard Stallman
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=EIENLHALHGIMHGDOLMIMGEJJCPAA.drew.adams@oracle.com \
--to=drew.adams@oracle.com \
--cc=emacs-devel@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).