From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Graham Murray <graham@gmurray.org.uk>
Cc: ding@gnus.org
Subject: Re: gnus-summary-save-in-pipe does not pipe raw article
Date: Sat, 19 Jul 2008 20:19:43 +0900 [thread overview]
Message-ID: <b4msku62ka8.fsf@jpl.org> (raw)
In-Reply-To: <87mykes2g8.fsf@newton.gmurray.org.uk>
[-- Attachment #1: Type: text/plain, Size: 579 bytes --]
>>>>> In <87mykes2g8.fsf@newton.gmurray.org.uk>
>>>>> Graham Murray <graham@gmurray.org.uk> wrote:
> Until recently, following the example in the documentation I was able to
> "report" spam articles using spamassassin using the function
> (defun my-gnus-raze-spam ()
> "Invoke SpamAssassin reporting , then mark it as expirable."
> (interactive)
> (gnus-summary-show-raw-article)
> (gnus-summary-save-in-pipe "spamassassin -r")
> (gnus-summary-mark-as-expirable 1))
> Now using the latest cvs of ngnus, the raw article is not sent to the
> pipe.
Try this instead:
[-- Attachment #2: Type: application/emacs-lisp, Size: 376 bytes --]
[-- Attachment #3: Type: text/plain, Size: 135 bytes --]
;; cf. (info "(gnus)Saving Articles")
Or if you use `gnus-summary-save-in-pipe' for only this feature
simply you can do as follows:
[-- Attachment #4: Type: application/emacs-lisp, Size: 271 bytes --]
[-- Attachment #5: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2008-07-19 11:19 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-07-19 8:28 Graham Murray
2008-07-19 11:19 ` Katsumi Yamaoka [this message]
2008-07-22 23:11 ` Katsumi Yamaoka
2008-07-23 7:22 ` Gabor Z. Papp
2008-07-23 7:54 ` Katsumi Yamaoka
2008-07-23 7:59 ` Gabor Z. Papp
2008-07-24 15:08 ` Dan Christensen
2008-07-25 0:15 ` Katsumi Yamaoka
2008-07-25 8:25 ` Lloyd Zusman
2008-07-25 9:16 ` Katsumi Yamaoka
2008-07-26 11:23 ` Gabor Z. Papp
2008-07-23 20:17 ` Reiner Steib
2008-07-23 20:24 ` Graham Murray
2008-07-24 15:29 ` Ted Zlatanov
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=b4msku62ka8.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=graham@gmurray.org.uk \
/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).