Gnus development mailing list
 help / color / mirror / Atom feed
From: Tassilo Horn <tsdh@gnu.org>
To: Rainer M Krug <Rainer@krugs.de>
Cc: ding@gnus.org
Subject: Re: Snoozing a message in gnus?
Date: Fri, 07 Nov 2014 12:12:52 +0100	[thread overview]
Message-ID: <8761erw9fv.fsf@thinkpad-t440p.tsdh.org> (raw)
In-Reply-To: <m21tpfs8nu.fsf@krugs.de> (Rainer M. Krug's message of "Fri, 07 Nov 2014 09:43:17 +0100")

[-- Attachment #1: Type: text/plain, Size: 1499 bytes --]

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?

I don't think there is.  But it shouldn't be too hard to implement
something like that, e.g., simply by marking snoozed articles as dormant
immediately (so that they won't be expired in the meantime), and then as
unread + ticked when the "wakeup time" has arrived.

BTW, I'm looking for something similar.  I'd like to have a global group
that collects all articles I've ticked no matter which select method.  I
tried a virtual group with the regex "^.*$" and group parameter (display
. [tick]), but that's not exactly what I want:

  - It still contains all hundreds of unread messages (and gazillions of
    read ones) because the `display' parameter is only limiting in the
    summary buffer.  That is, when I want to enter it, I'm queried how
    many articles out of the existing millions I want to view.  Even if
    there is no unread article at all, I'm queried.  At least in that
    case I had expected to get quick access to all my ticked articles.

  - It's dead slow.  When exiting that group, it'll trigger expiry in
    all contained groups which is just, well, all my groups.

Bye,
Tassilo

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 212 bytes --]

  parent reply	other threads:[~2014-11-07 11:12 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 [this message]
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=8761erw9fv.fsf@thinkpad-t440p.tsdh.org \
    --to=tsdh@gnu.org \
    --cc=Rainer@krugs.de \
    --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).