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 21:27:55 +0200 [thread overview]
Message-ID: <87wq1aa72c.fsf@gmail.com> (raw)
In-Reply-To: <jwva8y6womj.fsf-monnier+emacsdiffs@gnu.org> (Stefan Monnier's message of "Fri, 17 Apr 2015 15:22:15 -0400")
Stefan Monnier <monnier@IRO.UMontreal.CA> writes:
>> Seems very complex for just returning a (short) list of strings.
>
> The set of files or the set of Info nodes (which can appear in any file)
> can't conveniently be treated as "a (short) list of strings".
>
>> Why doesn't this work for `Info-read-node-name-1':
>> (setq collection (all-completions "" collection predicate))
>
> I don't understand the question. AFAIK it does work. It just doesn't
> return every possible node name, since there's pretty much an infinite
> supply (if you include those that can be accessed via Tramp, for example).
>
>> (setq collection (funcall collection "" nil t))
>
> Indeed (funcall collection "" pred t) should be equivalent to
> (all-completions "" collection predicate) when `collection' is a function.
> If you see otherwise, we have a problem.
You can try the current ivy-mode code in elpa. It uses this for functions:
(all-completions "" collection predicate)
And it does't work with Info. I tried also with helm-mode, it doesn't
work either.
Oleh
next prev parent reply other threads:[~2015-04-17 19:27 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
2015-04-17 19:22 ` Stefan Monnier
2015-04-17 19:27 ` Oleh Krehel [this message]
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
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=87wq1aa72c.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 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).