From: Oleh Krehel <ohwoeowho@gmail.com>
To: Stefan Monnier <monnier@IRO.UMontreal.CA>
Cc: emacs-devel@gnu.org
Subject: Re: [elpa] master 567ea7e 1/3: Ivy-mode now works better with `find-file'
Date: Fri, 17 Apr 2015 20:39:57 +0200 [thread overview]
Message-ID: <87d232ha4i.fsf@gmail.com> (raw)
In-Reply-To: <jwvwq1awqzh.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Fri, 17 Apr 2015 14:28:26 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Info-read-node-name-1 takes STRING, PREDICATE, and CODE and says to
>> look in the `completing-read' doc. But there's nothing abount CODE
>> there. Where do I get it?
>
> I think you're better off reading about it in the Elisp manual.
> The third argument (called ACTION usually) is basically the *method* to
> use on the "object implemented as a function". It can be nil (which
> means `try-completion'), t (which means `all-completions'), lambda
> (which means `test-completion'), or `boundaries', or `metadata'.
Seems very complex for just returning a (short) list of strings.
Why doesn't this work for `Info-read-node-name-1':
(setq collection (all-completions "" collection predicate))
while this works within the topic, but not in the directory:
(setq collection (funcall collection "" nil t))
If I understood the info page correctly, both should be equivalent.
Oleh
next prev parent reply other threads:[~2015-04-17 18:39 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20150417081157.13187.57850@vcs.savannah.gnu.org>
[not found] ` <E1Yj1NW-0003Ri-FV@vcs.savannah.gnu.org>
2015-04-17 14:49 ` [elpa] master 567ea7e 1/3: Ivy-mode now works better with `find-file' Stefan Monnier
2015-04-17 14:57 ` Oleh Krehel
2015-04-17 18:28 ` Stefan Monnier
2015-04-17 18:39 ` Oleh Krehel [this message]
2015-04-17 19:22 ` Stefan Monnier
2015-04-17 19:27 ` Oleh Krehel
2015-04-18 4:56 ` Stefan Monnier
2015-04-18 4:50 ` Thierry Volpiatto
2015-04-18 14:12 ` Stefan Monnier
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d232ha4i.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@IRO.UMontreal.CA \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.