Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <>
Subject: Re: Displaying stuff from spamassassin headers in the summary buffer?
Date: Sun, 28 Jan 2024 06:39:25 -0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

Steinar Bang <> writes:

>>>>>> Andreas Schwab <>:
>> On Jan 28 2024, Steinar Bang wrote:
>>> Right now I have to do C-u g to see these headers in the raw message.
>> t runs the command gnus-summary-toggle-header (found in
>> gnus-summary-mode-map), which is an interactive byte-compiled Lisp
>> function in ‘gnus-sum.el’.
>> It is bound to t and W t.

There's also `gnus-visible-headers', if you want to always see the
result in the article buffer.

> When you say this, I think I actually knew this and had forgotten
> it... I wonder of how I landed on 'C-u g'?
> Maybe I was told the previous time I asked this quesetion? (I miss
> gmane's xapien search from 'G G'...)
> But anyway: what I really-really-want is to have spam-tagged articles be
> flagged, highlighted some way in the summary buffer by the spam score.
> I think the concensus the last time I was "no" since the spamassassin
> headers weren't in the set cached for use in the summary buffer, so the
> entire article must be loaded and parsed.

I believe you could add your desired header to the `gnus-extra-headers'
variable, and get it from there?

  reply	other threads:[~2024-01-28 14:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-27 23:02 Steinar Bang
2024-01-27 23:29 ` Andreas Schwab
2024-01-28  6:12   ` Steinar Bang
2024-01-28 14:39     ` Eric Abrahamsen [this message]
2024-01-28 22:15       ` Steinar Bang
2024-01-29  1:06         ` Dan Christensen
2024-01-29  1:22           ` 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:

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

  git send-email \ \ \ \

* 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).