From: "Juanma Barranquero" <lekktu@gmail.com>
Cc: Emacs Devel <emacs-devel@gnu.org>
Subject: Re: Problem with non-valid file names on w32
Date: Thu, 30 Nov 2006 15:08:02 +0100 [thread overview]
Message-ID: <f7ccd24b0611300608n2d50696eu9b320b6903b71faa@mail.gmail.com> (raw)
In-Reply-To: <456ED855.9070006@student.lu.se>
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
next prev parent reply other threads:[~2006-11-30 14:08 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-30 13:10 Problem with non-valid file names on w32 Lennart Borgman
2006-11-30 14:08 ` Juanma Barranquero [this message]
2006-11-30 15:55 ` Lennart Borgman
2006-12-01 20:55 ` Stuart D. Herring
2006-11-30 17:52 ` Mathias Dahl
2006-11-30 19:25 ` Juanma Barranquero
2006-12-01 10:39 ` Eli Zaretskii
2006-12-01 11:12 ` Juanma Barranquero
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=f7ccd24b0611300608n2d50696eu9b320b6903b71faa@mail.gmail.com \
--to=lekktu@gmail.com \
--cc=emacs-devel@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.