From: Eli Zaretskii <eliz@gnu.org>
To: Dmitry Gutov <dmitry@gutov.dev>
Cc: sbaugh@janestreet.com, 71179@debbugs.gnu.org
Subject: bug#71179: [PATCH] In rgrep, check matching files before excluding files
Date: Sat, 25 May 2024 16:45:10 +0300 [thread overview]
Message-ID: <8634q6ypi1.fsf@gnu.org> (raw)
In-Reply-To: <e40c5d54-5292-480a-ba28-3211942b1e3b@gutov.dev> (message from Dmitry Gutov on Sat, 25 May 2024 16:03:00 +0300)
> Date: Sat, 25 May 2024 16:03:00 +0300
> Cc: sbaugh@janestreet.com, 71179@debbugs.gnu.org
> From: Dmitry Gutov <dmitry@gutov.dev>
>
> >> Can you think of a specific problematic usage?
> >
> > Why is that needed? Isn't it clear that it can happen?
>
> Provided we do add an option, knowing the actual audience could help
> name it better and document it better.
>
> But so far the audience I can think of is the very rare people who
> misused the template's customization. And those can use an existing option.
We cannot break user's existing setups, even if we consider them
"rare".
next prev parent reply other threads:[~2024-05-25 13:45 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-05-24 20:14 bug#71179: [PATCH] In rgrep, check matching files before excluding files Spencer Baugh
2024-05-24 20:45 ` Dmitry Gutov
2024-05-24 20:54 ` Spencer Baugh
2024-05-25 12:31 ` Dmitry Gutov
2024-05-26 6:50 ` Juri Linkov
2024-05-26 12:48 ` Spencer Baugh
2024-05-26 12:56 ` Dmitry Gutov
2024-05-25 6:36 ` Eli Zaretskii
2024-05-25 12:26 ` Dmitry Gutov
2024-05-25 12:51 ` Eli Zaretskii
2024-05-25 13:03 ` Dmitry Gutov
2024-05-25 13:45 ` Eli Zaretskii [this message]
2024-05-25 13:58 ` Dmitry Gutov
2024-05-25 13:36 ` Spencer Baugh
2024-05-25 13:56 ` Eli Zaretskii
2024-05-25 14:02 ` Spencer Baugh
2024-05-25 14:13 ` Eli Zaretskii
2024-05-25 14:47 ` Dmitry Gutov
2024-05-25 15:07 ` Eli Zaretskii
2024-05-26 13:42 ` Spencer Baugh
2024-06-01 14:15 ` Eli Zaretskii
2024-06-02 10:46 ` Stefan Kangas
2024-05-25 14:51 ` Dmitry Gutov
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8634q6ypi1.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=71179@debbugs.gnu.org \
--cc=dmitry@gutov.dev \
--cc=sbaugh@janestreet.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).