util-linux.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Nuno Silva <nunojsilva@ist.utl.pt>
To: util-linux@vger.kernel.org
Cc: "Haelwenn \(lanodan\) Monnier"
	<contact-BazVNOuc66DwXD0AkxfrAg@public.gmane.org>
Subject: Re: [PATCH] rename: change "expression" to "original"
Date: Sun, 22 Jun 2025 10:15:39 +0100	[thread overview]
Message-ID: <1038hjr$5nr$1@ciao.gmane.io> (raw)
In-Reply-To: 20250621232642.17613-2-contact@hacktivis.me

On 2025-06-22, Haelwenn (lanodan) Monnier wrote:

> As rename(1) doesn't uses an expression (like regex or glob) but
> rather a substring.
[...]
> -*rename* [options] _expression replacement file_...
> +*rename* [options] _original replacement file_...
[...]

Oh. I was aware of there being at least two different "rename" utilities
on Linux systems, this one from util-linux and a perl-based one using
regexes, but I hadn't noticed this wording in the online manual and
usage output.

Yes, this change probably helps telling it apart from the perl-based
rename.

(I don't recall what made confusion more prone in the case of this
utility, was it that some distributions installed the perl one as
"rename"?)

-- 
Nuno Silva
Who hopes the Cc works properly.


  reply	other threads:[~2025-06-22  9:20 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-06-21 23:26 [PATCH] rename: change "expression" to "original" Haelwenn (lanodan) Monnier
2025-06-22  9:15 ` Nuno Silva [this message]
2025-06-22  9:49   ` Dirk Gouders
2025-06-22 10:36   ` Dirk Gouders
2025-06-22 15:51 ` Benno Schulenberg
2025-06-30 12:08   ` Karel Zak
2025-07-01 16:03     ` Haelwenn (lanodan) Monnier
     [not found] ` <87cyawp26b.fsf@ist.utl.pt>
2025-06-22 21:34   ` Haelwenn (lanodan) Monnier
2025-07-01 16:01 ` [PATCH v2] rename: change "expression" to "substring" Haelwenn (lanodan) Monnier
2025-07-02  8:03   ` Karel Zak

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='1038hjr$5nr$1@ciao.gmane.io' \
    --to=nunojsilva@ist.utl.pt \
    --cc=contact-BazVNOuc66DwXD0AkxfrAg@public.gmane.org \
    --cc=util-linux@vger.kernel.org \
    /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 NNTP newsgroup(s).