This is the mail archive of the
mailing list for the Cygwin project.
Re: Sort of solved (was: Re: What are these cd errors?)
- To: "Kai Henningsen" <kai at cats dot ms>,"cygwin at sourceware dot cygnus dot com" <cygwin at hotpop dot com>
- Subject: Re: Sort of solved (was: Re: What are these cd errors?)
- From: "Larry Hall (RFK Partners, Inc)" <lhall at rfk dot com>
- Date: Fri, 01 Oct 1999 10:50:55 -0400
- References: <E11Wyl5-00069Zemail@example.com>
At 02:52 PM 10/1/99 +0200, Kai Henningsen wrote:
>Solved! See below.
>On 1 Oct 99, at 11:13, Kai Henningsen wrote:
>> The *same* bash cannot do this cd when called as sh?!
>> Here's cygcheck -s -v -r output - essentially, this is a fresh install
>> of B20.1 plus the cygwin1-19990115 DLL:
>I also tried this with the original DLL, and with the one from the
>19990929 snapshot, and both show the exact same problem.
>Mounting the drive it's happening on (so the pathname becomes
>/f/... instead of //f/...) does not change anything, either.
>Nor does ash have less trouble.
>HAH! Found it. Neither bash-called-as-sh nor ash can cope with
>the CDPATH. They cannot even cope with a CDPATH set to "."!
>This sure doesn't happen under Linux.
>Regards - Kai Henningsen
Huh? I've used CDPATH under cygwin for *years* and I've never seen any
problems cding anywhere. Perhaps it would be best if you passed along
your environment with a description of what you are doing since it seems
there are some definite environment issues here.
Larry Hall firstname.lastname@example.org
RFK Partners, Inc. http://www.rfk.com
118 Washington Street (508) 893-9779 - RFK Office
Holliston, MA 01746 (508) 893-9889 - FAX
(508) 560-1285 - cell phone
Want to unsubscribe from this list?
Send a message to email@example.com