From: Tassilo Horn <tassilo@member.fsf.org>
To: ding@gnus.org
Subject: Re: gnus-extra-headers and gnus-summary-limit-to-extra
Date: Tue, 31 Mar 2009 08:41:08 +0200 [thread overview]
Message-ID: <87d4byfb3v.fsf@thinkpad.tsdh.de> (raw)
In-Reply-To: <m2ab72hin9.fsf_-_@boostpro.com> (David Abrahams's message of "Mon, 30 Mar 2009 16:15:22 -0400")
David Abrahams <dave@boostpro.com> writes:
Hi David,
>> Anyway, you should be able to limit to the message-id using `/ h
>> Message-Id: <regexp>'.
>
> Cool, thanks. But why doesn't this work with gnus-extra-headers?
You can limit to headers in `gnus-extra-headers' using `/ x'. This will
give you a completion prompt for the available extra headers, too.
Bye,
Tassilo
prev parent reply other threads:[~2009-03-31 6:41 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-24 20:32 nnimap and sticky cache David Abrahams
2009-03-24 21:04 ` Tassilo Horn
2009-03-25 1:33 ` David Abrahams
2009-03-25 7:46 ` Tassilo Horn
2009-03-25 10:48 ` David Engster
2009-03-28 19:50 ` David Abrahams
2009-03-29 17:30 ` Tassilo Horn
2009-03-30 20:15 ` gnus-extra-headers and gnus-summary-limit-to-extra (was: nnimap and sticky cache)? David Abrahams
2009-03-31 6:41 ` Tassilo Horn [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=87d4byfb3v.fsf@thinkpad.tsdh.de \
--to=tassilo@member.fsf.org \
--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).