From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eric Abrahamsen <eric@ericabrahamsen.net>
Cc: Michael Heerdegen <michael_heerdegen@web.de>, info-gnus-english@gnu.org
Subject: Re: Highlight process-marked files in Gnus summary?
Date: Tue, 19 May 2020 15:47:43 +0200 [thread overview]
Message-ID: <87zha4ox34.fsf@gnus.org> (raw)
In-Reply-To: <87o8qlw8vs.fsf@ericabrahamsen.net> (Eric Abrahamsen's message of "Mon, 18 May 2020 08:38:47 -0700")
Eric Abrahamsen <eric@ericabrahamsen.net> writes:
>> The obvious goal is to get a better overview of what is marked before I
>> e.g. delete the articles. It's too easy to make a mistake with only
>> those little # marks around. Ideally the used face would specify a
>> background color (like hl-line) so it doesn't interfere with the stuff
>> in `gnus-summary-highlight'.
>
> I haven't ever looked at the summary-highlight code, but would it be
> hard to add another entry in there, call it `process', to specifically
> target the process mark?
I don't think that's necessary? Can't you just add highlighting based
on pretty much anything in the highlighting code? (It's been a while
since I looked at it...)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
_______________________________________________
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-05-19 13:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-18 2:42 Michael Heerdegen
2020-05-18 15:38 ` Eric Abrahamsen
2020-05-19 13:47 ` Lars Ingebrigtsen [this message]
2020-05-19 23:13 ` Michael Heerdegen
2020-05-22 13:00 ` Lars Ingebrigtsen
2021-07-25 20:08 ` Roland Winkler
2021-07-25 22:16 ` Michael Heerdegen
2021-07-26 2:26 ` Roland Winkler
2021-07-27 0:47 ` Michael Heerdegen
2021-07-25 22:20 ` 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=87zha4ox34.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=eric@ericabrahamsen.net \
--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).