Github messages for mblaze
 help / color / mirror / Atom feed
* [ISSUE] mpick/magrep only search first matching header
@ 2022-01-04  5:35 seansweda
  2023-02-12 11:24 ` ashiire
  0 siblings, 1 reply; 2+ messages in thread
From: seansweda @ 2022-01-04  5:35 UTC (permalink / raw)
  To: ml

[-- Attachment #1: Type: text/plain, Size: 511 bytes --]

New issue by seansweda on mblaze repository

https://github.com/leahneukirchen/mblaze/issues/219

Description:
This is easily demonstrated by using either tool to search the "Received" headers, as virtually all messages will have several of them. I figured out this can be worked around via magrep "*:regex" to search all the headers so it's not a show stopper. I realize this may be intentional, but if so I don't believe it is clearly documented in the respective man pages (unlike mhdr which has -M option).

^ permalink raw reply	[flat|nested] 2+ messages in thread

* Re: mpick/magrep only search first matching header
  2022-01-04  5:35 [ISSUE] mpick/magrep only search first matching header seansweda
@ 2023-02-12 11:24 ` ashiire
  0 siblings, 0 replies; 2+ messages in thread
From: ashiire @ 2023-02-12 11:24 UTC (permalink / raw)
  To: ml

[-- 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.

^ permalink raw reply	[flat|nested] 2+ messages in thread

end of thread, other threads:[~2023-02-12 11:24 UTC | newest]

Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2022-01-04  5:35 [ISSUE] mpick/magrep only search first matching header seansweda
2023-02-12 11:24 ` ashiire

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).