Mailing-List:	contact cygwin-help AT cygwin DOT com; run by ezmlm
List-Subscribe:	<mailto:cygwin-subscribe AT cygwin DOT com>
List-Archive:	<http://sources.redhat.com/ml/cygwin/>
List-Post:	<mailto:cygwin AT cygwin DOT com>
List-Help:	<mailto:cygwin-help AT cygwin DOT com>, <http://sources.redhat.com/ml/#faqs>
Sender:	cygwin-owner AT cygwin DOT com
Mail-Followup-To:	cygwin AT cygwin DOT com
Delivered-To:	mailing list cygwin AT cygwin DOT com
Message-ID:	<009001c2bfbd$88de7640$78d96f83@pomello>
From:	"Max Bowsher" <maxb AT ukf DOT net>
To:	"Magnus Holmgren" <magho AT home DOT se>, <cygwin AT cygwin DOT com>
References:	<LNBBJIKCLBKJMCCLELOEOECPCJAA DOT magho AT home DOT se>
Subject:	Re: Tab completion list takes enormously long time to generate from empty string
Date:	Sun, 19 Jan 2003 13:20:28 -0000
MIME-Version:	1.0
X-Priority:	3
X-MSMail-Priority:	Normal
X-MimeOLE:	Produced By Microsoft MimeOLE V6.00.2800.1106

Magnus Holmgren wrote:
> But Cygwin setup doesn't have to open and read thousands of files.
> And it's not using cygwin1.dll. The Cygwin layer seems to slow down
> things considerably.  

Yes, stat is known to be an expensive operation.
 
> I was able to strip down my $PATH a bit (removing KDE for example),
> reducing the time needed to generate the list to some minute, but I'm
> not quite satisfied with that either.  
> 
>> It's too bad so many DLLs are produced in this list. Must they
>> have execute
>> bits set to be loaded?
>> 
> NT does have separate read and execute bits. I don't know if DLL:s
> have to have the execute bits set to be loaded,

Yes!

>> This is the sort of thing the "-x," "-E" and "-X" options to "mount"
>> are 
>> meant to address. Check them out, they can probably help a lot with
>> this 
>> problem.
> 
> It helps a bit, or even a lot, but at the price that all files will
> be tab completed to. Unless I create a mount point to each directory
> in $PATH.  

Do you have that many that this is impractical?

Max.


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Bug reporting:         http://cygwin.com/bugs.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/

- Raw text -