From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Romain Francoise <romain@orebokech.com>
Cc: ding@gnus.org
Subject: Re: gnus-summary-pipe-output doesn't work for two or more articles
Date: Wed, 30 Jul 2008 09:04:42 +0900 [thread overview]
Message-ID: <b4mtze8me3p.fsf@jpl.org> (raw)
In-Reply-To: <b4mmyk1wplc.fsf_-_@jpl.org>
>>>>>> Romain Francoise wrote:
>> Hi Katsumi,
>> I think this change introduces a regression: it used to be possible
>> to process-mark several articles and then run a shell command on
>> them (in my case I often run `sa-learn --spam' on misclassified
>> messages). Now I get the following error:
>>| Debugger entered--Lisp error: (error "Selecting deleted buffer")
>>| gnus-summary-save-article(nil t)
>>| gnus-summary-pipe-output(nil nil)
>>| call-interactively(gnus-summary-pipe-output nil nil)
>> Note that I didn't try to reverse it to make sure that your change
>> is really the problem, but it looks likely. WDYT?
>>>>> Katsumi Yamaoka wrote:
> That's exactly due to my changes. Thanks for finding it. I'll
> fix it ASAP. Maybe `gnus-summary-pipe-output' needs to be
> restructured to work in closer cooperation with
> `gnus-summary-save-in-pipe'.
Done.
In addition to this fix, I've enabled `gnus-summary-pipe-output'
to pipe raw articles by specifying the symbolic prefix `r'. Try:
M-i r |
Regards,
next prev parent reply other threads:[~2008-07-30 0:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1KE0oC-0000R1-00@quimby.gnus.org>
[not found] ` <87tzeaju3k.fsf@elegiac.orebokech.com>
2008-07-28 23:34 ` gnus-summary-pipe-output doesn't work for two or more articles (was Re: Changes committed gnus/lisp (ChangeLog gnus-art.el gnus-sum.el)) Katsumi Yamaoka
2008-07-30 0:04 ` Katsumi Yamaoka [this message]
2008-08-08 17:45 ` gnus-summary-pipe-output doesn't work for two or more articles Romain Francoise
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=b4mtze8me3p.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=romain@orebokech.com \
/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).