unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Chong Yidong <cyd@stupidchicken.com>
Cc: emacs-devel@gnu.org
Subject: Re: hi-lock mode and special buffers
Date: Thu, 24 Nov 2005 11:05:53 -0500	[thread overview]
Message-ID: <87psoqav4u.fsf@stupidchicken.com> (raw)
In-Reply-To: <87ek563ytf.fsf@pacem.orebokech.com> (Romain Francoise's message of "Thu, 24 Nov 2005 15:28:12 +0100")

Romain Francoise <romain@orebokech.com> writes:

> This change:
>
> 2005-11-12  Chong Yidong  <cyd@stupidchicken.com>
>
> 	* hi-lock.el (hi-lock-mode): Set the default value of
> 	font-lock-defaults.
>
> breaks fontification in special buffers if hi-lock mode is enabled.
> This affects Gnus and ERC, among others; see Bill's report about Gnus
> (<9993.1131326507@olgas.newt.com>) and the following Debian bug:
>
>     <URL: http://bugs.debian.org/339920>
>
> What was this change supposed to fix?  Is there a better way?

The bug is "No highlight in compilation-minor-mode when hi-lock-mode
is on", at

http://lists.gnu.org/archive/html/emacs-pretest-bug/2005-11/msg00173.html

The old behavior of hi-lock mode is that it sets the
font-lock-defaults to '(nil) when it is turned on.  However,
font-lock-defaults is buffer-local, so the value for other buffers is
unchanged, even though hi-lock-mode applies to them as well.  That was
the source of the incompatibility with compilation-minor-mode.

  reply	other threads:[~2005-11-24 16:05 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-11-24 14:28 hi-lock mode and special buffers Romain Francoise
2005-11-24 16:05 ` Chong Yidong [this message]
2005-11-24 18:16   ` Romain Francoise
2005-11-24 16:36 ` Chong Yidong
2005-11-24 18:03   ` Chong Yidong
2005-11-24 18:21     ` Romain Francoise
2005-11-24 18:17   ` Romain Francoise

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87psoqav4u.fsf@stupidchicken.com \
    --to=cyd@stupidchicken.com \
    --cc=emacs-devel@gnu.org \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).