emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Cc: bbdb-info@lists.sourceforge.net
Subject: Re: for your amusement
Date: Thu, 20 Feb 2014 19:29:58 +0800	[thread overview]
Message-ID: <8738je2f9l.fsf@ericabrahamsen.net> (raw)
In-Reply-To: 87iosaf3yk.fsf@yahoo.fr

"Nicolas Richard" <theonewiththeevillook@yahoo.fr> writes:

> [fu2 gmane.emacs.bbdb.user]
>
> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> Incidentally, I'm using `ido-everywhere', and would like to write this
>> function so that it didn't _rely_ on ido, but made use of ido when
>> `ido-everywhere' was true. Ie, I'd like to replace the
>> `ido-completing-read' calls with something more generic that still made
>> use of ido when it was turned on. Any suggestions?
>
> ido-everywhere is only meant for buffer/file (see its docstring). People
> who really want ido everywhere should probably use ido-ubiquitous which
> sets completing-read-function to ido-completing-read (in fact, a wrapper
> around it because it cannot handle all cases that completing-read should
> handle).
>
> Hence, my suggestion would be to use completing-read instead of
> ido-completing-read in your code, and configure ido-ubiquitous
> (available from marmalade and melpa) for controlling what to use.
>
> Related package : ido-hacks (which also enables ido in more places)
>
> I *guess* it'll then also work automagically with icomplete-mode
> (shipped with recent emacs) if that is what the user enable instead of
> ido-ubiquitous.

Gosh, where did you guys dig this thread up from? :)

Thanks for the refinements on the original function, and for the tips on
ido related packages in elpa repos -- I hadn't been aware of that. I've
been a tiny bit annoyed with this function ever since I wrote it
(obviously not annoyed enough, since that was years ago), as progressive
narrowing didn't work the way I wanted it to. Kevin, I'll give your
version a whack, and maybe come back with some more refinements in a
bit.

Thanks!
E

  reply	other threads:[~2014-02-20 11:32 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-08-02  9:41 for your amusement Eric Abrahamsen
2014-02-20 10:55 ` Nicolas Richard
2014-02-20 11:29   ` Eric Abrahamsen [this message]
2014-02-20 12:08     ` Nicolas Richard
2014-02-20 13:42       ` Eric Abrahamsen

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.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=8738je2f9l.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --cc=bbdb-info@lists.sourceforge.net \
    --cc=emacs-orgmode@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/org-mode.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).