From: raphael.berbain@free.fr (Raphaël Berbain)
Subject: Re: gnus-summary-pipe-output and headers
Date: Wed, 30 Jun 2004 17:08:21 +0200 [thread overview]
Message-ID: <86fz8dytg9.fsf@ID-110038.user.uni-berlin.de> (raw)
In-Reply-To: <87eko2bp4l.fsf@peti.cryp.to>
Peter Simons <simons@cryp.to> writes:
> Hi,
>
> is there any way to make 'gnus-summary-pipe-output' (a.k.a.
> 'O p' in the *Summary* buffer) include _all_ headers into
> the message, regardless of which headers I was seeing in the
> *Article* buffer when I issued to command?
>
> I tried setting
>
> '(gnus-save-all-headers t)
>
> ..., but that didn't change 'gnus-summary-pipe-output'
> behavior at all. So I set
>
> '(gnus-show-all-headers t)
>
> ..., which does the trick, but has the side-effect that I,
> well, see all headers all the time -- which is not what I
> originally wanted either.
Actually, my guess is that (depending on your setup) it doesn't really
do what you want either (meaning if it does, you are lucky): It
includes 'pseudo' headers (I don't know how to call them..) - here I
get extraneous X-Sent & X-Boundary headers.
> Any ideas anyone?
In my spam reporting function, I use:
(gnus-summary-show-raw-article)
(gnus-summary-save-in-pipe "command")
prev parent reply other threads:[~2004-06-30 15:08 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-26 10:16 Peter Simons
[not found] ` <864qoynjax.fsf@rumba.de.uu.net>
2004-06-26 21:43 ` Peter Simons
[not found] ` <86eko18f63.fsf@rumba.de.uu.net>
2004-06-27 10:50 ` Peter Simons
2004-06-30 15:08 ` Raphaël Berbain [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=86fz8dytg9.fsf@ID-110038.user.uni-berlin.de \
--to=raphael.berbain@free.fr \
/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).