From: KGreiner@xpediantsolutions.com
Subject: Re: gnus-summary-highlight should use overlays?
Date: Tue, 10 Dec 2002 12:15:02 -0600 [thread overview]
Message-ID: <ur8cp3fmh.fsf@XS8200-1.i-did-not-set--mail-host-address--so-tickle-me> (raw)
In-Reply-To: <87adjd4wo0.fsf@wesley.springies.com>
Alan Shutko <ats@acm.org> writes:
> Because of the gnus-agent-downloaded-article-face overriding other
> summary highlights, I was wondering if perhaps gnus-summary-highlight
> should use overlays (on Emacs, at least) instead of text properties
> for the face. That way, we could have one overlay for each entry in
> gnus-summary-highlight which matches, and the resultant face would be
> the composition of the matching faces. I presume XEmacs could do the
> same thing, somehow.
>
> How does that sound?
Just to let you know, I've already rewritten this code to address
feedback from other users. The code is ready for check-in, just
waiting for some feedback on a couple of private questions.
The changes and the concerns that they address are:
1) The current gnus-agent-downloaded-article-face currently displays
when an article was fetched. The new agent article face will be
applied when an article has NOT been fetched. The idea being
that the fetched status should be fairly low priority.
2) The gnus-agent-downloaded-article-face stepped on the
high/normal/low score faces. There are actually three new agent
article faces. They provide the same high/normal/low score
indicator as usual with a background color indicating that the
articles have not been fetched.
Will this help with the overriding problem that you are seeing?
Kevin
next prev parent reply other threads:[~2002-12-10 18:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-10 17:21 Alan Shutko
2002-12-10 18:15 ` KGreiner [this message]
2002-12-10 18:34 ` Alan Shutko
2002-12-11 4:36 ` kgreiner
2002-12-28 18:09 ` Lars Magne Ingebrigtsen
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=ur8cp3fmh.fsf@XS8200-1.i-did-not-set--mail-host-address--so-tickle-me \
--to=kgreiner@xpediantsolutions.com \
/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).