From: Roland Winkler <winkler@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,
Michael Heerdegen <michael_heerdegen@web.de>,
info-gnus-english@gnu.org
Subject: Re: Highlight process-marked files in Gnus summary?
Date: Sun, 25 Jul 2021 15:08:21 -0500 [thread overview]
Message-ID: <87fsw2upfu.fsf@gnu.org> (raw)
In-Reply-To: <87zha4ox34.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 19 May 2020 15:47:43 +0200")
On Tue, May 19 2020, Lars Ingebrigtsen wrote:
> 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...)
I found this old thread. Could it make sense to have a minor mode that
puts the `invisible' text property on all lines without process-mark?
I have in mind a use case different from Michael who started this thread:
Often I deal with threads that evolve (magically) such that they become
recognized as multiple threads. In such a case the process-mark can
help to "collect" all threads on a topic. Or are there better solutions
for this?
_______________________________________________
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:[~2021-07-25 20:38 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
2020-05-19 23:13 ` Michael Heerdegen
2020-05-22 13:00 ` Lars Ingebrigtsen
2021-07-25 20:08 ` Roland Winkler [this message]
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=87fsw2upfu.fsf@gnu.org \
--to=winkler@gnu.org \
--cc=eric@ericabrahamsen.net \
--cc=info-gnus-english@gnu.org \
--cc=larsi@gnus.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).