all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lawrence Mitchell <wence@gmx.li>
To: "Sean B. Palmer" <sean@miscoranda.com>
Cc: 3628@emacsbugs.donarmstrong.com
Subject: bug#3628: Python-Mode Ignores Global Font Lock
Date: Mon, 22 Jun 2009 10:10:30 +0100	[thread overview]
Message-ID: <?fnord?y3h6my80vdkp.fsf@ID-97657.user.individual.net> (raw)
In-Reply-To: <b6bb4d890906200846we88800am193aa9f70a4267d1@mail.gmail.com> (Sean B. Palmer's message of "Sat, 20 Jun 2009 16:46:58 +0100")

Sean B. Palmer wrote:
> In my .emacs file I turn off global font lock:

>    (global-font-lock-mode 0)

[...]

> In emacs 23.0.95.1 (build details below), this no longer works for
> Python files. That is to say, various *.py files that I've tested have
> syntax highlighting ON when I edit them in emacs with a normal
> command:

>    $ emacs example.py
>    $ emacs api.py

> Perl and C files have syntax highlighting OFF, on the other hand. When
> editing one of the Python files, syntax highlighting can be turned OFF
> by using the following procedure:

>    M-x eval-expression <RET>
>    (global-font-lock-mode 0) <RET>

> In other words, by evaluating the expression from my .emacs file
> manually. On repeating the expression, syntax highlighting remains
> OFF, so it is apparently not acting as a toggle.

(global-font-lock-mode 0) only turns /off/ font lock

| With prefix arg, turn Global-Font-Lock mode on if and only if
| arg is positive.

I.e., it's not acting as a toggle, but this is intended.

[...]

The overriding of user preference regarding font lock appears to
be a deliberate change.  A commit on Feb 21 2008 merges changes
from Dave Love's python.el.

| Author: Chong Yidong <cyd@stupidchicken.com>
| Date:   Thu Feb 21 17:03:47 2008 +0000

|     Merge from Dave Love's 2008-01-20 version.

These include:

|     (python-mode): Add python-pea-hook to pre-abbrev-expand-hook.  Use
|     symbol-completion-try-complete for hippie expansion.  Turn on font
|     lock unconditionally.

Font-lock is used unconditionally in python buffers, I think, so
that text properties marking strings and comments can be
maintained with greater ease than otherwise.  It appears to be a
design decision.

Cheers,
Lawrence
-- 
Lawrence Mitchell <wence@gmx.li>





  reply	other threads:[~2009-06-22  9:10 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-20 15:46 bug#3628: Python-Mode Ignores Global Font Lock Sean B. Palmer
2009-06-22  9:10 ` Lawrence Mitchell [this message]
2009-06-22 10:00   ` Sean B. Palmer

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='?fnord?y3h6my80vdkp.fsf@ID-97657.user.individual.net' \
    --to=wence@gmx.li \
    --cc=3628@emacsbugs.donarmstrong.com \
    --cc=sean@miscoranda.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.