From: asjo@koldfront.dk (Adam Sjøgren)
To: ding@gnus.org
Subject: Re: fancy splitting interactively
Date: Sat, 03 Jan 2015 15:48:24 +0100 [thread overview]
Message-ID: <87tx07j4xz.fsf@topper.koldfront.dk> (raw)
In-Reply-To: <87fvbs6u4k.fsf@mat.ucm.es>
Uwe writes:
> How can I run this splitting on the INBOX for all messages even read
> ones?
You can always mark the relevant messages with # and then run B r on
them.
,----
| B r runs the command gnus-summary-respool-article, which is an
| interactive compiled Lisp function in `gnus-sum.el'.
|
| It is bound to B r, <menu-bar> <Article> <Copy, move,... (Backend)>
| <Respool article...>.
|
| (gnus-summary-respool-article &optional N METHOD)
|
| Respool the current article.
| The article will be squeezed through the mail spooling process again,
| which means that it will be put in some mail newsgroup or other
| depending on `nnmail-split-methods'.
| If N is a positive number, respool the N next articles.
| If N is a negative number, respool the N previous articles.
| If N is nil and any articles have been marked with the process mark,
| respool those articles instead.
|
| Respooling can be done both from mail groups and "real" newsgroups.
| In the former case, the articles in question will be moved from the
| current group into whatever groups they are destined to. In the
| latter case, they will be copied into the relevant groups.
`----
You can use B q on a message to see what splitting will do to it, if you
actually do B r on it.
,----
| B q runs the command gnus-summary-respool-query, which is an
| interactive compiled Lisp function in `gnus-sum.el'.
|
| It is bound to B q, <menu-bar> <Article> <Copy, move,... (Backend)>
| <Query respool>.
|
| (gnus-summary-respool-query &optional SILENT TRACE)
|
| Query where the respool algorithm would put this article.
`----
Best regards,
Adam
--
"Vegetarian progressive grindcore" Adam Sjøgren
asjo@koldfront.dk
next prev parent reply other threads:[~2015-01-03 14:48 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-03 10:22 Uwe Brauer
2015-01-03 10:39 ` Glyn Millington
2015-01-03 10:57 ` Eric S Fraga
2015-01-03 13:53 ` Eric Abrahamsen
2015-01-03 17:43 ` Uwe Brauer
2015-01-04 3:12 ` Eric Abrahamsen
2015-01-05 12:31 ` Eric S Fraga
2015-01-05 14:34 ` Eric Abrahamsen
2015-01-05 15:30 ` Eric S Fraga
2015-01-05 19:23 ` Adam Sjøgren
2015-01-06 1:25 ` Eric Abrahamsen
2015-01-06 5:35 ` Russ Allbery
2015-01-06 6:34 ` Eric Abrahamsen
2015-01-06 6:39 ` Russ Allbery
2015-01-06 7:27 ` Glyn Millington
2015-01-09 3:01 ` Eric Abrahamsen
2015-01-09 3:00 ` Eric Abrahamsen
2015-01-06 18:05 ` Eric S Fraga
2015-01-06 18:20 ` Eric S Fraga
2015-01-07 1:28 ` Eric Abrahamsen
2015-01-07 6:21 ` Julien Cubizolles
2015-01-07 10:12 ` Eric Abrahamsen
2015-01-14 10:27 ` Julien Cubizolles
2015-05-25 16:14 ` Julien Cubizolles
2015-01-07 19:46 ` Adam Sjøgren
2015-01-14 10:27 ` Julien Cubizolles
2015-01-03 14:48 ` Adam Sjøgren [this message]
2015-01-03 17:38 ` Uwe Brauer
2015-01-03 17:51 ` Adam Sjøgren
2015-01-03 22:49 ` Uwe Brauer
2015-01-04 14:56 ` [bug] (was: fancy splitting interactively) Uwe Brauer
2015-01-26 3:15 ` [bug] Lars Ingebrigtsen
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=87tx07j4xz.fsf@topper.koldfront.dk \
--to=asjo@koldfront.dk \
--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).