From: Reiner Steib <4.uce.03.r.s@nurfuerspam.de>
Subject: Re: headers argument in gnus-summary-pipe-output is ignored
Date: Sun, 04 Jan 2004 16:37:38 +0100 [thread overview]
Message-ID: <v9r7yfsp19.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m365fu3r0w.fsf@quimbies.gnus.org>
On Fri, Jan 02 2004, Lars Magne Ingebrigtsen wrote:
> 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...
Hm. With my patch (see below), when I did `M-i a | xless RET' it
worked as expected (headers are included). But then, it always
included them, also with a simple `|'. Dunno why. I don't really
understand the code.
Bye, Reiner.
--8<---------------cut here---------------start------------->8---
--- gnus-art.el.~6.380.~ Wed Dec 31 17:27:37 2003
+++ gnus-art.el Sat Jan 3 21:05:19 2004
@@ -3279,7 +3279,8 @@
(if gnus-last-shell-command
(setq command gnus-last-shell-command)
(error "A command is required")))
- (gnus-eval-in-buffer-window gnus-article-buffer
+ (gnus-eval-in-buffer-window (or gnus-save-article-buffer
+ gnus-article-buffer)
(save-restriction
(widen)
(shell-command-on-region (point-min) (point-max) command nil)))
--8<---------------cut here---------------end--------------->8---
--
,,,
(o o)
---ooO-(_)-Ooo--- PGP key available via WWW http://rsteib.home.pages.de/
next prev parent reply other threads:[~2004-01-04 15:37 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
2004-01-04 15:37 ` Reiner Steib [this message]
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=v9r7yfsp19.fsf@marauder.physik.uni-ulm.de \
--to=4.uce.03.r.s@nurfuerspam.de \
--cc=reiner.steib@gmx.de \
/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).