public inbox for cygwin@cygwin.com
 help / color / mirror / Atom feed
From: Fergus Daly <fergusd84@outlook.com>
To: "cygwin@cygwin.com" <cygwin@cygwin.com>
Cc: Fergus Daly <fergusd84@outlook.com>, Lee <ler762@gmail.com>
Subject: RE: Has rename syntax changed?
Date: Sat, 29 Feb 2020 08:27:00 -0000	[thread overview]
Message-ID: <AM6PR03MB52826D4DAF6E696C5EF048D0A4E90@AM6PR03MB5282.eurprd03.prod.outlook.com> (raw)
In-Reply-To: <CAD8GWsvpmfoNtmyN=ntqMF7k3bTy6ycp2EnxZ3ZGe5uz4LrtXw@mail.gmail.com>

> $ rename "anything" "AnyThing" *.ext
> What I remember as past behaviour now fails, leaving he filename unaltered.

>> Try it with the '-v' option

So I did:

$ touch "This is the test file"
$ ls -al
-rw-r--r-- 1    0 Feb 29 08:10 This is the test file
$ rename -v " the " " The " *
`This is the test file' -> `This is The test file'
$ ls -al
-rw-r--r-- 1    0 Feb 29 08:10 This is the test file

Filename unaltered, contrary to verbose confirmation.
Just checking: in DOS Command Prompt box, dir also shows filename unaltered. 
BTW failure consistent on both FAT32 and exFAT filesystems; but the rename command _works_as_expected_ on NTFS.
I get the subtle distinctions between FAT (all versions) and NTFS platforms; but, all the same, the rename command surely worked on *FAT* in the past - I would have noticed if it didn't because I toggle lc <> UC quite a lot.

Fergus




--
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


  parent reply	other threads:[~2020-02-29  8:27 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 [this message]
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

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=AM6PR03MB52826D4DAF6E696C5EF048D0A4E90@AM6PR03MB5282.eurprd03.prod.outlook.com \
    --to=fergusd84@outlook.com \
    --cc=cygwin@cygwin.com \
    --cc=ler762@gmail.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).