Mailing-List: contact cygwin-help@sourceware.cygnus.com; run by ezmlm List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: cygwin-owner@sourceware.cygnus.com Delivered-To: mailing list cygwin@sourceware.cygnus.com From: "Kai Henningsen" Organization: Spuentrup CTI To: cygwin@sourceware.cygnus.com Date: Fri, 1 Oct 1999 14:52:06 +0200 MIME-Version: 1.0 Content-type: text/plain; charset=ISO-8859-1 Subject: Sort of solved (was: Re: What are these cd errors?) X-Confirm-Reading-To: "Kai Henningsen" X-pmrqc: 1 In-reply-to: X-mailer: Pegasus Mail for Win32 (v3.12a) Message-Id: Content-Transfer-Encoding: 8bit X-MIME-Autoconverted: from Quoted-printable to 8bit by delorie.com id IAA11979 Solved! See below. On 1 Oct 99, at 11:13, Kai Henningsen wrote: > Huh?! > > 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 -- http://www.cats.ms Spuentrup CTI Fon: +49 251 322311 0 Windbreede 12 Fax: +49 251 322311 99 D-48157 Münster Mob: +49 161 3223111 Germany GSM: +49 171 7755060 -- Want to unsubscribe from this list? Send a message to cygwin-unsubscribe@sourceware.cygnus.com