From: Daniel Kahn Gillmor <dkg@fifthhorseman.net>
To: Johan Parin <johanparin@gmail.com>, notmuch@notmuchmail.org
Subject: Re: [PATCH] Display extra headers for emacs-mua - db config option
Date: Fri, 22 Nov 2019 10:51:06 +0800 [thread overview]
Message-ID: <87lfs8ipyd.fsf@fifthhorseman.net> (raw)
In-Reply-To: <m21ru0sxl7.fsf@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1407 bytes --]
On Thu 2019-11-21 22:56:04 +0100, Johan Parin wrote:
> Here is a taste (not fully tested, but seems to work).
Oof, i see what you mean :(
I haven't tried to implement this a different way, so i don't know
whether there isn't a shorter cut to what we want, but yow it is a lot.
Are we doing something more deeply, architecturally wrong that saddles
us these two rather displeasing choices?
> diff --git a/doc/man1/notmuch-config.rst b/doc/man1/notmuch-config.rst
> index 28487079..0eb59883 100644
> --- a/doc/man1/notmuch-config.rst
> +++ b/doc/man1/notmuch-config.rst
> @@ -204,6 +204,12 @@ The available configuration items are described below.
> supported. See **notmuch-search-terms(7)** for a list of existing
> prefixes, and an explanation of probabilistic prefixes.
>
> +**show.extra_headers**
> + A list of extra headers that will be output by **notmuch show**
> + with ``--format=sexp``, if present in the message.
> +
> + Default: empty list.
> +
> **built_with.<name>**
> Compile time feature <name>. Current possibilities include
> "compact" (see **notmuch-compact(1)**) and "field_processor" (see
Given the implementation choices, i think you want **[STORED IN
DATABASE]** here (see the definitions for query.<name> and
index.header.<prefix> and index.decrypt).
Thanks for taking the time to sort this out!
--dkg
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 227 bytes --]
next prev parent reply other threads:[~2019-11-22 2:51 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-11-16 16:27 [PATCH] Display extra headers for emacs-mua - db config option Johan Parin
2019-11-16 16:35 ` Tomi Ollila
2019-11-16 16:53 ` Johan Parin
2019-11-21 2:48 ` Daniel Kahn Gillmor
2019-11-21 12:16 ` David Bremner
2019-11-21 18:29 ` Johan Parin
2019-11-21 21:56 ` Johan Parin
2019-11-22 2:51 ` Daniel Kahn Gillmor [this message]
2019-11-22 17:46 ` Carl Worth
2019-11-21 12:27 ` David Bremner
2019-11-21 19:47 ` Daniel Kahn Gillmor
2019-11-21 21:38 ` Tomi Ollila
2019-11-22 2:43 ` moving the config into the database [was: Re: [PATCH] Display extra headers for emacs-mua - db config option] Daniel Kahn Gillmor
2019-12-08 16:47 ` Jorge P. de Morais Neto
2019-12-08 17:12 ` Jameson Graef Rollins
2019-12-08 18:19 ` Jorge P. de Morais Neto
2019-12-09 18:31 ` Daniel Kahn Gillmor
2019-12-10 12:46 ` Jorge P. de Morais Neto
2019-12-10 17:01 ` Daniel Kahn Gillmor
2019-12-12 11:59 ` Jorge P. de Morais Neto
2019-12-10 16:11 ` Jameson Graef Rollins
2019-12-11 10:53 ` David Edmondson
2019-12-11 14:00 ` David Bremner
2019-12-11 14:21 ` David Edmondson
2019-12-12 16:25 ` Daniel Kahn Gillmor
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=87lfs8ipyd.fsf@fifthhorseman.net \
--to=dkg@fifthhorseman.net \
--cc=johanparin@gmail.com \
--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).