From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: add a gnus-summary-pipe-output-default-command variable
Date: Thu, 10 Jul 2008 17:56:10 +0900 [thread overview]
Message-ID: <b4mlk0aruc5.fsf@jpl.org> (raw)
In-Reply-To: <kztzeyx6ap.fsf@kafka.physik3.gwdg.de>
>>>>> David Engster wrote:
> The command `gnus-summary-save-in-pipe' does not work for me
> anymore. This is due to the change from `gnus-article-buffer' to
> `gnus-save-article-buffer' in l.3965 in gnus-art.el. For example, if I
> do something like
> (gnus-summary-save-in-pipe "bogofilter -v -n")
> in the summary buffer, I get an error because gnus-save-article-buffer
> is nil:
I forgot to try running `g-s-save-in-pipe' independently, sorry.
The cause is that I changed the buffer `gnus-article-buffer' to
`gnus-save-article-buffer' (in which there are article contents)
so that a raw article may also be piped. I'll fix it soon.
next prev parent reply other threads:[~2008-07-10 8:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-06-29 18:42 jidanni
2008-06-30 0:35 ` Katsumi Yamaoka
2008-07-01 16:01 ` jidanni
2008-07-02 11:47 ` Katsumi Yamaoka
2008-07-09 18:26 ` David Engster
2008-07-10 8:56 ` Katsumi Yamaoka [this message]
2008-07-10 23:59 ` Katsumi Yamaoka
2008-07-11 7:45 ` David Engster
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=b4mlk0aruc5.fsf@jpl.org \
--to=yamaoka@jpl.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).