From: physiculus <physiculus@gmail.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: gnus <info-gnus-english@gnu.org>
Subject: Re: gnus-registry-marks; Any chance to search or filter for?
Date: Mon, 13 Jul 2020 19:52:32 +0200 [thread overview]
Message-ID: <87y2nnnvz3.fsf@googlemail.com> (raw)
In-Reply-To: <87imet4m88.fsf@web.de> (Michael Heerdegen's message of "Sun, 12 Jul 2020 02:21:11 +0200")
Michael Heerdegen <michael_heerdegen@web.de> writes:
Thanks for this information!
Thats sad...
So i understand it correct, that is not clear, if it will be work in the
near future ?
Is there any other solution to tag mails in gnus?
With this i will be able, to filter for these tags or search for.
But i only have little hope after reading your infos ...
Regards
Poul
> physiculus <physiculus@gmail.com> writes:
>
>> Hello,
>> thank you for this info. I thought, that no one on this list (full of
>> poeple with gnus knowledge) did try it or care about it.
>
> These registry marks were more or less broken until a year or so (they
> disappeared after restarting Emacs. That has been fixed after I had
> tried them and complained.
>
> So view people use it (nobody else complained for a long time), but now
> they at least work. Integration into the rest of Gnus is only
> rudimentary.
>
>> But unfortunately i do not understand what you mean, because i'm not a
>> developer and have very little knowledge about elisp.
>>
>> Could you please explain, what you mean with this code snippet?
>> I can't see a function to call or interactive run in minibuffer.
>
> No, sorry, that was just to give you a start for implementing a function
> or command yourself. The snipped shows how to extract a list of
> registry marked messages from the registry database. Not more.
>
> I guess I could implement what you want, but I'm short on time. BTW,
> what exactly do you mean by "filter" (maybe the "/" prefixed limiting
> commands?) and "search" (the search articles commands from the summary
> buffer, or something from the group buffer)?
>
>
> Regards,
>
> Michael.
_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english
next prev parent reply other threads:[~2020-07-13 17:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-24 12:04 physiculus
2020-07-10 23:40 ` Michael Heerdegen
[not found] ` <87o8om9dew.fsf@googlemail.com>
[not found] ` <87imet4m88.fsf@web.de>
2020-07-13 17:52 ` physiculus [this message]
2020-07-14 15:08 ` Michael Heerdegen
2020-07-14 16:12 ` Eric Abrahamsen
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=87y2nnnvz3.fsf@googlemail.com \
--to=physiculus@gmail.com \
--cc=info-gnus-english@gnu.org \
--cc=michael_heerdegen@web.de \
/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).