From: "Dave Korn" <dave.korn@artimi.com>
To: "Thread TITTTL'd!" <cygwin-talk@cygwin.com>
Subject: RE: Handling special characters (\/:*?"<>|) gracefully
Date: Wed, 24 May 2006 10:05:00 -0000 [thread overview]
Message-ID: <04c701c67f19$66dd7fe0$a501a8c0@CAM.ARTIMI.COM> (raw)
In-Reply-To: <447420E3.5B3609B3@dessent.net>
On 24 May 2006 10:01, Brian Dessent wrote:
> mwoehlke wrote:
>
>> (Speaking of case sensitivity, is it a Windows limitation that Cygwin
>> can't do this? I'm pretty sure it isn't an NTFS limitation, as Interix
>> has true case-sensitivity.)
>
> As I understand it, the win32 API preserves case but is not case
> sensitive. The native API is both, so in theory an application that
> used only native calls could cope with both README and Readme, but no
> win32 app could.
Not so. See MSDN://CreateFile/FILE_FLAG_POSIX_SEMANTICS. The actual
requirement is "NTFS not FAT" rather than "Native API not Win32 API".
> So, from the standpoint of Cygwin this is pretty
> useless as A) it would take significant code rewrites to use the native
> API everywhere (not to mention backcompat hell for 9x/ME) and B) it
> would lead to the situation (which we briefly got a taste of somewhere
> in a past 1.5.x release) where Cygwin was able to create files that
> could not be deleted by Explorer or any other regular Windows app.
Well, the /real/ problem about those files (which matched DOS special device
names) was that you couldn't remove them from cygwin either; not being able to
delete them from the very same command shell where you created them is far
worse than having to use the same tool to delete something that you used to
create it.
cheers,
DaveK
--
Can't think of a witty .sigline today....
next parent reply other threads:[~2006-05-24 10:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <447420E3.5B3609B3@dessent.net>
2006-05-24 10:05 ` Dave Korn [this message]
2006-05-24 12:18 ` Brian Dessent
2006-05-24 12:28 ` Dave Korn
2006-05-24 22:07 Williams, Gerald S (Jerry)
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='04c701c67f19$66dd7fe0$a501a8c0@CAM.ARTIMI.COM' \
--to=dave.korn@artimi.com \
--cc=cygwin-talk@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).