Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yagibdah.de>
To: ding@gnus.org
Subject: Re: storing messages into an mbox file
Date: Wed, 29 Apr 2015 21:32:00 +0200	[thread overview]
Message-ID: <878uda689b.fsf@heimdali.yagibdah.de> (raw)
In-Reply-To: <87y4lc10lt.fsf@igel.home> (Andreas Schwab's message of "Tue, 28 Apr 2015 22:03:58 +0200")

Andreas Schwab <schwab@linux-m68k.org> writes:

> lee <lee@yagibdah.de> writes:
>
>> how can I move messages into an mbox file (which I will use for
>> spamassassin to learn once there are enough messages in it)?
>
> O m runs the command gnus-summary-save-article-mail, which is an
> interactive compiled Lisp function in `gnus-sum.el'.
>
> It is bound to C-o, O m, <menu-bar> <Article> <Output> <Save in Unix mail
> format...>.
>
> (gnus-summary-save-article-mail &optional ARG)
>
> Append the current article to a Unix mail box file.
> If N is a positive number, save the N next articles.
> If N is a negative number, save the N previous articles.
> If N is nil and any articles have been marked with the process mark,
> save those articles instead.

Thank you!  It works, though it isn't too great because it's asking for
each and every article where to save it rather than saving all articles
that are marked with the process mark to the same file.  It also leaves
to delete the save articles afterwards.

Isn't there a better way to do this?


-- 
Again we must be afraid of speaking of daemons for fear that daemons
might swallow us.  Finally, this fear has become reasonable.



  reply	other threads:[~2015-04-29 19:32 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-04-28 19:03 lee
2015-04-28 20:03 ` Andreas Schwab
2015-04-29 19:32   ` lee [this message]
2015-04-29 20:10     ` Andreas Schwab
2015-04-29 20:37       ` this group and gnu.emacs.gnus (was: Re: storing messages into an mbox file) Emanuel Berg
2015-04-29 23:02       ` storing messages into an mbox file lee
2015-04-30  0:40         ` Eric Abrahamsen
2015-05-04  5:50           ` lee
2015-05-04  6:01             ` Adam Sjøgren
2015-05-07 23:11               ` lee
2015-05-08  9:22                 ` Adam Sjøgren
2015-05-09 14:49                   ` lee
2015-05-09 15:16                     ` Adam Sjøgren
2015-05-10 12:39                     ` Eric S Fraga
2015-05-12  8:06                       ` Steinar Bang
2015-05-12  9:04                         ` Eric S Fraga
2015-05-13 20:07                       ` lee
2015-05-13 21:48                         ` Adam Sjøgren
2015-05-17  8:46                           ` lee
2015-05-13 23:17                         ` Dan Christensen
2015-05-14  6:13                           ` Steinar Bang
2015-05-17  9:02                           ` lee
2015-05-14  6:10                         ` Steinar Bang
2015-05-17  9:06                           ` lee
2015-05-17 19:42                             ` Steinar Bang
2015-05-17 20:45                             ` Peter Münster
2015-05-14  9:19                         ` e.fraga
2015-05-17  9:40                           ` lee
2015-05-17 13:04                             ` Eric S Fraga
2015-05-04  6:07             ` Eric Abrahamsen
2015-05-07 23:14               ` lee
2015-04-30  9:47         ` Andreas Schwab
2015-05-04  5:45           ` lee
2015-05-07 23:53         ` Dan Christensen
2015-05-08 22:10           ` lee
2015-05-18  2:25     ` Nikolaus Rath

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=878uda689b.fsf@heimdali.yagibdah.de \
    --to=lee@yagibdah.de \
    --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).