How to write function to operate on marked articles?

How to write function to operate on marked articles?

[Svend Tollak Munkejord]

Hi,

I have the following function to tell Spamassassin that a message is spam:

(defun stm-spamassassin-spam ()
  (interactive)
  (gnus-summary-show-raw-article)
  (gnus-summary-save-in-pipe "sa-learn --spam");
  (gnus-summary-move-article 1 "nnmaildir:boss" nil nil))
; "boss" is Norwegian meaning "rubbish".

It only works on the current article. Is there a way I can modify this
function to operate on all marked articles in the Summary buffer, one at a
time?

Regards,
-- 
Svend Tollak Munkejord 

Re: How to write function to operate on marked articles?

[Frank Schmitt]

Svend Tollak Munkejord <stm+direct_reply@bacchus.pvv.org> writes:

> I have the following function to tell Spamassassin that a message is spam:
>
> (defun stm-spamassassin-spam ()
>   (interactive)
>   (gnus-summary-show-raw-article)
>   (gnus-summary-save-in-pipe "sa-learn --spam");
>   (gnus-summary-move-article 1 "nnmaildir:boss" nil nil))
> ; "boss" is Norwegian meaning "rubbish".
>
> It only works on the current article. Is there a way I can modify this
> function to operate on all marked articles in the Summary buffer, one at a
> time?

Yes, you can use the function gnus-summary-work-articles to get a list
of all process-marked articles. Have a look in
gnus-summary-move-article for an example. Remember to wrap the code in
(eval-after-load 'gnus-sum (...))

-- 
Did you ever realize how much text fits in eighty columns? If you now consider
that a signature usually consists of up to four lines, this gives you enough
space to spread a tremendous amount of information with your messages. So seize
this opportunity and don't waste your signature with bullshit nobody will read.

Re: How to write function to operate on marked articles?

[Svend Tollak Munkejord]

On 2004-03-16, Frank Schmitt <usereplyto2004@Frank-Schmitt.net> wrote:

> Svend Tollak Munkejord <stm+direct_reply@bacchus.pvv.org> writes:
>
>>> Remember to wrap the code in (eval-after-load 'gnus-sum (...))
>>
>> Is this necessary? It seemed to work without it...
>
> Well, you use a function defined in gnus-sum.el and when you haven't
> loaded gnus-sum.el when this part of .gnus is read, you'll run in an
> error.

OK, I see. Since I didn't get an error, there is probably something else in
my .gnus that "saved" me, then.

Regards,
-- 
Svend Tollak Munkejord