From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: still want Seen articles split...
Date: Thu, 09 Jan 2014 10:23:08 +0700 [thread overview]
Message-ID: <878uupsusj.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87r48ia47q.fsf@flea.lifelogs.com>
Ted Zlatanov <tzz@lifelogs.com> writes:
> On Tue, 7 Jan 2014 17:55:19 +0000 Eric S Fraga <e.fraga@ucl.ac.uk> wrote:
>
> ESF> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> ESF> [...]
>
>>> I can't really take it out of there, because IIUC that will resplit all
>>> the messages in INBOX every single time I sync, which would be bad.
>
> ESF> This would only be bad if splitting leaves messages in INBOX. My
> ESF> solution to this problem was to ensure that all emails are moved to
> ESF> other folders when splitting, leaving INBOX empty each time. For those
> ESF> emails that you would normally have left in INBOX, create a "general"
> ESF> folder and move them there.
>
> ESF> Alternatively, do the splitting on the server instead of in gnus.
>
> ESF> Both approaches can work -- I've done both and, in fact, currently use a
> ESF> combination of the two. On the server, I split those emails I would
> ESF> seldom, if ever, want to look at on a mobile device. Gnus splits all
> ESF> others, seen or not.
>
> I keep everything from one account in a single INBOX to keep it
> manageable with other tools, but another account is always split into
> folders. Both approaches make sense in context.
>
> I can't think of a good general solution, sorry. A gnus-seen flag would
> help but not in every situation.
Fair enough. Both approaches do make sense, and generally speaking
server-side splitting seems far the most reasonable thing to do. I only
wish Gmail supported bulk import of filters -- I'm pretty wedded to my
BBDB-based splitting.
Thanks,
Eric
next prev parent reply other threads:[~2014-01-09 3:23 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-05 13:15 Eric Abrahamsen
2014-01-06 22:25 ` Ted Zlatanov
2014-01-07 3:23 ` Eric Abrahamsen
2014-01-07 17:55 ` Eric S Fraga
2014-01-08 15:22 ` Ted Zlatanov
2014-01-09 3:23 ` Eric Abrahamsen [this message]
2014-01-09 3:36 ` Eric Abrahamsen
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=878uupsusj.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).