From: Dirk Gouders <dirk@gouders.net>
To: util-linux@vger.kernel.org
Cc: "Haelwenn (lanodan) Monnier" <contact@hacktivis.me>
Subject: Re: [PATCH] rename: change "expression" to "original"
Date: Sun, 22 Jun 2025 12:36:12 +0200 [thread overview]
Message-ID: <ghjz54vzab.fsf@gouders.net> (raw)
In-Reply-To: <1038hjr$5nr$1@ciao.gmane.io> (Nuno Silva's message of "Sun, 22 Jun 2025 10:15:39 +0100")
Resend with Cc address from original posting:
Nuno Silva <nunojsilva@ist.utl.pt> writes:
> 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.
In case this change will be accepted, how about using other terms for
both, "expression / original" and "replacement"? Could be that it is my
individual difficulty but I would way better understand something like:
*rename* [options] _string_1 string_2 file_...
Anyway, I guess the following should be fixed, regardless:
+If the _original_ is empty, then by default _replacement_ will...
=>
+If _original_ is empty, then by default _replacement_ will...
Regards,
Dirk
next prev parent reply other threads:[~2025-06-22 10:36 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
2025-06-22 9:49 ` Dirk Gouders
2025-06-22 10:36 ` Dirk Gouders [this message]
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=ghjz54vzab.fsf@gouders.net \
--to=dirk@gouders.net \
--cc=contact@hacktivis.me \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.