unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: "Sean O'Rourke" <sorourke@cs.ucsd.edu>
Subject: Allow prefix arg for ido-find-*file* (maybe)
Date: Tue, 14 Sep 2004 10:07:53 -0700	[thread overview]
Message-ID: <m2wtywzsly.wl%sorourke@cs.ucsd.edu> (raw)

ido mode is currently unusably slow when finding a file in a large
directory.  For example, in a directory with ~3000 files,
`ido-find-file' takes several seconds to come up with a prompt.  When
you know you're in such a directory, it would be nice to bypass ido
entirely and fall back to the original `find-file'.  Since the ido
functions currently don't use a prefix argument, I think that when
called with a prefix argument, the ido functions should fall back to
their non-ido equivalents.

/s

ps -- here's a defadvice to get the effect I want:

    (defadvice ido-find-file (around allow-prefix compile activate)
      (if current-prefix-arg
          (let ((read-file-name-function nil))
            (call-interactively 'find-file))
          ad-do-it))
    
    (defadvice ido-find-file-other-window (around allow-prefix compile activate)
      (if current-prefix-arg
          (let ((read-file-name-function nil))
            (call-interactively 'find-file-other-window))
          ad-do-it))
    
    (defadvice ido-find-alternate-file (around allow-prefix compile activate)
      (if current-prefix-arg
          (let ((read-file-name-function nil))
            (call-interactively 'find-alternate-file))
          ad-do-it))

             reply	other threads:[~2004-09-14 17:07 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-09-14 17:07 Sean O'Rourke [this message]
     [not found] <mailman.2739.1095182044.1998.bug-gnu-emacs@gnu.org>
2004-09-25  0:13 ` Allow prefix arg for ido-find-*file* (maybe) Kim F. Storm
2004-09-25  1:54   ` Sean O'Rourke
     [not found]   ` <mailman.3966.1096077688.1998.bug-gnu-emacs@gnu.org>
2004-09-26 21:29     ` Kim F. Storm
2004-09-26 22:02       ` Sean O'Rourke

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=m2wtywzsly.wl%sorourke@cs.ucsd.edu \
    --to=sorourke@cs.ucsd.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.
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).