unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Herbert Valerio Riedel <hvr@gnu.org>
To: notmuch@notmuchmail.org
Subject: Re: [BUG] Custom headers in `notmuch-message-headers` are broken
Date: Sat, 20 Apr 2024 11:07:39 +0200	[thread overview]
Message-ID: <34ebe1878d09507efed0414eb47f4aff.hvr@gnu.org> (raw)
In-Reply-To: <875yovgmfd.fsf@tethera.net>


>> The end result is that `notmuch-message-headers` variable has no effect.

> Not sure if you are still interested, but this should be fixed in
> notmuch 0.35 (see show.extra_headers in notmuch-config(1)).

I just stumbled over this issue when trying to add "Message-Id" to the
list of shown messages as the docstring of the custom variable
definition in 'notmuch-show.el' didn't mention that I needed to tweak my
config or that only a small subset of headers might be supported:

--8<---------------cut here---------------start------------->8---
(defcustom notmuch-message-headers '("Subject" "To" "Cc" "Date")
  "Headers that should be shown in a message, in this order.

For an open message, all of these headers will be made visible
according to `notmuch-message-headers-visible' or can be toggled
with `notmuch-show-toggle-visibility-headers'. For a closed message,
only the first header in the list will be visible."
  :type '(repeat string)
  :group 'notmuch-show)
--8<---------------cut here---------------end--------------->8---

I suggest adding a hint there that tweaking 'show.extra_headers' might
be necessary.

      reply	other threads:[~2024-04-20  9:08 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 11:47 [BUG] Custom headers in `notmuch-message-headers` are broken Jan Malakhovski
2017-12-26 12:34 ` David Bremner
2018-07-16 21:51   ` Amin Bandali
2018-07-26  4:33     ` David Bremner
2018-07-26  6:46       ` Jan Malakhovski
2018-07-26  6:55         ` David Bremner
2018-10-20  5:09         ` Leo Gaspard
2022-03-03 14:06 ` David Bremner
2024-04-20  9:07   ` Herbert Valerio Riedel [this message]

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=34ebe1878d09507efed0414eb47f4aff.hvr@gnu.org \
    --to=hvr@gnu.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).