From: Seth Kurtzberg <seth@cql.com>
To: zsh-users@sunsite.dk
Subject: Re: zmv another zsh gem
Date: Tue, 15 Feb 2005 14:05:53 -0700 [thread overview]
Message-ID: <42126431.5040208@cql.com> (raw)
In-Reply-To: <200502151206.39476.cht@chello.at>
Christian Taylor wrote:
>On Tuesday 15 February 2005 09:51, zzapper wrote:
>
>
>
>>In comp.editors I came across mmv and zmv
>>[...]
>>The case changers don't work on Cygwin because WinXP grumbles target &
>>source filename are the same!
>>
>>
>
>Using mv to change the case of a filename doesn't work on any "caseless" file
>system like vfat, because both filenames refer to the same, existing file.
>Afaik POSIX compliance demands an error in that case. You'll have to do it in
>two steps.
>
>
That would make sense if cygwin were, in general, POSIX compliant and
similarly if cygwin treated the mixed case file system as a mixed case
file system.
That is, however, not the case. In fact cygwin is all over the map. If
you have a file named Filename, and, say, do "vi file<tab>", Filename
will not appear. Cygwin more or less wraps the file system in an
attempt to make the observed behavior as close as possible to a typical
UNIX case sensitive file system. This layer does many things that
cannot be done in the native file system. For example, it maintains
pseudo-permissions, and you cannot, say, do something like ./filename
(to run it), unless it has the x pseudo-permission. It even does fake
symbolic links.
I'm not saying it is worth the effort to muck around with the code to
treat cygwin as a special case. I'm just pointing out that the reason
is not because it violates POSIX, because cygwin is miles away from
being POSIX compliant.
>Christian Taylor
>
>!DSPAM:4211dbf2255221178510702!
>
>
>
next prev parent reply other threads:[~2005-02-15 21:06 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-15 8:51 zzapper
2005-02-15 11:06 ` Christian Taylor
2005-02-15 21:05 ` Seth Kurtzberg [this message]
2005-02-17 19:02 ` Peter Stephenson
2005-02-21 17:08 ` zzapper
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=42126431.5040208@cql.com \
--to=seth@cql.com \
--cc=zsh-users@sunsite.dk \
/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 public inbox
https://git.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).