Gnus development mailing list
 help / color / mirror / Atom feed
From: Dan Christensen <jdc@uwo.ca>
To: ding@gnus.org
Subject: Re: Snoozing a message in gnus?
Date: Tue, 11 Nov 2014 20:00:29 -0500	[thread overview]
Message-ID: <87mw7x6xn6.fsf@uwo.ca> (raw)
In-Reply-To: <m2mw7zyusw.fsf@krugs.de>

Rainer M Krug <Rainer@krugs.de> writes:

> Snoozing should work on all (probably except nntp as it is read only?)
> backends. But what about the approach which Mailbox is using,
> i.e. moving the messages from the inbox into another folder (called "Later"?), and storing
> metadata (which folder the message is from, when it is due, ...) in the
> registry? The querying of the registry could be timed (every x minutes),
> and when due, the message could be moved back to it's original location.
>
> The advantage of this approach is that snoozed messages can also be
> checked from other mail programs (I am thinking about an imap backend
> for gmail), although only with missing information on due dates / times.

I like this idea, at least as an option, precisely so that the messages
would also appear "snoozed" when viewed with other IMAP clients (like
cell phones).

I also like the idea of storing the snooze information in a header when
possible.  This *can* be done with nnimap, which can edit messages by
deleting the old one and creating a new one.  And if you are already
copying the message to another folder, the header could be added at
the same time.

The registry has some auto-pruning features, which always makes me
worried about storing important information there.

Dan




  reply	other threads:[~2014-11-12  1:00 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
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 [this message]
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=87mw7x6xn6.fsf@uwo.ca \
    --to=jdc@uwo.ca \
    --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).