This is the mail archive of the
mailing list for the Cygwin project.
Re: bash "pregnant pauses" revisited (B19 on NT 4.0)
- To: Matthias Morche <morche at sat1 dot de>
- Subject: Re: bash "pregnant pauses" revisited (B19 on NT 4.0)
- From: Arndt Schoenewald <arndt at schoenewald dot de>
- Date: Fri, 14 Aug 1998 19:19:28 +0200
- Cc: Cygwin32 Maillist <gnu-win32 at cygnus dot com>
- References: <email@example.com> <35D46C09.7FB309AC@sat1.de>
On Fri, Aug 14, 1998 at 06:55:37PM +0200, Matthias Morche wrote:
> Please, give us a dump of Your PATH as seen by the bash from within
> cygnus.bat. I've got similar problems before I tweaked my PATH.
> Obviously cygwin tried to interpret some element of the path as a
Well, this is what I checked first (I have read all the messages from July
regarding delays caused by name lookups for DOS-style path names).
Anyway, this is what I get in a newly opened CMD.EXE window:
Microsoft(R) Windows NT(TM)
(C) Copyright 1985-1996 Microsoft Corp.
And this is from a fresh bash window launched via cygnus.bat:
Cygnus Cygwin32 B19
bash-2.01$ echo $PATH
But even if I had a stale network drive in PATH, this wouldn't explain
why the prompt is often delayed when I just hit <RETURN> on an empty
line -- why should the shell search the PATH when there's no command
to execute and the prompt is a constant string?!
Arndt Schoenewald (firstname.lastname@example.org)
IT Technology & Solutions Integrator
Ostenhellweg 31, 44135 Dortmund, Germany
Tel: +49 231 556075
Fax: +49 231 556049
For help on using this list (especially unsubscribing), send a message to
"email@example.com" with one line of text: "help".