From: Christopher Faylor <cygwin@sourceware.cygnus.com>
To: John Wiersba <John.Wiersba@medstat.com>
Cc: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls
Date: Tue, 22 Jun 1999 13:41:00 -0000 [thread overview]
Message-ID: <19990622164131.C29902@cygnus.com> (raw)
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E167@AA-MSG-01>
On Tue, Jun 22, 1999 at 02:56:38PM -0400, John Wiersba wrote:
>Since no one has yet suggested a "stable" release of cygwin1.dll after 1/16,
>I tried the 5/23 release (it was the earliest one I could find after the
>3/28 date mentioned below). It seems to be relatively stable so far (i.e.
>I've used it for several minutes so far!). I did have to twiddle the
>registry settings for mounts (not unexpected, after the comment about mounts
>below).
What does "twiddle the registry settings" mean, exactly? Does that mean that
you didn't use the newer "mount" program which is associated with the DLL?
AFAIK, there should be no need for any manual invervention in switching from
an older DLL to a newer. The new DLL should read the older mount settings
and copy them to the appropriate place in the registry.
>2) It does not however seem to fix the "cd /; cd relativepath/dir" problem
>(apparently going out to the LAN). Note that cd does eventually work -- it
>just hangs for several seconds before figuring things out.
>
>=> Additional information: it doesn't hang when CDPATH is unset. It does
>hang when CDPATH=.
So, in other words, this is probably bash bug. Is anyone willing to debug
this and offer a fix?
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
WARNING: multiple messages have this Message-ID
From: Christopher Faylor <cygwin@sourceware.cygnus.com>
To: John Wiersba <John.Wiersba@medstat.com>
Cc: "'cygwin@sourceware.cygnus.com'" <cygwin@sourceware.cygnus.com>
Subject: Re: question (latest "stable" dll?) + bugs: vim, bash, gcc, cp, find, less, zip, ls
Date: Wed, 30 Jun 1999 22:10:00 -0000 [thread overview]
Message-ID: <19990622164131.C29902@cygnus.com> (raw)
Message-ID: <19990630221000.7M8h3qQwctW3AtDekw7g4FCO6C-RHdeqnwwxSmSB9i4@z> (raw)
In-Reply-To: <03F4742D8225D21191EF00805FE62B990205E167@AA-MSG-01>
On Tue, Jun 22, 1999 at 02:56:38PM -0400, John Wiersba wrote:
>Since no one has yet suggested a "stable" release of cygwin1.dll after 1/16,
>I tried the 5/23 release (it was the earliest one I could find after the
>3/28 date mentioned below). It seems to be relatively stable so far (i.e.
>I've used it for several minutes so far!). I did have to twiddle the
>registry settings for mounts (not unexpected, after the comment about mounts
>below).
What does "twiddle the registry settings" mean, exactly? Does that mean that
you didn't use the newer "mount" program which is associated with the DLL?
AFAIK, there should be no need for any manual invervention in switching from
an older DLL to a newer. The new DLL should read the older mount settings
and copy them to the appropriate place in the registry.
>2) It does not however seem to fix the "cd /; cd relativepath/dir" problem
>(apparently going out to the LAN). Note that cd does eventually work -- it
>just hangs for several seconds before figuring things out.
>
>=> Additional information: it doesn't hang when CDPATH is unset. It does
>hang when CDPATH=.
So, in other words, this is probably bash bug. Is anyone willing to debug
this and offer a fix?
cgf
--
Want to unsubscribe from this list?
Send a message to cygwin-unsubscribe@sourceware.cygnus.com
next prev parent reply other threads:[~1999-06-22 13:41 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
1999-06-22 11:57 John Wiersba
1999-06-22 13:41 ` Christopher Faylor [this message]
1999-06-30 22:10 ` Christopher Faylor
1999-06-30 22:10 ` John Wiersba
-- strict thread matches above, loose matches on Subject: below --
1999-06-23 6:19 Lincoln, W. Terry
1999-06-30 22:10 ` Lincoln, W. Terry
1999-06-22 13:57 John Wiersba
1999-06-22 14:07 ` DJ Delorie
1999-06-30 22:10 ` DJ Delorie
1999-06-30 22:10 ` John Wiersba
1999-06-22 12:09 Lincoln, W. Terry
1999-06-30 22:10 ` Lincoln, W. Terry
1999-06-21 15:59 Phil Edwards
1999-06-21 16:32 ` Brendan Simon
1999-06-30 22:10 ` Brendan Simon
1999-06-22 11:00 ` itz
1999-06-30 22:10 ` itz
1999-06-30 22:10 ` Phil Edwards
1999-06-21 15:40 John Wiersba
1999-06-30 22:10 ` John Wiersba
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=19990622164131.C29902@cygnus.com \
--to=cygwin@sourceware.cygnus.com \
--cc=John.Wiersba@medstat.com \
/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.
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 read-only IMAP folder(s) and NNTP newsgroup(s).