Linked by Hadrien Grasland on Thu 13th Jan 2011 12:53 UTC, submitted by sawboss

Thread beginning with comment 457553
To view parent comment, click here.
To read all comments associated with this story, please click here.
To view parent comment, click here.
To read all comments associated with this story, please click here.
RE[2]: Comment by Toonie
by henderson101 on Thu 13th Jan 2011 15:48
in reply to "RE: Comment by Toonie"
RE[3]: Comment by Toonie
by StephenBeDoper on Fri 14th Jan 2011 16:18
in reply to "RE[2]: Comment by Toonie"
You can't cd to an UNC path, which is extremely annoying!
At work, I practically live in Emacs. It handles UNC paths beautifully, but when I spawn a shell to run a couple of svn commands, I get:
'\\foo\bar\baz\wombat'
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows>_
CMD.EXE was started with the above path as the current directory.
UNC paths are not supported. Defaulting to Windows directory.
Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.
C:\Windows>_
Also, WINE does not support UNC paths at all, AFAIK. This is obviously not Microsoft's fault, but still a pretty bad situation.
Member since:
2009-12-24
Microsoft did not invent the drive letters, its the CP/M heritage, so blame Gary Kildall.
The use of shorthand notation for drives is much older btw.
No need to comment on Mirosoft still using drive letters, there is not much need in modern Windows environments for driver letters, UNC for network drives works fine.