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: Wed, 07 Jan 2015 09:28:30 +0800	[thread overview]
Message-ID: <87fvbnwf9d.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87y4pfeqe2.fsf@ucl.ac.uk>

Eric S Fraga <e.fraga@ucl.ac.uk> writes:

> On Tuesday,  6 Jan 2015 at 09:25, Eric Abrahamsen wrote:
>
> [...]
>
>> The multiple device problem is trickier. The idea of Gnus-specific marks
>> was floated, and Lars was also talking about something called "Gnus
>> Cloudy" which might also address this. It's not an area I'm very
>> familiar with, and I guess I don't know what the best solution is...
>
> I am not sure what the problem is?  Gnus handles marks understood by
> other MUAs properly, as far as I can tell.

The OP was talking about the fact that, by default, Gnus won't split
read messages. So if you've read it on your phone or whatever, it won't
get split. Unless you do the zero INBOX thing.

> My annoyance is that server side splitting is incredibly clumsy (in my
> experience) compared with gnus's fancy splitting capabilities and so I
> hate having to read emails on other devices with having split anything.

No argument here! 

> Of course, once the emails have been processed once by gnus, I can
> access all the appropriate folders on other devices (assuming IMAP, of
> course).
>
> So, again, my view is that other MUAs need to catch up...
>
> Am I missing something?




  parent reply	other threads:[~2015-01-07  1:28 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 [this message]
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=87fvbnwf9d.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).