Gnus development mailing list
 help / color / mirror / Atom feed
From: Juliusz Chroboczek <jec@dcs.ed.ac.uk>
Subject: How *not* to highlight
Date: 08 Oct 1996 20:51:47 +0100	[thread overview]
Message-ID: <dh3pw2tw7xo.fsf@calvay.dcs.ed.ac.uk> (raw)

Hello,

I was thinking how to keep Gnus from highlighting when some face stuff
has already been done, e.g. by a MIME decoder.  The problem is that if
the preprocessor changed some faces, then the Gnus highlighting
functions will just undo its work.

What I currently do is to check in the function
gnus-article-maybe-highlight whether

   (text-property-not-all (point-min) (point-max) 'face nil)

in the article buffer.  If it is the case, no highlighting is done.

Of course, this is not the right approach.  This means that if a face
has been changed, say, in the body of the article, then neither the
headers nor the signature will be highlighted.  Furthermore, it does
not inhibit spurious highlighting in the summary buffer.

I've thought about doing a similar check in the function
`gnus-add-text-properties', but then any function that sets text
faces would have to make sure that those will not be overridden
later.  Or should I add a function `gnus-set-text-face', which would
be called by all the highlighting functions?

By the way, I believe that this modification should find its way into
the distribution of Gnus.  It does not cost much, and as highlighting
is only there for esthetics, a preprocessor should be able to override
it.

Just if you're interested: I need this for some character set support
that I've added to TM and RMIME.  Feel free to browse

    http://www.dcs.ed.ac.uk/home/jec/charset/


                                        J. Chroboczek


             reply	other threads:[~1996-10-08 19:51 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1996-10-08 19:51 Juliusz Chroboczek [this message]
1996-10-08 22:23 ` Per Abrahamsen
1996-10-09 18:14   ` Juliusz Chroboczek
1996-10-10 22:30 ` 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=dh3pw2tw7xo.fsf@calvay.dcs.ed.ac.uk \
    --to=jec@dcs.ed.ac.uk \
    /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).