zsh-workers
 help / color / mirror / code / Atom feed
From: Felix Rosencrantz <f_rosencrantz@yahoo.com>
To: zsh-workers <zsh-workers@sunsite.auc.dk>
Subject: Re: Speaking of slow completion ...
Date: Wed, 7 Jun 2000 20:14:05 -0700 (PDT)	[thread overview]
Message-ID: <20000608031405.12127.qmail@web1303.mail.yahoo.com> (raw)

--- Bart Schaefer <schaefer@candle.brasslantern.com> wrote:
>Any ideas on optimizing _path_files for directories with LOTS of subdirs?

Not sure what you can do if you have to wait for the OS.

Something I suggested in workers/9630 would be to have a style that caused 
_path_files to basically do stats (-d/-f) on the leading portion of a path that
is to be completed.  If the leading part exists, don't attempt to do any
completion on that part of the path, you've got what you want.  Or check for
existence before attempting to glob a name.

I think the stats will go much faster than the directory scans.

This doesn't really help in your example, since you want zsh to perform
completion in the big directories.  But if you know certain directories are
going to can cause you to wait for a while, you might be willing to type that
part of the path.

Also, on a side note, I think there might be a bug in compadd (possibly
matching) that causes it to get in a bad state if an interrupt is sent while it
is working.  I typically want to interrupt in situations when completion is
slow.  Completion works, but matching seems to have some problems.  (I know,
you probably want some those helpful details...)

-FR

__________________________________________________
Do You Yahoo!?
Yahoo! Photos -- now, 100 FREE prints!
http://photos.yahoo.com


             reply	other threads:[~2000-06-08  3:14 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-06-08  3:14 Felix Rosencrantz [this message]
  -- strict thread matches above, loose matches on Subject: below --
2000-06-08  8:53 Sven Wischnowsky
2000-06-07 17:14 Bart Schaefer

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

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

  git send-email \
    --in-reply-to=20000608031405.12127.qmail@web1303.mail.yahoo.com \
    --to=f_rosencrantz@yahoo.com \
    --cc=zsh-workers@sunsite.auc.dk \
    /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.vuxu.org/mirror/zsh/

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 NNTP newsgroup(s).