Re: Problem with non-valid file names on w32

["Juanma Barranquero" <lekktu@gmail.com>]

On 11/30/06, Lennart Borgman <lennart.borgman.073@student.lu.se> wrote:

> When you try to save the file Emacs will be noted about the problem and
> tell the user. So maybe it is not that catastrophic, but it is not
> pretty IMO.

If you have shared resources, the rules governing file name validity
could be different in some mounted volumes. How do you plan to say
that to Emacs?

> It gets a bit worse if you have file names like
> "c:/some/path/d:hidden.txt". In this case Emacs will not complain when
> saving the file. Instead a hidden stream is created.

That is a feature (if unintended). foo:bar is not an invalid name in
Windows. Moreover, it will only happen for the infamous C:foo case. If
you try C:/my/dir/d:/another/dir/file.txt the buffer will be saved
(assuming it exists) on "d:/another/dir/file.txt".

> This seems to be the way our
> famous relative Notepad does it. (Except for the awkward hidden case.)

Why do you call it "awkward"? It's a feature, and that's its syntax.
CMD does not do a very good job of handling streams, but for example
in 4NT you can do:

 C:\> copy con foo:bar
 con => foo:bar
  foobar fubar
 ^Z
      1 file copied

 C:\> type foo:bar
  foobar fubar

  C:\> dir /: foo

  Volume in drive C is unlabeled      Serial number is 0836:9fa9
  Directory of  C:\foo

 30/11/2006  14:52               0  foo
                                14    bar:$DATA
              14 bytes in 1 file and 0 dirs    0 bytes allocated
 175.102.554.112 bytes free

 C:\>

                    /L/e/k/t/u