From: Mark Plaksin <happy@usg.edu>
Subject: Re: Use ido for *all* completion?
Date: Thu, 10 Mar 2005 08:27:46 -0500 [thread overview]
Message-ID: <m3acpb6371.fsf@water.tss.usg.edu> (raw)
In-Reply-To: 87mztbu1uy.fsf@ID-87814.user.uni-berlin.de
Oliver Scholz <alkibiades@gmx.de> writes:
> Romain Francoise <romain@orebokech.com> writes:
>
>> Oliver Scholz <alkibiades@gmx.de> writes:
>>
>>> Yes.
>>
>> And don't you agree that while they both show available completions,
>> icomplete is nowhere near ido when it comes to functionality? Or am I
>> missing something?
>
> I don't recall having seen any list of required functionality. I do
> remember that somebody wanted to use ido for other sorts of
> completion. Such things most of the time mean: people want to have a
> particular functionality and express that as "can X also do Y?" So
> before we jump on anything without consideration and merge
> gnu.emacs.help and emacs-devel, it would be quite more methodical to
> find the least difficult way to achieve the required functionality.
I posted the original question. What I really want is to type as little as
possible. The lightning completion code I mentioned is great because it
completes automatically (you don't have to hit TAB) and because you can use
it for all minibuffer prompts.
I have looked at icomplete, partial-completion-mode, and ido. Of the
three, ido is the best for me. It's completion is similar to but much more
powerful than lightning completion's. The only missing piece is (an option)
to make it active for all minibuffer prompts.
next prev parent reply other threads:[~2005-03-10 13:27 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.3075.1110334732.32256.help-gnu-emacs@gnu.org>
2005-03-09 10:19 ` Use ido for *all* completion? Oliver Scholz
2005-03-09 17:44 ` Drew Adams
2005-03-09 17:53 ` Romain Francoise
2005-03-09 21:45 ` Oliver Scholz
2005-03-10 7:43 ` Romain Francoise
2005-03-10 12:22 ` Oliver Scholz
2005-03-10 13:27 ` Mark Plaksin [this message]
[not found] ` <mailman.3281.1110462563.32256.help-gnu-emacs@gnu.org>
2005-03-10 17:02 ` Peter Lee
2005-03-10 17:24 ` Mark Plaksin
[not found] <mailman.3043.1110317172.32256.help-gnu-emacs@gnu.org>
2005-03-09 0:58 ` Oliver Scholz
2005-03-09 1:43 ` Drew Adams
2005-03-09 14:13 ` Stefan Monnier
2005-03-09 17:43 ` Mark Plaksin
[not found] ` <mailman.3152.1110391613.32256.help-gnu-emacs@gnu.org>
2005-03-10 4:19 ` Stefan Monnier
2005-03-14 0:25 ` Mark Plaksin
2005-03-08 18:14 Mark Plaksin
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=m3acpb6371.fsf@water.tss.usg.edu \
--to=happy@usg.edu \
/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).