From: Glenn Morris <rgm@gnu.org>
To: Richard Copley <rcopley@gmail.com>
Cc: 13730@debbugs.gnu.org
Subject: bug#13730: 24.3.50; Diff from Bzr-Log-View not highlighted
Date: Sun, 17 Feb 2013 01:36:41 -0500 [thread overview]
Message-ID: <20768.31353.425536.985964@gnu.org> (raw)
In-Reply-To: <CAPM58ohKAudLVMs2YLtpF5DLAyFqVJR8Bv_iYg30+GDy1OBuWA@mail.gmail.com>
Please keep the debbugs address cc'd.
Richard Copley wrote (on Sun, 17 Feb 2013 at 03:35 +0000):
> > Do you mean that font-locking should be enabled in the *vc-diff* buffer?
> > If so, it is for me. (Try bootstrapping?)
>
> That is what I mean, yes. Curious. Did you follow the recipe from
> "emacs -Q"? Not all *vc-diff* buffers are affected.
Yes. Works for me.
> >> The trunk revision in which this stopped working is in (111784,11794].
>
> Make that (111793,111794]. Revision 111794 introduces a new feature
> in "easy-mmode.el" that allows major mode functions to disable
> global minor modes by explicitly turning off the corresponding minor
> mode. Unfortunately font-lock gets turned off in a
> change-major-mode-hook function (font-lock-change-mode in
> "font-core.el"), which doesn't seem to have been anticipated.
>
> I can't say I understand why this doesn't cause
> global-font-lock-mode to be disabled in all major modes in all
> circumstances. It could be a question of whether
> font-lock-change-mode or global-font-lock-mode-enable-in-buffers is
> earlier in change-major-mode-hook.
prev parent reply other threads:[~2013-02-17 6:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-16 12:10 bug#13730: 24.3.50; Diff from Bzr-Log-View not highlighted rcopley
2013-02-17 1:16 ` Glenn Morris
[not found] ` <CAPM58ohKAudLVMs2YLtpF5DLAyFqVJR8Bv_iYg30+GDy1OBuWA@mail.gmail.com>
2013-02-17 3:38 ` Richard Copley
2013-02-17 5:27 ` Richard Copley
2013-02-17 6:40 ` Glenn Morris
2013-02-19 22:04 ` Richard Copley
2013-02-19 22:07 ` Glenn Morris
2013-02-17 6:36 ` Glenn Morris [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
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=20768.31353.425536.985964@gnu.org \
--to=rgm@gnu.org \
--cc=13730@debbugs.gnu.org \
--cc=rcopley@gmail.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 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).