From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: Snoozing a message in gnus?
Date: Mon, 10 Nov 2014 20:23:10 -0500 [thread overview]
Message-ID: <87fvdqedj5.fsf@lifelogs.com> (raw)
In-Reply-To: <874mu666bf.fsf@gmail.com>
On Mon, 10 Nov 2014 17:26:12 -0500 Trevor Murphy <trevor.m.murphy@gmail.com> wrote:
TM> On Mon, Nov 10 2014, Ted Zlatanov wrote:
>> But as far as moving messages, if Gnus supported Gmail's labels, we
>> could just apply a "Later" label to the message. It doesn't seem too
>> hard:
>> https://developers.google.com/gmail/imap_extensions#access_to_gmail_labels_x-gm-labels
TM> What features of Gmail labels are you missing?
You can have more than one per message :)
>> The registry could update those groups with a glowing indicator
>> light or something :)
TM> Whoa, I hadn't seen the registry before. That looks like a fairly
TM> heavyweight solution, but since it'll work with nnimap and nntp out of
TM> the box, I figure it's worth starting there.
TM> Looks like I want a command that marks the article dormant, prompts
TM> for a delay like how `gnus-delay-article' does, then sets an
TM> appropriate value under a registry "snooze" key.
TM> Then I'll throw something in the demon or the get-new-news hook to
TM> iterate over articles in the registry with a "snooze" key and mark
TM> them ticked + unread if the date is past.
TM> The manual says there's a built-in registry inverse map that'll let me
TM> look up all messages matching a particular set of criteria. Is this
TM> referring to `registry-search'? Or should I be trying to use
TM> `gnus-registry-find-keywords'?
registry.el is the generic DB, while gnus-registry.el uses it. So I
would use gnus-registry functions if possible, implementing new ones as
needed, to avoid unnecessary coupling to the underlying registry.el
implementation (which can and probably will change when we have FFI in
Emacs :)
Your plan seems good to me. Maybe you want to synchronize with Eric
Abrahamsen who was looking at fixing up some registry issues?
Ted
next prev parent reply other threads:[~2014-11-11 1:23 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
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 [this message]
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=87fvdqedj5.fsf@lifelogs.com \
--to=tzz@lifelogs.com \
--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).