Mercurial > hg > xemacs-beta

comparison lisp/startup.el @ 5384:3889ef128488

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
Fix misspelled words, and some grammar, across the entire source tree. See xemacs-patches message with ID <AANLkTi=edkEKtK3pZ60ytsG5pTJQy2TjAEVCZCLOa-oA@mail.gmail.com>.
author Jerry James <james@xemacs.org>
date Thu, 24 Mar 2011 11:00:11 -0600
parents 5efbd1253905
children 4dee0387b9de
comparison
equal deleted inserted replaced
5383:294ab9180fad 5384:3889ef128488
769 ;; however, and any font locking that is ever put in place is done as 769 ;; however, and any font locking that is ever put in place is done as
770 ;; a result of `font-lock-set-defaults' being in find-file-hook and 770 ;; a result of `font-lock-set-defaults' being in find-file-hook and
771 ;; various other places. We could make *scratch* honour the user's 771 ;; various other places. We could make *scratch* honour the user's
772 ;; choice of whether font-locking is in place by adding a call to 772 ;; choice of whether font-locking is in place by adding a call to
773 ;; font-lock-set-defaults in `lisp-interaction-mode'; but that'll 773 ;; font-lock-set-defaults in `lisp-interaction-mode'; but that'll
774 ;; break if `intial-major-mode' is anything else. 774 ;; break if `initial-major-mode' is anything else.
775 ;; 775 ;;
776 ;; So, despite what `font-lock-set-defaults'' docstring says, this 776 ;; So, despite what `font-lock-set-defaults'' docstring says, this
777 ;; *is* where we should call it to have the user's choice of font-lock 777 ;; *is* where we should call it to have the user's choice of font-lock
778 ;; level take effect in *scratch*. If the modes are rewritten to do 778 ;; level take effect in *scratch*. If the modes are rewritten to do
779 ;; the right then, we're okay too, the function is idempotent. 779 ;; the right then, we're okay too, the function is idempotent.