|
From: Earnie B. <ea...@us...> - 2012-10-26 11:46:39
|
On Fri, Oct 26, 2012 at 3:15 AM, Eli Zaretskii wrote: >> From: Renato Silva >> Date: Thu, 25 Oct 2012 19:07:29 -0200 >> >> 2012/10/25 Eli Zaretskii >> >> > > From: Renato Silva >> > > Date: Thu, 25 Oct 2012 16:46:35 -0200 >> > > >> > > Right, and even Windows understands forward slashes, for example: >> > > cmd.exe> cd ../.. >> > >> > Only sometimes, so this is unreliable; caveat emptor! E.g.: >> > >> > D:\usr\eli\data>cd d:/usr >> > The system cannot find the path specified. >> > D:\usr\eli\data>cd /usr >> > The system cannot find the path specified. >> > >> > (As you can see from the prompt, that directory does exist.) >> > >> > It looks like it only recognizes relative directory names with forward >> > slashes. >> > >> > >> That seems an specific (and annoying) bug with cmd.exe > > What bug are you alluding to? I see no bug in the examples I posted" > "cd", the cmd.exe internal command, is not advertised as supporting > forward slashes in file names. We are lucky it sometimes work. > What Windows OS? The only failure I could produce on Windows 7 was if I created a directory named d in the root of the drive. Now on my older XP if I cd /somedir then it changes to the directory but if I cd /somedir/subdir then I get an error that it can't find the path. -- Earnie -- https://sites.google.com/site/earnieboyd |