On Sun, 5 Feb 2006 22:22:06 -0500 Dusik <[EMAIL PROTECTED]> babbled:

> On 05/02/06, The Rasterman Carsten Haitzler <[EMAIL PROTECTED]> wrote:
> > On Sun, 5 Feb 2006 21:19:31 -0500 Dusik <[EMAIL PROTECTED]> babbled:
> >
> > >
> > > My tab-tab gives me 2800 possibilities on Gentoo on a reiserfs 3 disk
> > > (it's supposed to be a fast SATA disk too).  Bash completion takes
> > > under a second, while exebuf really takes several seconds, feels like
> > > maybe 8-10 sec the first time I run it.  After that both bash an
> > > exebuf appear to be using cached data and appear instantaneously.
> >
> > it could be that bash doesnt stat() the files until they match the string
> > and then it weeds out non-executables. ecore_file stats when it lists and
> > weeds out at that time so it occurs all the expense at once.
> 
> I was comparing to bash completion on an empty string, which means it
> couldn't have checked if it's an executable when it listed, since it
> listed all.  By the time it says "Display all 2800 possibilities? (y
> or n)" it has already weeded out all non-execs, and it's before that
> message appears that I can hear the hard drive going, not after.
> 
> My computer generally feels fast, including working with files, and
> exebuf pops up instantaneously unless I haven't used it for a few
> hours, in which case it hits the hard drive for a few seconds before
> giving me the input dialog.

there is not a lot i can do. exebuf does what bash does - it has to list all
dirs in $PATH and then list contents, weed out non-executable files and then it
finally has enough data to do completions. i moved the list to happen in a
"background thread" (idler) but this simply means exebuf wont have all
executables listed until it has threashed your disk looking for all of them. it
will remain interactive and work- it will simply have a partial list until its
fully finished. once cached the scan will be faster - but really  - beyond you
improving your disk IO (better fs type, better disk, defragment the disk by
tarring it up, re-formattign the writing it all back out so its all sequential
reads to list directory contents) there is nothing we can do without starting
to do evil thgnis like cache files containing all files in $PATH and code that
maintains such cache files based on soruce contents etc.

-- 
------------- Codito, ergo sum - "I code, therefore I am" --------------
The Rasterman (Carsten Haitzler)    [EMAIL PROTECTED]
裸好多
Tokyo, Japan (東京 日本)


-------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc. Do you grep through log files
for problems?  Stop!  Download the new AJAX search engine that makes
searching your log files as easy as surfing the  web.  DOWNLOAD SPLUNK!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642
_______________________________________________
enlightenment-users mailing list
enlightenment-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/enlightenment-users

Reply via email to