Re: Path problems with trailing dot

2005-05-20 Thread Christopher Faylor
On Mon, May 16, 2005 at 10:19:34AM -0400, Christopher Faylor wrote: >On Mon, May 16, 2005 at 06:53:26AM -0600, Eric Blake wrote: >>According to Stefan Schuerger on 5/15/2005 4:41 PM: >>>bash: test./test2: No such file or directory >>> >>>The trailing dot disappears and cannot be used in paths. Thi

Re: Path problems with trailing dot

2005-05-16 Thread Christopher Faylor
On Mon, May 16, 2005 at 06:53:26AM -0600, Eric Blake wrote: >-BEGIN PGP SIGNED MESSAGE- >Hash: SHA1 > >According to Stefan Schuerger on 5/15/2005 4:41 PM: >> bash: test./test2: No such file or directory >> >> The trailing dot disappears and cannot be used in paths. This seems to >> be a DO

Re: Path problems with trailing dot

2005-05-16 Thread Eric Blake
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 According to Stefan Schuerger on 5/15/2005 4:41 PM: > bash: test./test2: No such file or directory > > The trailing dot disappears and cannot be used in paths. This seems to > be a DOS legacy of either NTFS or Windows. Yes - Windows strips all traili

Re: Path problems with trailing dot

2005-05-15 Thread Larry Hall
At 06:41 PM 5/15/2005, you wrote: >Today I noticed with streamripper that Cygwin appears to have a problem >with trailing dots in paths: > >> mkdir test. ; echo > test./test2 >bash: test./test2: No such file or directory > >The trailing dot disappears and cannot be used in paths. This seems to >be

Path problems with trailing dot

2005-05-15 Thread Stefan Schuerger
Today I noticed with streamripper that Cygwin appears to have a problem with trailing dots in paths: > mkdir test. ; echo > test./test2 bash: test./test2: No such file or directory The trailing dot disappears and cannot be used in paths. This seems to be a DOS legacy of either NTFS or Windows. I