Gnus development mailing list
 help / color / mirror / Atom feed
From: Jens Lautenbacher <jens@metrix.de>
Cc: Lars Magne Ingebrigtsen <larsi@ifi.uio.no>
Subject: Re: Group highlighting
Date: 01 Mar 1997 02:58:54 +0100	[thread overview]
Message-ID: <m3hgiwpe3l.fsf@jens.metrix.de> (raw)
In-Reply-To: Lars Magne Ingebrigtsen's message of 01 Mar 1997 01:01:24 +0100

Lars Magne Ingebrigtsen <larsi@ifi.uio.no> writes:

> Jens Lautenbacher <jens@lemming0.lem.uni-karlsruhe.de> writes:
> 
> > There seem to be some inconsitencies with the way groups lines are
> > highlighted. 
[blurb] 
> > The problem is that first a) is done and then, if it is selected, b).
> > But b) overwrites any (face) changes done by a).
> 
> Yes, this is a problem.  Uhm.  The fontification done by A can't be
> done after B, since it's actually done while inserting the text.
> Uhm.  Well, perhaps the `gnus-group-highlight-line' should be
> rewritten to be done before inserting anything in the buffer, so that
> we know what the default face is supposed to be before inserting any
> of the text?  I don't know whether that's workable...

Why not doing it the way I suggested: Introduce another spec for the
gnus-group-format-line which, if present, will limit the area
gnus-group-highlight-line will work on. This could be achived by
inserting an extent spanning the area with a special property, say
'do-highlight-here set. Gnus-group-highlight-line only needs to be
changed to 1) check if such an extent is present here. If not, proceed
as before. 2) If it is, highlight only the area that covers this
extent.

If I would know how to define another spec , say something along the
line %&{ ..... %} (this is not present already, is it?) I would do
this, but unfortunately I didn't really understand that part from a
quick glance...

      JTL


  reply	other threads:[~1997-03-01  1:58 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-02-27 15:59 Jens Lautenbacher
1997-03-01  0:01 ` Lars Magne Ingebrigtsen
1997-03-01  1:58   ` Jens Lautenbacher [this message]
1997-03-01  3:20     ` 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=m3hgiwpe3l.fsf@jens.metrix.de \
    --to=jens@metrix.de \
    --cc=jens@lemming0.lem.uni-karlsruhe.de \
    --cc=larsi@ifi.uio.no \
    /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).