From: Lars Magne Ingebrigtsen <larsi@gnus.org>
Subject: Re: headers argument in gnus-summary-pipe-output is ignored
Date: Fri, 02 Jan 2004 23:49:19 +0100 [thread overview]
Message-ID: <m365fu3r0w.fsf@quimbies.gnus.org> (raw)
In-Reply-To: <v9n0btflfr.fsf@marauder.physik.uni-ulm.de>
Reiner Steib <4.uce.03.r.s@nurfuerspam.de> writes:
> according to the doc-string, `M-: (gnus-summary-pipe-output 1 t) RET'
> should pipe the current article to a command, _including_ the headers:
[...]
> | If HEADERS (the symbolic prefix), include the headers, too.
[...]
> The following patch fixes this. But I'm not sure if it's the
> best/correct fix. Comments?
Well, it should take the symbolic prefix into account...
--
(domestic pets only, the antidote for overdose, milk.)
larsi@gnus.org * Lars Magne Ingebrigtsen
next prev parent reply other threads:[~2004-01-02 22:49 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-10-22 13:31 Reiner Steib
2004-01-02 22:49 ` Lars Magne Ingebrigtsen [this message]
2004-01-04 15:37 ` Reiner Steib
2004-01-04 20:43 ` Lars Magne Ingebrigtsen
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=m365fu3r0w.fsf@quimbies.gnus.org \
--to=larsi@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).