Announcements and discussions for Gnus, the GNU Emacs Usenet newsreader
 help / color / mirror / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Eric Abrahamsen <eric@ericabrahamsen.net>,  info-gnus-english@gnu.org
Subject: Re: Highlight process-marked files in Gnus summary?
Date: Fri, 22 May 2020 15:00:37 +0200	[thread overview]
Message-ID: <874ks8qg3u.fsf@gnus.org> (raw)
In-Reply-To: <87ftbvy0vw.fsf@web.de> (Michael Heerdegen's message of "Wed, 20 May 2020 01:13:07 +0200")

Michael Heerdegen <michael_heerdegen@web.de> writes:

> I would suggest to at least do the following:
>
> (1) Provide an `article' variable.  Maybe also provide `processable' as
> suggested and/or `sec-mark' (somewhere in the code the process mark is
> called a "secondary mark")?

I think everything that's not a readedness mark is a secondary mark
(like % and the like).

> (2) make the docstring of `gnus-summary-highlight' say that arbitrary
> expressions are allowed, and that they are evaluated with point
> positioned on the according article's line.
>
> For (1), AFAIU two places would need to be changed:
> `gnus-summary-highlight-line' and `gnus-tree-highlight-node'.  Seems to
> be simple to do.

Sounds good to me -- patches welcome.  :-)


_______________________________________________
info-gnus-english mailing list
info-gnus-english@gnu.org
https://lists.gnu.org/mailman/listinfo/info-gnus-english

  reply	other threads:[~2020-05-22 13:01 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 [this message]
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=874ks8qg3u.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).