From: "Lawrence Velázquez" <larryv@zsh.org>
To: "Michele Venturi" <dardo82@gmail.com>
Cc: zsh-users@zsh.org
Subject: Re: Substitute the last match of a pattern during parameters expansion.
Date: Tue, 13 Sep 2022 02:06:17 -0400 [thread overview]
Message-ID: <4844b850-2ca6-4c90-95ae-aae00dc339cf@www.fastmail.com> (raw)
In-Reply-To: <CA+Ds4NuuAMiKoi9D=hgyY-RbySais1eEgZHbivx=L68KUWv1bg@mail.gmail.com>
On Tue, Sep 13, 2022, at 12:19 AM, Michele Venturi wrote:
> On Mon, Sep 12, 2022, 08:01,
> Lawrence Velázquez,
> <larryv@zsh.org>, wrote:
>
>> But there is already a '%' flag...
>> This doesn't merits a new one.
No, I didn't write that. What I wrote was: "There is already a '%'
flag. I do not think this merits a new one." I intentionally said
"I do not think" to make it clear that that was my personal opinion.
Please do not modify others' words and present the revision as a
quotation. It's *extremely* poor form.
> What merits a new one then?
There isn't a strict policy or anything, but in my opinion new flags
should only be considered for broadly useful functionality that
cannot be implemented using the existing flags or enhanced versions
of them. We already have an absurd number of flags; I don't think
new ones should be added willy-nilly.
Your use case could theoretically be satisfied by an enhanced 'I'
flag, so I don't think it deserves its own flag.
> How do you extend the I flag?
I don't know. I am not familiar with the code base.
--
vq
next prev parent reply other threads:[~2022-09-13 6:08 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-12 4:20 Michele Venturi
2022-09-12 6:01 ` Lawrence Velázquez
2022-09-13 4:19 ` Michele Venturi
2022-09-13 6:06 ` Lawrence Velázquez [this message]
2022-09-13 23:11 ` Bart Schaefer
2022-09-14 3:20 ` Michele Venturi
2022-09-14 18:56 ` Bart Schaefer
2022-09-14 20:06 ` Ray Andrews
2022-09-14 21:59 ` Michele Venturi
2022-09-14 22:04 ` Bart Schaefer
2022-09-14 22:20 ` Michele Venturi
2022-09-15 0:00 ` Alex Satrapa
2022-09-15 0:29 ` Lawrence Velázquez
2022-09-15 1:45 ` Michele Venturi
2022-09-15 12:01 ` Roman Perepelitsa
2022-09-15 23:29 ` Michele Venturi
2022-09-16 6:37 ` Roman Perepelitsa
2022-09-16 7:52 ` Michele Venturi
2022-09-16 7:57 ` Roman Perepelitsa
2022-09-16 8:19 ` Michele Venturi
2022-09-16 8:22 ` Roman Perepelitsa
2022-09-16 8:33 ` Michele Venturi
2022-09-16 8:36 ` Roman Perepelitsa
2022-09-16 9:08 ` Michele Venturi
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=4844b850-2ca6-4c90-95ae-aae00dc339cf@www.fastmail.com \
--to=larryv@zsh.org \
--cc=dardo82@gmail.com \
--cc=zsh-users@zsh.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.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
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).