From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: fancy splitting interactively
Date: Mon, 05 Jan 2015 22:34:15 +0800 [thread overview]
Message-ID: <87mw5x70uw.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <874ms54ddy.fsf@ucl.ac.uk>
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> On Sunday, 4 Jan 2015 at 11:12, Eric Abrahamsen wrote:
>
> [...]
>
>> 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.
>
> Indeed but it works well when you have more than one device
> (esp. phones) accessing the inbox, as you note later in your post, *and*
> if you have a Inbox 0 approach!
>
> My approach, when I use gnus splitting, is that I do not expect any
> emails in my INBOX once gnus has processed them. I do access emails on
> my phone frequently so I need those that have been read elsewhere split
> as well. In my case, *all* emails in my INBOX get split off to
> somewhere, whether to a special folder or to a "general" catch-all
> folder for emails that I cannot classify.
>
> I hope this makes sense...
Yeah, that definitely makes sense, and if you're willing to adopt the
no-messages-in-the-INBOX approach then it all works out quite nicely. I
still think someone clever should come up with a more certain solution
to the problem, though. Multiple devices -- like multiple email
addresses -- are becoming the norm rather than the exception, and in
both cases Gnus has a bit of catch-up to do...
next prev parent reply other threads:[~2015-01-05 14:34 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 [this message]
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=87mw5x70uw.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).