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
>    frontends (in many other email systems frontends parse full email
>    messages and see all headers, in notmuch case frontends don't have
>    to do so since notmuch did the parsing and provides structured data
>    of (currently subset) that information
>
>
> 2a have option --message-headers= -- when used just those headers requested
>    is returned (I'd personally prefer this over the "differential" options,
>    frontends get exactly what it wants and does not need to consider any
>    default where to add of suppress from)
>
> 2b have --add-message-header=foo --suppress-message-header=qux -- to modify
>    the defult list...
>
> 2c have named stored configurations, which can be retrieved with yet another
>    command line option, since naming is hard, quick potenttially dumb
>    example could be like: --custom-message-headers=my-cli-headers-set-3

thanks for this list.  It seems to miss the other thing that is
currently being contemplated, which is maybe:

  3  have a new "notmuch show" configuration option that affects what
     headers should be emitted

This is distinct from the command-line options detailed in 2a and 2b,
and distinct from the idea of named bundled configuration options in the
config file.

       --dkg