From: L A Walsh <cygwin@tlinx.org>
To: cygwin@cygwin.com
Subject: Re: Has rename syntax changed?
Date: Wed, 04 Mar 2020 10:42:00 -0000 [thread overview]
Message-ID: <5E5F2606.3070201@tlinx.org> (raw)
In-Reply-To: <bc294a03-2796-a53e-c56f-a015a60f557c@t-online.de>
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. If you type 'man basename', you'll
see something that is essentially this:
basename = [optional directory name '/'] basename [. extension (or
suffix)]
You said we are only working in 'cwd' so there is no directory name.
You said all of the filenames must match '*.ext'. The only part
left after the extension, ".ext", is removed is the basename. So while
your replacement can match _anywhere_in_ the filename, the filename and
basename
are the same after it matched the listed 'extension', no?
Second, rename doesn't replace the string '_anywhere_' in the filename,
but only
the first occurance:
> rename anything AnyThing *.ext
> ll *.ext
-rw-rw-rw-+ 1 0 Mar 3 19:24 oneAnyThingtwo.ext
-rw-rw-rw-+ 1 0 Mar 3 19:25 oneAnyThingtwoanythingthree.ext
While bash only works on 1 file at a time,
it can replace 1 or multiple occurances:
> for f in *.ext;do
> mv "$f" "${f//anything/AnyThing}"
> done
> ll *.ext
-rw-rw-rw-+ 1 0 Mar 3 19:24 oneAnyThingtwo.ext
-rw-rw-rw-+ 1 0 Mar 3 19:25 oneAnyThingtwoAnyThingthree.ext
If one wants to replace 1 occurance in multiple files, I would
still use 'mmv', as rename will overwrite files if there is a collision
whereas 'mmv' won't.
--
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
next prev parent reply other threads:[~2020-03-04 3:52 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 [this message]
2020-03-05 10:33 ` Hans-Bernhard Bröker
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=5E5F2606.3070201@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).