>>>>> jidanni@jidanni.org wrote:

> gnus-summary-pipe-output needs a
> gnus-summary-pipe-output-default-command variable, for users who find
> themselves mostly piping to the same command. It should be prompted as
> (Default: blabla) in the minibuffer, so one could just hit RET if OK.

> (P.S., currently if one does a second pipe, but first removes (DEL
> DEL...) the first command replay that one it prompted with, it indeed
> still does that same first command again. Kind of scary.)

Currently the default command that appears in the minibuffer is
the value held by the internal varable `gnus-last-shell-command'
when you invoked the `gnus-summary-pipe-output' command or the
`gnus-summary-muttprint' command previously.  There is the
`gnus-summary-muttprint-program' variable as a user option that
specifies the default command used by `gnus-summary-muttprint',
however it might be unfair that there is no such option for
`gnus-summary-pipe-output'.  Moreover, the command "muttprint"
will be suggested as the default command even if you invoke
`gnus-summary-pipe-output' if you've used `gnus-summary-muttprint'
previously.

The attached patch does:

1. Introduce `gnus-summary-pipe-output-default-command' which
   overrides `gnus-last-shell-command' if it is non-nil.
2. Make `gnus-summary-muttprint' not modify
   `gnus-last-shell-command'.  `gnus-summary-muttprint-program'
   itself holds the modified value.

A non-nil value of `gnus-summary-pipe-output-default-command'
always overrides `gnus-last-shell-command'.  So, my worry is that
one might forget having set it.  WDYT?  I'll commit the changes
if no one comments.