emacs-diffs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[Emacs-diffs] Changes to emacs/lisp/font-core.el


From: Stefan Monnier
Subject: [Emacs-diffs] Changes to emacs/lisp/font-core.el
Date: Wed, 14 Aug 2002 20:36:26 -0400

Index: emacs/lisp/font-core.el
diff -c emacs/lisp/font-core.el:1.9 emacs/lisp/font-core.el:1.10
*** emacs/lisp/font-core.el:1.9 Fri Aug  9 08:15:54 2002
--- emacs/lisp/font-core.el     Wed Aug 14 20:36:26 2002
***************
*** 290,296 ****
  ;; hook is run, the major mode is in the process of being changed and we do 
not
  ;; know what the final major mode will be.  So, `font-lock-change-major-mode'
  ;; only (a) notes the name of the current buffer, and (b) adds our function
! ;; `turn-on-font-lock-if-enabled' to the hook variables `find-file-hooks' and
  ;; `post-command-hook' (for buffers that are not visiting files).  By the time
  ;; the functions on the first of these hooks to be run are run, the new major
  ;; mode is assumed to be in place.  This way we get a Font Lock function run
--- 290,296 ----
  ;; hook is run, the major mode is in the process of being changed and we do 
not
  ;; know what the final major mode will be.  So, `font-lock-change-major-mode'
  ;; only (a) notes the name of the current buffer, and (b) adds our function
! ;; `turn-on-font-lock-if-enabled' to the hook variables `find-file-hook' and
  ;; `post-command-hook' (for buffers that are not visiting files).  By the time
  ;; the functions on the first of these hooks to be run are run, the new major
  ;; mode is assumed to be in place.  This way we get a Font Lock function run




reply via email to

[Prev in Thread] Current Thread [Next in Thread]