On Thu 2019-11-14 22:44:32 +0200, Tomi Ollila wrote:
> W/ all this information, somewhat exhaustive (not by options, but by
> resources I put making it) list of thougts.
>
>
> 1a by default behave as it is behaving now
>
> 1b alternative, in json and sexp, include *all* headers for the use of
>
On Thu, Nov 14 2019, Daniel Kahn Gillmor wrote:
> On Wed 2019-11-13 01:30:50 +0200, Tomi Ollila wrote:
>> On Tue, Nov 12 2019, Daniel Kahn Gillmor wrote:
>>
>>> And, I still haven't heard any clear arguments for choosing between
>>> configurability as an absolute thing or a differential thing. Th
On Wed 2019-11-13 01:30:50 +0200, Tomi Ollila wrote:
> On Tue, Nov 12 2019, Daniel Kahn Gillmor wrote:
>
>> And, I still haven't heard any clear arguments for choosing between
>> configurability as an absolute thing or a differential thing. They have
>> significantly different impact on adopters o
On Tuesday, 2019-11-12 at 17:19:13 -05, Daniel Kahn Gillmor wrote:
> Are you sure you want the configuration in the config file and not in
> the database itself?
That's fine with me.
dme.
--
So tap at my window, maybe I might let you in.
___
notmuch m
On Tue, Nov 12 2019, Daniel Kahn Gillmor wrote:
>
> And, I still haven't heard any clear arguments for choosing between
> configurability as an absolute thing or a differential thing. They have
> significantly different impact on adopters over time, as the default
> configuration changes.
I don'
On Tue 2019-11-12 20:24:12 +0100, Johan Parin wrote:
> I think this is quite basic functionality. All "nerdy" muas have it ;)
> Gnus has it, mu4e has it etc. mutt seems to have some reasonable default
> of at least displaying User-Agent. I think Thunderbird has it too. etc
Yes, and of course i acc
Daniel Kahn Gillmor writes:
> 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 ot
On 2019-11-12 12:19:01, Daniel Kahn Gillmor wrote:
> On Tue 2019-11-12 10:48:54 -0500, Antoine Beaupré wrote:
>> They need User-Agent:, I want Archive-At:, they will want
>> X-Mailer... when is it going to stop?
>
> It's going to stop when users are satisfied. :) I highly doubt that we
> will reac
On Tue 2019-11-12 10:48:54 -0500, Antoine Beaupré wrote:
> They need User-Agent:, I want Archive-At:, they will want
> X-Mailer... when is it going to stop?
It's going to stop when users are satisfied. :) I highly doubt that we
will reach all possible headers.
> I would rather have configurabili
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 ex
Hi Johan--
On Sun 2019-11-10 13:49:29 +0100, Johan Parin wrote:
> Add a new flag --message-headers to notmuch show, in order to let the
> user specify displayed headers using `notmuch-message-headers' in the
> emacs mua.
This is interesting work, thanks for proposing it.
I haven't reviewed the C
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
According to the proposal of Jani and Tomi I have made a new patch
version which adds a flag --message-headers to notmuch show. This is a
preliminary commit just to get general comments.
No doc updates here. Also there are probably a few style issues. And I
guess I should use talloc instead of m
Add a new flag --message-headers to notmuch show, in order to let the
user specify displayed headers using `notmuch-message-headers' in the
emacs mua.
The flag will impact which headers are output in
format_headers_sprinter.
By default only the following headers are output by notmuch show with
--
14 matches
Mail list logo