From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: Colin Baxter <m43cap@yandex.com>
Cc: ding@gnus.org
Subject: Re: gnus-extra-headers
Date: Thu, 02 Sep 2021 15:12:43 -0700 [thread overview]
Message-ID: <87sfymy6ck.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87sfyohftb.fsf@yandex.com> (Colin Baxter's message of "Wed, 01 Sep 2021 09:15:44 +0100")
Colin Baxter <m43cap@yandex.com> writes:
> Hello,
>
> If emacs (tested with 27.2 and 28.0.50) is launched with -Q (or
> gnus-extra-headers has not been set explicitly by the user) then the
> variable gnus-extra-headers has the value:
>
> gnus-extra-headers is a variable defined in ‘gnus-sum.el’.
> Its value is
> (X-Diary-Time-Zone X-Diary-Dow X-Diary-Year X-Diary-Month X-Diary-Dom X-Diary-Hour X-Diary-Minute To Cc Keywords Gcc Newsgroups X-GM-LABELS)
> Original value was
> (To Cc Keywords Gcc Newsgroups X-GM-LABELS)
>
> You can customize this variable.
>
>
> This variable was introduced, or its default value was changed, in
> version 25.1 of Emacs.
>
> Documentation:
> Extra headers to parse.
>
> The X-Diary settings seem to come from nndiary.el, but there is nothing
> in the doc-string to indicate this.
>
> Is this a bug? Is not the "Original value" of gnus-extra-headers incorrect?
I don't think it's really a bug. If you don't use the nndiary backend,
those headers don't get added to `gnus-extra-headers', and it has its
"original value" as noted in *Help*. I don't think there's any contract
that says additional libraries can't manipulate the value of
customization options... is there?
next prev parent reply other threads:[~2021-09-02 22:13 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-01 8:15 gnus-extra-headers Colin Baxter
2021-09-02 22:12 ` Eric Abrahamsen [this message]
2021-09-03 5:42 ` gnus-extra-headers Colin Baxter
2021-09-03 18:30 ` gnus-extra-headers Eric Abrahamsen
2021-09-04 14:39 ` gnus-extra-headers Colin Baxter
2021-09-04 15:15 ` gnus-extra-headers Eric Abrahamsen
2021-09-05 8:36 ` gnus-extra-headers Colin Baxter
2021-09-06 3:31 ` gnus-extra-headers Eric Abrahamsen
2021-09-06 7:14 ` gnus-extra-headers Colin Baxter
2021-09-06 8:37 ` gnus-extra-headers Colin Baxter
2021-09-06 16:15 ` gnus-extra-headers Eric Abrahamsen
2021-09-06 16:29 ` gnus-extra-headers Colin Baxter
2021-09-06 17:39 ` gnus-extra-headers Eric Abrahamsen
2021-09-06 19:33 ` gnus-extra-headers Colin Baxter
2021-09-06 17:16 ` gnus-extra-headers Stephen Berman
2021-09-06 18:40 ` gnus-extra-headers Eric Abrahamsen
2021-09-07 5:53 ` gnus-extra-headers Colin Baxter
2021-09-07 18:56 ` gnus-extra-headers Eric Abrahamsen
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87sfymy6ck.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=ding@gnus.org \
--cc=m43cap@yandex.com \
/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.
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 NNTP newsgroup(s).