Gnus development mailing list
 help / color / mirror / Atom feed
From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Snoozing a message in gnus?
Date: Tue, 11 Nov 2014 10:27:41 +0800	[thread overview]
Message-ID: <87389qbheq.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87a943xj78.fsf@lifelogs.com>

Ted Zlatanov <tzz@lifelogs.com> writes:

> On Fri, 07 Nov 2014 19:04:57 +0800 Eric Abrahamsen <eric@ericabrahamsen.net> wrote: 
>
> EA> Rainer M Krug <Rainer@krugs.de> writes:
>>> some mail clients (add on for notmuch [1] or Mailbox [2]) have an
>>> interesting feature, namely snoozing messages, i.e. removing them
>>> temporarily from the inbox and having them returned after / at a certain time.
>>> 
>>> This would make scheduling to deal with emails much easier.
>>> 
>>> I was wondering - is there something similar possible in GNUS?
>
> EA> I would just capture the message to an Org TODO, and then schedule the
> EA> TODO for some time in the future. Instant snooze!
>
> That's pretty cool.  I want to offer that the Gnus registry could also
> store this information, for those that don't use Org.

FWIW, this is where I'm planning to take Gnorb[1]. Right now it store
correspondences between messages and Org TODOs using the registry, and
includes a dummy Gnus server for doing nnir searches. I'm planning on
fleshing out that server so that it has real groups: each group would
hold (virtual copies of) the messages associated with a certain Org
TODO. Each group would be created using the information stored in the
registry.

That way you could refresh these groups as you pleased, and see what
needed to be done for each TODO, or refresh the whole server and see
everything. Once I got to that point, it would be possible to make it
work even for people who aren't using Org: the "todo" information could
be solely stored in the registry.

Anyway, that's where that's headed.

Eric

[1]: https://github.com/girzel/gnorb




  reply	other threads:[~2014-11-11  2:27 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-07  8:43 Rainer M Krug
2014-11-07 11:04 ` Eric Abrahamsen
2014-11-07 12:56   ` Ted Zlatanov
2014-11-11  2:27     ` Eric Abrahamsen [this message]
2014-11-07 15:09   ` Rainer M Krug
2014-11-07 11:12 ` Tassilo Horn
2014-11-07 13:07   ` Xavier Maillard
2014-11-07 15:37   ` Trevor Murphy
2014-11-07 22:20     ` Peter Münster
2014-11-10 13:49     ` Ted Zlatanov
2014-11-10 13:59       ` Adam Sjøgren
2014-11-10 14:49         ` Rainer M Krug
2014-11-12  1:00           ` Dan Christensen
2014-12-08 16:59             ` Ted Zlatanov
2014-11-10 14:06       ` Tassilo Horn
2014-11-10 20:04         ` Ted Zlatanov
2014-11-10 22:26           ` Trevor Murphy
2014-11-11  1:23             ` Ted Zlatanov
2014-11-10 23:33           ` Trevor Murphy
2014-11-11  2:13             ` Eric Abrahamsen
2014-11-10 22:27         ` Trevor Murphy
2015-01-26  4:34 ` Lars Ingebrigtsen
2015-01-26  8:39   ` Rainer M Krug
2015-01-27  0:56     ` Lars Ingebrigtsen
2015-01-27  1:53       ` Eric Abrahamsen
2015-01-27  8:12         ` Rainer M Krug

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=87389qbheq.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).