From: "Hans-Bernhard Bröker" <HBBroeker@t-online.de>
To: cygwin@cygwin.com
Subject: Re: Has rename syntax changed?
Date: Thu, 05 Mar 2020 10:33:00 -0000 [thread overview]
Message-ID: <b4493fb3-7dc7-2363-5d81-30d5b5441881@t-online.de> (raw)
In-Reply-To: <5E5F2606.3070201@tlinx.org>
Am 04.03.2020 um 04:52 schrieb L A Walsh:
> On 2020/03/03 15:45, Hans-Bernhard Bröker wrote:
>> Am 04.03.2020 um 00:25 schrieb L A Walsh:
>>> On 2020/02/28 04:38, Fergus Daly wrote:
>>>> I am almost certain that the command
>>>> $ rename "anything" "AnyThing" *.ext
>>>> would alter the string from lc to uc as shown, anywhere it occurred
>>>> in any filename in *.ext in the current directory.
>>> isn't that they same as "mv anything.xxx Anything.xxx" ?
>>
>> No. For three reasons:
>>
>> *) it's .ext, not .xxx :-)
>> *) it will find and replace 'anything' _anywhere_in_ the filename, not
>> just in the basename.
> I'm confused about your terminology.
The terminology is fine, but the statement isn't quite. That had better
have read:
>> it will find and replace 'anything' _anywhere_in_ the filename, not
>> just if that's the entire basename.
> You said all of the filenames must match '*.ext'.
No, I didn't. I said that rename will work on all files in the cwd
matching *.ext. Files in the cwd not matching *.ext will be left alone.
--
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:[~2020-03-04 19:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-28 12:38 Fergus Daly
2020-02-28 18:09 ` Lee
2020-02-28 19:52 ` Brian Inglis
2020-02-29 8:27 ` Fergus Daly
2020-02-29 15:48 ` Brian Inglis
2020-03-04 3:52 ` L A Walsh
2020-03-04 5:09 ` Hans-Bernhard Bröker
2020-03-04 10:42 ` L A Walsh
2020-03-05 10:33 ` Hans-Bernhard Bröker [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=b4493fb3-7dc7-2363-5d81-30d5b5441881@t-online.de \
--to=hbbroeker@t-online.de \
--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).