From: ashiire <ashiire@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: mpick/magrep only search first matching header
Date: Sun, 12 Feb 2023 12:24:55 +0100 [thread overview]
Message-ID: <20230212112455.kUADuom4iP87uWbuLzb30oYT3KRWceiI2gYMN4x9Hw4@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-fa6558a0-26e0-48f6-803f-f5a8af34f6a8-mblaze-219@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 440 bytes --]
New comment by ashiire on mblaze repository
https://github.com/leahneukirchen/mblaze/issues/219#issuecomment-1427007071
Comment:
If this is intentional, an option that modifies this behavior would probably be a good idea.
I believe this is not intuitive behavior and would be in favor of changing it, at least by default, unless there is reason to believe that the performance penalty would be an unreasonable tradeoff for most users.
prev parent reply other threads:[~2023-02-12 11:24 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-04 5:35 [ISSUE] " seansweda
2023-02-12 11:24 ` ashiire [this message]
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=20230212112455.kUADuom4iP87uWbuLzb30oYT3KRWceiI2gYMN4x9Hw4@z \
--to=ashiire@users.noreply.github.com \
--cc=ml@inbox.vuxu.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).