From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: feature proposal gnus-summary-limit-to-registry
Date: Thu, 03 Aug 2017 16:01:17 -0400 [thread overview]
Message-ID: <87d18ca0aa.fsf@lifelogs.com> (raw)
In-Reply-To: <87k28hgpi5.fsf@mat.ucm.es>
On Thu, 23 Feb 2017 10:39:30 +0000 Uwe Brauer <oub@mat.ucm.es> wrote:
UB> I am starting to use the registry which seems nice, however want is
UB> missing to make it more useful is a function like
UB> gnus-summary-limit-to-registry
UB> To display only those message which have a registry label.
I think the limiting functions require the data to be fetched as
essential or extra headers, so it's not trivial, but should be possible.
Another potential use case is scoring.
Ted
prev parent reply other threads:[~2017-08-03 20:01 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-23 10:39 Uwe Brauer
2017-08-03 20:01 ` Ted Zlatanov [this message]
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=87d18ca0aa.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).