RE: Re: SixPack mods for Linux users

Try using literally what you typed, i.e.

cd "./pat

Dave
p.s. I suspect the different behaviours you see are because of slight
differences in the CMD options in effect at the time you type the commands.

> -----Original Message-----
> From: [email protected] [mailto:[email protected]] On Behalf
> Of "Fish" (David B. Trout)
> Sent: 17 October 2010 07:53
> To: [email protected]
> Subject: RE: [H390-VM] Re: SixPack mods for Linux users
> 
> Fish wrote:
> 
> [...]
> > Windows has supported *either* forward slash *OR* backward slash
> > for many, many years now.
> 
> More specifically, Windows has accepted either since its inception
> (Windows
> version 1.0! i.e. PRE Windows 3.1!).
> 
> It was only the command interpreter (i.e. cmd.exe, i.e. the command-prompt
> environment) which *originally* did not support forward slashes because of
> its use as an option indicator (e.g. "command /option1 /option2"), but
> that
> was fixed fairly early on.
> 
> I *do* know for a fact that AT LEAST since Windows 2000 (and *probably*
> since Windows 95) the command interpreter (cmd.exe) has supported forward
> slashes in paths. I do note however that the following does, interestingly
> enough, throw an error:
> 
>   Microsoft Windows [Version 6.1.7600]
>   Copyright (c) 2009 Microsoft Corporation.  All rights reserved.
> 
>   C:\Users\Fish>cd /documents
>   The system cannot find the path specified.
> 
> 
> HOWEVER... changing the syntax ever so slightly to be a more properly
> formed
> *relative* path DOES work just fine:
> 
>   C:\Users\Fish>cd ./documents
> 
>   C:\Users\Fish\Documents>
> 
> 
> This is on Windows 7, but I suspect it should prove to be true on every
> Windows system currently in existence.
> 
> --
> "Fish" (David B. Trout)
>  [email protected]
> 
> 
> 
> 
> 
> 
> ------------------------------------
> 
> Yahoo! Groups Links
> 
> 
>