Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: fancy splitting interactively
Date: Sun, 04 Jan 2015 11:12:54 +0800	[thread overview]
Message-ID: <87k313utl5.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <877fx37ob9.fsf@mat.ucm.es>

Uwe Brauer <oub@mat.ucm.es> writes:

>>> "Eric" == Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>
>    > Eric S Fraga <e.fraga@ucl.ac.uk> writes:
>    >> On Saturday,  3 Jan 2015 at 11:22, Uwe Brauer wrote:
>>> How can I run this splitting on the INBOX for all messages even read
>>> ones?
>    >> 
>    >> Possibly:
>    >> 
>    >> ,----[ C-h v nnimap-unsplittable-articles RET ]
>    >> | nnimap-unsplittable-articles is a variable defined in `nnimap.el'.
>    >> | Its value is (%Deleted %Seen)
>    >> | 
>    >> | Documentation:
>    >> | Articles with the flags in the list will not be considered when splitting.
>    >> | 
>    >> | This is a Gnus server variable.  See Info node `(gnus)Select Methods'.
>    >> | 
>    >> | [back]
>    >> `----
>
>    > Yup, this is what I've done in the past and it works a treat. Just set
>    > it to (%Deleted) temporarily, then refresh.
>
> Thanks for pointing this variable out to me, I see that it is not
> customize-able via customize, so I have to use:
>
>
> (setq nnimap-unsplittable-articles '(%Deleted))
>
> By refresh you mean 
> gnus-group-get-new-news??

Yes, any entry point into the "fetch new news" process will run the
splitting routine.

I think the idea is that you aren't really meant to run Gnus regularly
without the %Seen flag in that variable. That means (as far as I
understand it) that *every* time you get new news, *all* of your
existing messages will be run through the splitting process again. That
could be heavy, though to be honest when I've done this in the past I
don't remember it taking nearly as long as I thought it would.

What's meant to happen is that *unseen* messages are split once, on
their way in, and then left where they are.

It's been noted on this list that this can produce unwanted results if
you're accessing your mail from several devices, and some other device
marks a message as read before Gnus gets to it -- that way Gnus won't
know to split it. I'm not sure what the proper solution is there, but I
still don't think it's running day-to-day with %Seen removed from
`nnimap-unsplittable-articles'.

Eric




  reply	other threads:[~2015-01-04  3:12 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 [this message]
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
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=87k313utl5.fsf@ericabrahamsen.net \
    --to=eric@ericabrahamsen.net \
    --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).