Gnus development mailing list
 help / color / mirror / Atom feed
From: Lloyd Zusman <ljz@asfast.com>
Subject: Re: Which gnus variable(s) control the over-colorizing of messages?
Date: Tue, 01 Jan 2002 11:35:54 -0500	[thread overview]
Message-ID: <m2zo3y58r9.fsf@asfast.com> (raw)
In-Reply-To: <vafelld1ymw.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Sat, 29 Dec 2001 22:53:43 +0100")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Lloyd Zusman <ljz@asfast.com> writes:
>
>> Recently I had a system crash when my gnus session was up and running.
>> After restarting my system and re-entering gnus (fairly recent Oort),
>> the message highlighting behavior has become excessive.  This only
>> occurs when I'm in message mode (i.e., composing or replying to a
>> message), at which time I get the "fruit salad" look for the message
>> headers, quoted lines, etc.  The messages look just fine when I'm
>> reading them in article mode.
>
> Gnus uses font-lock for message mode, whereas it uses the
> gnus-treat-* variables for displaying articles.

Thanks.  Making some font-lock changes among my customizations fixed
the problem.  But now, what I'm mystified about is why I had the
problem to begin with.  I hadn't upgraded Gnus or XEmacs or any elisp
packages, and I can't find any files that were corrupted by the system
crash.


-- 
 Lloyd Zusman
 ljz@asfast.com



      reply	other threads:[~2002-01-01 16:35 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-12-29 15:44 Lloyd Zusman
2001-12-29 21:14 ` Lars Magne Ingebrigtsen
2001-12-29 21:53 ` Kai Großjohann
2002-01-01 16:35   ` Lloyd Zusman [this message]

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=m2zo3y58r9.fsf@asfast.com \
    --to=ljz@asfast.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).