OT: DOS/Windows and slashes (was Re: Windows XP Pro and PossiblefilePro Bug)

[Kenneth Brody]

Fairlight wrote:
[...]
> > My finger slipped off the 'v' key onto the adjacent 'c' key and
> > I type   ci <filename> when I wanted to type  vi <filename>.
> > But that's how we learn isn't it?  Have you ever done that one?
> 
> Yeah, I've buggered something into CVS that way.  Funnily, I was trying to
> type CVS just now and -three- times in a row typed VCS instead before I
> could force it to go right.  :)

What about typing "print" and having an "f" magically appear after it?

[...]
> > Or things which come in from a Mac world where a / is permitted
> > in a file name.  I have enough problems with <spaces> when things
> > get moved cross-platform.
> 
> I just tried escaping one in *nix and no joy.  (touch bli\/p)  You can
> escape damned near everything else, including control characters.  Not
> slashes.

You can escape the slash all you want.  All that happens is that you end
up with a slash, which is built into the kernel as the path separator.
It's not possible to get a filename with a '/' or '\0' in it.  (Well, you
could theoretically place a '/' in a filename with a raw disk editor, but
I have no idea if you could ever access it.)

[...]

-- 
+-------------------------+--------------------+-----------------------------+
| Kenneth J. Brody        | www.hvcomputer.com |                             |
| kenbrody/at\spamcop.net | www.fptech.com     | #include <std_disclaimer.h> |
+-------------------------+--------------------+-----------------------------+
Don't e-mail me at: <mailto:ThisIsASpamTrap at gmail.com>