From: Philipp Stephani <p.stephani2@gmail.com>
To: "help-gnu-emacs@gnu.org" <help-gnu-emacs@gnu.org>
Subject: How should libraries integrate with IDO?
Date: Fri, 17 Feb 2017 13:41:26 +0000 [thread overview]
Message-ID: <CAArVCkRtfOXdxB8=7ddUEKt7jJ07wYn6sios3G4KArTKE0UcPQ@mail.gmail.com> (raw)
Hi,
what should a library do that wants to use `completing-read', but
optionally support IDO?
- just call `completing-read' and tell the user to set
`completing-read-function' to `ido-completing-read'?
- provide a library-specific customization option, like
`magit-completing-read-function'?
- use `ido-completing-read' whenever ido.el is loaded?
- or something else?
If this isn't documented yet in the ELisp or IDO manuals, please document
it there.
Thanks,
Philipp
next reply other threads:[~2017-02-17 13:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-17 13:41 Philipp Stephani [this message]
2017-02-18 18:55 ` How should libraries integrate with IDO? Stefan Monnier
2017-02-26 16:13 ` Philipp Stephani
2017-02-27 4:08 ` 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='CAArVCkRtfOXdxB8=7ddUEKt7jJ07wYn6sios3G4KArTKE0UcPQ@mail.gmail.com' \
--to=p.stephani2@gmail.com \
--cc=help-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.
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).