From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: add a gnus-summary-pipe-output-default-command variable
Date: Wed, 02 Jul 2008 20:47:52 +0900 [thread overview]
Message-ID: <b4mtzf8ecd3.fsf@jpl.org> (raw)
In-Reply-To: <87hcb9mw4i.fsf@jidanni.org>
>>>>> jidanni@jidanni.org wrote:
> I see. Also please document gnus-last-shell-command in Info, for users
> who just want a first default if there is none yet. Thanks.
I considered using of `gnus-last-shell-command' for setting the
default (or the initial) command by a user, but reached the
conclusion that it is better to provide options individually for
the features (as you suggested). Currently those are pipe and
muttprint. So, `gnus-last-shell-command' is still an internal
variable and I think it is not worth being mentioned in Info.
Now you can use `gnus-summary-pipe-output-default-command' for
`gnus-summary-pipe-output' (and `gnus-summary-save-in-pipe') as
well as `gnus-summary-muttprint-program' for
`gnus-summary-pipe-to-muttprint'.
BTW, I've fixed some bugs in relation to the saving articles
features:
1. The functions set to `gnus-default-article-saver' can't be
controlled by the `:headers' property.
cf. (info "(gnus)Saving Articles")
2. The 2nd argument HEADERS passed to `gnus-summary-pipe-output'
is not effective.
3. `gnus-summary-pipe-output' and `gnus-summary-save-in-pipe'
always pass decoded articles to the pipe.
The last one might not be a bug but I believe there must be
demand of piping raw articles to a shell command. The default
behavior is unchanged.
Regards,
next prev parent reply other threads:[~2008-07-02 11:47 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 [this message]
2008-07-09 18:26 ` David Engster
2008-07-10 8:56 ` Katsumi Yamaoka
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=b4mtzf8ecd3.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).