From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 7771@debbugs.gnu.org
Subject: bug#7771: 23.1; can't turn off font-lock-mode globally
Date: Mon, 03 Jan 2011 20:01:48 +0200 [thread overview]
Message-ID: <83lj31oohf.fsf@gnu.org> (raw)
In-Reply-To: <0B9196567CAD40E6997D5EC3BF6386F2@us.oracle.com>
> From: "Drew Adams" <drew.adams@oracle.com>
> Cc: <rgm@gnu.org>, <7771@debbugs.gnu.org>
> Date: Mon, 3 Jan 2011 08:00:34 -0800
>
> > Users will not be deprived of anything, I think. The problem is that
> > these features turn font-lock on in the compilation buffer, which is a
> > nuisance (for those who turned it off).
>
> Good. But what was said was that "compile (and grep) require font-lock to
> work". That's what my comment responded to.
I understand, but I think the original comment was slightly
inaccurate. I think a more accurate statement would be
"compilation-mode needs font-lock to be turned on for its
functionality, so it turns it on unconditionally in the compilation
buffer." Here's the code from compilation-setup:
(set (make-local-variable 'font-lock-support-mode) nil)
(set (make-local-variable 'font-lock-maximum-size) nil)
(if minor
(let ((fld font-lock-defaults))
(font-lock-add-keywords nil (compilation-mode-font-lock-keywords))
(if font-lock-mode
(if fld
(font-lock-fontify-buffer)
(font-lock-change-mode)
(turn-on-font-lock))
(turn-on-font-lock)))
(setq font-lock-defaults '(compilation-mode-font-lock-keywords t))
;; maybe defer font-lock till after derived mode is set up
(run-mode-hooks 'compilation-turn-on-font-lock)))
and compilation-turn-on-font-lock is defined like this:
(defconst compilation-turn-on-font-lock 'turn-on-font-lock)
next prev parent reply other threads:[~2011-01-03 18:01 UTC|newest]
Thread overview: 47+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 19:17 bug#7771: 23.1; can't turn off font-lock-mode globally K. Richard Pixley
2011-01-02 22:56 ` Leo
2011-01-02 23:19 ` K. Richard Pixley
2011-01-03 8:48 ` Leo
2011-01-02 23:49 ` Stefan Monnier
2011-01-03 0:27 ` K. Richard Pixley
2011-01-03 3:55 ` Stefan Monnier
2011-01-03 5:57 ` Glenn Morris
2011-01-03 6:00 ` Glenn Morris
[not found] ` <mailman.4.1294035825.27854.bug-gnu-emacs@gnu.org>
2011-01-03 6:56 ` K. Richard Pixley
2011-01-03 8:13 ` Drew Adams
2011-01-03 16:42 ` Lennart Borgman
2011-01-03 17:29 ` Drew Adams
2011-01-03 17:32 ` Lennart Borgman
2011-01-03 17:40 ` Drew Adams
[not found] ` <mailman.1.1294073635.27149.bug-gnu-emacs@gnu.org>
2011-01-03 18:40 ` K. Richard Pixley
2011-01-03 19:52 ` Eli Zaretskii
2011-01-03 20:29 ` K. Richard Pixley
2011-01-03 20:39 ` Eli Zaretskii
2011-01-03 21:02 ` Lennart Borgman
2011-01-03 21:30 ` K. Richard Pixley
2011-01-03 22:04 ` Lennart Borgman
2011-01-03 22:14 ` K. Richard Pixley
[not found] ` <mailman.3.1294088031.614.bug-gnu-emacs@gnu.org>
2011-01-03 22:27 ` K. Richard Pixley
[not found] ` <mailman.1.1294028628.27854.bug-gnu-emacs@gnu.org>
2011-01-03 22:23 ` K. Richard Pixley
2011-01-04 4:05 ` Eli Zaretskii
2011-01-04 4:21 ` K. Richard Pixley
2011-01-03 0:29 ` K. Richard Pixley
2011-01-03 1:55 ` Glenn Morris
2011-01-03 3:21 ` Lennart Borgman
2011-01-03 13:04 ` Eli Zaretskii
[not found] ` <mailman.30.1294025024.15403.bug-gnu-emacs@gnu.org>
2011-01-03 4:10 ` K. Richard Pixley
2011-01-03 5:34 ` Stefan Monnier
2011-01-03 6:52 ` K. Richard Pixley
2011-01-03 8:13 ` Drew Adams
2011-01-03 13:43 ` Eli Zaretskii
2011-01-03 16:00 ` Drew Adams
2011-01-03 18:01 ` Eli Zaretskii [this message]
2011-01-03 18:09 ` Drew Adams
2011-01-03 18:26 ` Eli Zaretskii
[not found] ` <mailman.1.1294062865.25287.bug-gnu-emacs@gnu.org>
2011-01-03 18:38 ` K. Richard Pixley
[not found] ` <mailman.10.1294043026.27854.bug-gnu-emacs@gnu.org>
2011-01-03 18:33 ` K. Richard Pixley
[not found] ` <mailman.22.1294021456.15403.bug-gnu-emacs@gnu.org>
2011-01-03 4:14 ` K. Richard Pixley
2011-01-03 0:31 ` K. Richard Pixley
2011-01-03 1:20 ` K. Richard Pixley
2011-01-03 1:54 ` Glenn Morris
2011-01-03 2:08 ` Glenn Morris
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=83lj31oohf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=7771@debbugs.gnu.org \
--cc=drew.adams@oracle.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.