Gnus development mailing list
 help / color / mirror / Atom feed
From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Subject: Re: Limit summary to participant
Date: Mon, 30 Sep 2002 15:51:38 +0200	[thread overview]
Message-ID: <vafptuvy49h.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: <hhwup3sry1.fsf@blah.pl> (Maciej Matysiak's message of "Mon, 30 Sep 2002 12:16:38 +0200")

Maciej Matysiak <phoner.ding@blah.pl> writes:

> On the 30th of September 2002 at 12:01, Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) wrote:
>
>> You can add To and Cc to nnmail-extra-headers and gnus-extra-headers.
>
> what's the difference between nnmail-extra-headers and gnus-extra-headers?
> for both 'c-h v' says: extra headers to parse. are they redundant?

nnmail-extra-headers means to insert them into the overview/NOV data
for nnml and nnfolder (and other backends supporting NOV).

gnus-extra-headers means, I think, to extract them from the
overview/NOV data when present.  Also, some backends don't have NOV
and so this variable means (I think) to extract them from the headers.

For example, if your NNTP server provides some headers as extra
headers, then you don't need nnmail-extra-headers.

But indeed, there is great overlap in their use, so maybe they should
be unified.  Opinions?

kai
-- 
~/.signature is: umop ap!sdn    (Frank Nobis)



      parent reply	other threads:[~2002-09-30 13:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-30  9:02 Nicolas Kowalski
2002-09-30 10:01 ` Kai Großjohann
2002-09-30 11:05   ` Nicolas Kowalski
2002-09-30 13:52     ` Kai Großjohann
2002-09-30 13:58       ` Nicolas Kowalski
2002-10-02  4:08     ` Dan Christensen
2002-10-02  7:19       ` Nicolas Kowalski
     [not found]   ` <hhwup3sry1.fsf@blah.pl>
2002-09-30 13:51     ` Kai Großjohann [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=vafptuvy49h.fsf@lucy.cs.uni-dortmund.de \
    --to=kai.grossjohann@cs.uni-dortmund.de \
    /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).