unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Fast completion with visible cue?
Date: 27 Aug 2004 12:33:47 +0200	[thread overview]
Message-ID: <m34qmoc1kk.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <ilu8yc03neg.fsf@latte.josefsson.org>

Simon Josefsson <jas@extundo.com> writes:

> > Try ido-mode.
> 
> Thanks!  This seem to be icomplete-mode, but for C-x C-f.
> 
> However, I see two major problems:
> 
> * It changes how file completion work.  When I type ~/sr and press TAB
>   it scroll in the file *Ido Completion* buffer while displaying 'Find
>   file: ~/sr{SRC/ | CVSROOT | .cvsrc | .newsrc | .newsrc.eld }' in the
>   minibuffer.  It doesn't complete the input to ~/src/, which is the
>   only matching entry.

You accept the current (first) choice with RET, not TAB.

Actually, "sr" occurs as a substring in all of the listed entries,
so there are more than one "matching entry".

You can customize ido-enable-prefix to only match on the first part of
file names.  Personally I find this too inflexible, once you get used
to the default non-prefix mode.

You can also customize ido-enable-flex-matching to get even more
flexible matching, e.g. to select help.txt, you can enter e.g. htx

> 
> * While the 'Find file: ~/{file | foo | bar | ... }' display,
>   occupying up two three lines of the minibuffer by default, may be
>   useful for experts, I think normal users will become afraid when
>   they see it.  My original idea would only display one suggested
>   filename, which seems friendlier.

Customize ido-max-window-height to 1.

> 
> > With that, you have several options here:
> >
> > 1) Since ido remembers the directories you have been editing, it
> > puts the most recent directory as the first choice for completion:
> >
> >   C-x C-f ~/pro RET RET RET RET ... RET
> 
> Yes, I understand now how it wants me to use it.  But I think this is
> a too big user interface change to be on by defaul.t

I have it as the default (with flex matching), and it makes C-x C-f
MUCH MUCH MUCH faster once you get used to it.

> 
> > 2) Since ido remembers the files you work on, this may also work:
> >
> >   C-x C-f help.txt M-s RET
> 
> It worked sometimes, but seemed a bit fragile.

True, but it works most of the time...

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

      reply	other threads:[~2004-08-27 10:33 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-08-26 22:37 Fast completion with visible cue? Simon Josefsson
2004-08-26 22:44 ` David Kastrup
2004-08-26 23:13   ` Simon Josefsson
2004-08-27  3:51     ` Dhruva Krishnamurthy
2004-08-27  8:54     ` Andreas Schwab
2004-08-27 13:27       ` Stefan Monnier
2004-08-27 13:37         ` Andreas Schwab
2004-08-26 23:06 ` Andreas Schwab
2004-08-26 23:13   ` Miles Bader
2004-08-29 20:29     ` Juri Linkov
2004-08-30  3:10       ` Dan Nicolaescu
2004-08-30  8:22         ` Juri Linkov
2004-08-27  6:33 ` Jan D.
2004-08-27 10:16   ` Simon Josefsson
2004-08-27  7:29 ` Kim F. Storm
2004-08-27 10:07   ` Simon Josefsson
2004-08-27 10:33     ` Kim F. Storm [this message]

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=m34qmoc1kk.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@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.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).