From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: ding@gnus.org
Subject: Re: Fixed bug with custom marks in registry
Date: Fri, 16 Nov 2018 16:32:49 -0800 [thread overview]
Message-ID: <87wopch7bi.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <871s7xwkgv.fsf@ericabrahamsen.net>
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
> Michael Heerdegen <michael_heerdegen@web.de> writes:
>
>> Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>>
>>> TBH I hadn't even looked into this part of the code before you brought
>>> it up last time, so I'm not really ahead of you in this game. I think in
>>> principle it would be nice to have a higher-level, more user-friendly
>>> way of adjusting this behavior. I could certainly imagine using an
>>> option that let me say "always display any message that has registry
>>> keys marked "precious"".
>>
>> Yeah, something like that would be nice.
>
> I'll put that on the list of things to consider!
Right now the thing that makes the most sense to me is:
1. Make a new group parameter that matches the "display" parameter that
you can set for individual groups. Ie, we'd have a
`gnus-parameter-display-alist' variable.
2. Allow that parameter to take more than just a number to display: it
should be a list, and allow pre-set symbols (like 'registry-marked,
'registry-precious), and maybe functions? I haven't thought it all
the way through.
3. Consult that parameter when constructing Summary buffers.
How's that sound?
Eric
next prev parent reply other threads:[~2018-11-17 0:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-11 18:26 Eric Abrahamsen
2018-10-11 18:44 ` Emanuel Berg
2018-10-11 21:00 ` Ted Zlatanov
2018-11-06 0:54 ` Michael Heerdegen
2018-11-06 4:56 ` Michael Heerdegen
2018-11-06 6:01 ` Eric Abrahamsen
2018-11-06 23:33 ` Michael Heerdegen
2018-11-07 5:00 ` Eric Abrahamsen
2018-11-17 0:32 ` Eric Abrahamsen [this message]
2018-11-17 15:01 ` Michael Heerdegen
2018-11-19 23:51 ` 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=87wopch7bi.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).