From: Linda Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: allowed Linux characters (and windows substitutes)...
Date: Wed, 01 Jun 2011 00:09:00 -0000 [thread overview]
Message-ID: <4DE582FC.5000605@tlinx.org> (raw)
In-Reply-To: <31711163.post@talk.nabble.com>
sweinberger wrote:
> Since ":" and "\" are not acceptable characters in a Linux path, I had to
> work around the problem.
----
I don't know where you got this idea, but on linux, you can put
: and "\" in filenames just fine. Only "/" and "\000" (ASCII NUL) can't
be in a _file_name ("/", obviously works fine in pathnames).
/home> uname --kernel-name --hardware-platform
/home> llg -d C*
drwsrwsr-x 4 lw devel 4096 May 29 10:38 CPAN-ishtar-build-cache/
drwxrwx--- 65 lw lwgrp 4096 Mar 2 2010 C:\Windows/
Note in my "C:\Windows" dir, that's a real colon and backslash,
Not the "full-width" or "presentation forms" one has to use to get a similar
filename on Windows...
Colon: "ï¼" U+FE13 (Presentation Form for Vertical Colon)
Backslash: "ï¼¼" U+FF3C (FullWidth Reverse Solidus)
There also also 'small colon and small reverse solidus' but I've not
used them but they would also appear to work to _display_ a colon and
backslash in a windows filename.
However, on Linux the 'ascii' versions work just fine. 0x3a(colon) &
0x5c(backslash/reverse solidus).
Note, : and \ have no special meaning on linux -- so they are not device or
directory separators if that was something you needed.
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2011-06-01 0:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-05-26 19:33 Cygwin and Windows Paths Leaking Through sweinberger
2011-05-26 20:05 ` Charles Wilson
2011-05-26 20:17 ` sweinberger
2011-05-26 20:24 ` Charles Wilson
2011-05-26 21:21 ` sweinberger
2011-06-01 0:09 ` Linda Walsh [this message]
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=4DE582FC.5000605@tlinx.org \
--to=cygwin@tlinx.org \
--cc=cygwin@cygwin.com \
/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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).