From: Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann)
Cc: ding@gnus.org
Subject: Re: Using `gnus-extra-headers'
Date: 13 Feb 2000 16:39:59 +0100 [thread overview]
Message-ID: <vafzot5w1ps.fsf@lucy.cs.uni-dortmund.de> (raw)
In-Reply-To: Harry Putnam's message of "13 Feb 2000 06:37:37 -0800"
Harry Putnam <reader@newsguy.com> writes:
> Now I want to dispay in the visible headers, a home made "Keywords"
> header. Using the above approach doesn't display that header. I'm
> not interested in having this in Summary buffer format, but want to
> be able to use the `/ x' (limit to extra headers) on that (`Keywords: ')
> Header.
Adding the header to gnus-extra-headers does _not_ automatically
display it in the article buffer. See gnus-visible-headers and
gnus-ignored-headers for this.
You should be able to do `/ x' on the keywords header, though, if you
put it in gnus-extra-headers. Does that work?
kai
--
~/.signature: No such file or directory
next prev parent reply other threads:[~2000-02-13 15:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-13 14:37 Harry Putnam
2000-02-13 15:39 ` Kai Großjohann [this message]
[not found] ` <wtnwvo9w3xo.fsf@licia.dtek.chalmers.se>
2000-02-13 15:48 ` Harry Putnam
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=vafzot5w1ps.fsf@lucy.cs.uni-dortmund.de \
--to=kai.grossjohann@cs.uni-dortmund.de \
--cc=ding@gnus.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.
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).