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:13:12 +0800	[thread overview]
Message-ID: <87d28ubi2v.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87ioim3a24.fsf@gmail.com>

Trevor Murphy <trevor.m.murphy@gmail.com> writes:

> On Mon, Nov 10 2014, Ted Zlatanov wrote: 
>
>> The registry could update those groups with a glowing indicator
>> light or something :)
>
> Whoa, I hadn't seen the registry before.  That looks like a fairly
> heavyweight solution, but since it'll work with nnimap and nntp out of
> the box, I figure it's worth starting there.
>
> Looks like I want a command that marks the article dormant, prompts
> for a delay like how `gnus-delay-article' does, then sets an
> appropriate value under a registry "snooze" key.
>
> Then I'll throw something in the demon or the get-new-news hook to
> iterate over articles in the registry with a "snooze" key and mark
> them ticked + unread if the date is past.
>
> The manual says there's a built-in registry inverse map that'll let me
> look up all messages matching a particular set of criteria. Is this
> referring to `registry-search'?  Or should I be trying to use
> `gnus-registry-find-keywords'?

Keywords are specifically used for adaptive word scoring;
`registry-search' is the one you want for finding arbitrary keys.




  reply	other threads:[~2014-11-11  2:13 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
2014-11-10 23:33           ` Trevor Murphy
2014-11-11  2:13             ` Eric Abrahamsen [this message]
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=87d28ubi2v.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).