From: "Antoine Beaupré" <anarcat@orangeseeds.org>
To: notmuch@notmuchmail.org
Subject: Re: [PATCH] Add --message-headers flag to notmuch-show
Date: Tue, 12 Nov 2019 10:48:54 -0500 [thread overview]
Message-ID: <87lfsl6qop.fsf@curie.anarc.at> (raw)
In-Reply-To: 87y2wms9r4.fsf@fifthhorseman.net
On 2019-11-11 10:39:11, Daniel Kahn Gillmor wrote:
> On Mon 2019-11-11 10:26:18 -0500, Daniel Kahn Gillmor wrote:
>> - What is the specific use case for this? For example, can you identify
>> situations where different headers need to be emitted by different
>> users? Even one motivating example would help others on this list
>> understand why they might want to care :)
>
> ah, sorry, i've just read id:20191109221358.4349-1-johan.parin@gmail.com
> and its associated messages, so i can see that some of the questions i'm
> asking are already under discussion.
>
> I see that you just want user-agent and x-mailer for your own purposes.
>
> Maybe it would be worthwhile to propose that narrow, limited change as a
> simple patch, without configurability and see what it looks like? I
> would personally be more likely to advocate for merging a patch that
> meets the specific needs of a notmuch user, and increase the
> configurability surface of notmuch.
>
> If processing a couple of extra headers on a long thread is too
> expensive for some consumer, i'd suggest that is an optimization for the
> consumer to tackle.
They need User-Agent:, I want Archive-At:, they will want
X-Mailer... when is it going to stop? I would rather have
configurability here than and endless stream of patches to grow a
possibly boundless list...
a.
--
Brief is this existence, as a fleeting visit in a strange house.
The path to be pursued is poorly lit by a flickering consciousness.
- Albert Einstein
next prev parent reply other threads:[~2019-11-12 16:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-10 12:49 [PATCH] Add --message-headers flag to notmuch-show Johan Parin
2019-11-10 12:56 ` Johan Parin
2019-11-11 15:26 ` Daniel Kahn Gillmor
2019-11-11 15:39 ` Daniel Kahn Gillmor
2019-11-12 15:48 ` Antoine Beaupré [this message]
2019-11-12 17:19 ` Daniel Kahn Gillmor
2019-11-12 17:27 ` Antoine Beaupré
2019-11-12 19:24 ` Johan Parin
2019-11-12 22:19 ` Daniel Kahn Gillmor
2019-11-12 23:30 ` Tomi Ollila
2019-11-14 0:23 ` Daniel Kahn Gillmor
2019-11-14 20:44 ` Tomi Ollila
2019-11-15 16:59 ` Daniel Kahn Gillmor
2019-11-13 9:37 ` David Edmondson
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://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87lfsl6qop.fsf@curie.anarc.at \
--to=anarcat@orangeseeds.org \
--cc=notmuch@notmuchmail.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://yhetil.org/notmuch.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).