GNU bug report logs -
#3628
Python-Mode Ignores Global Font Lock
Previous Next
Reported by: "Sean B. Palmer" <sean <at> miscoranda.com>
Date: Sat, 20 Jun 2009 15:55:04 UTC
Severity: normal
Merged with 4303
Found in version 23.1
Done: Stefan Monnier <monnier <at> iro.umontreal.ca>
Bug is archived. No further changes may be made.
Full log
Message #23 received at control <at> debbugs.gnu.org (full text, mbox):
close 3628
thanks
>>> (global-font-lock-mode 0) doesn't seem to work.
>> It should work. So please tell us the cases where it doesn't work, so
>> we can try and figure out where's the problem.
> M-x grep
OK, that one is a known problem: compile.el (used for M-x compile and
M-x grep) uses font-lock internally, so it forces font-lock to
be enabled.
> When I call (global-font-lock-mode 0) in my .emacs.el, python mode isn't
> font locked. But if I ever M-x python-shell, then files visited afterward
> will be font locked, even though global-ton-lock-mode's value is nil.
> At this point I have to restart emacs in order to see anything.
I'm not sure I understand why you see different results before and after
python-shell, but indeed I see that python.el incorrectly forces
font-lock-mode to be enabled in emacs-23. I've just installed a patch
which should fix it.
> Visit a binary file, the nonprintable ascii is colored.
This is not controlled by font-lock. IIUC this just unconditionally
receives the `escape-glyph' face, so you can only "turn it off" by
configuring this face.
> M-x compile
As mentioned above, this is the same issue as M-x grep. I hope we can
fix it for Emacs-24 (by making compile.el use syntax-propertize-function
rather than font-lock), but for Emacs-23 the only solution I can offer
is to configure the relevant faces so they look the same as default.
Stefan
This bug report was last modified 14 years and 140 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.