Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Speaking of slow completion ...
- X-seq: zsh-workers 11809
- From: Felix Rosencrantz <f_rosencrantz@xxxxxxxxx>
- To: zsh-workers <zsh-workers@xxxxxxxxxxxxxx>
- Subject: Re: Speaking of slow completion ...
- Date: Wed, 7 Jun 2000 20:14:05 -0700 (PDT)
- Mailing-list: contact zsh-workers-help@xxxxxxxxxxxxxx; run by ezmlm
--- Bart Schaefer <schaefer@xxxxxxxxxxxxxxxxxxxxxxx> 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
Messages sorted by:
Reverse Date,
Date,
Thread,
Author