From: john.nospam@nospamassen.nospamdemon.co.uk (John McCabe)
Subject: Re: Enabling global-font-lock-mode
Date: Fri, 25 Oct 2002 09:42:17 GMT [thread overview]
Message-ID: <3db910eb.6104998@news.demon.co.uk> (raw)
In-Reply-To: ap9d09$cuo$07$1@news.t-online.com
On Thu, 24 Oct 2002 20:11:27 +0200, Florian Lindner
<Florian.Lindner@xgm.de> wrote:
>John McCabe wrote:
>
>> On Thu, 24 Oct 2002 17:39:29 +0200, Florian Lindner
>> <Florian.Lindner@xgm.de> wrote:
>>
>>>Hello,
>>>I want to enable Syntax Highlightning (Global font lock mode)
>>>Using this expression in my .emacs file is evaluated without errors but
>>>don't take effect. What's wrong?
>>>
>>>'(global-font-lock-mode t nil (font-lock))
>>
>> What version of Emacs are you using? If anything after 20.0, use the
>> "Customize" features to do it rather than edit your .emacs.
>>
>> It may be under the "Help" menu, or the "Options" menu. Find the
>> "Customize" menu, then "Specific Option" and enter
>> global-font-lock-mode when asked.
>
>I prefer to edit the .emacs directly, it's a greater learn effect and I
>don't like to use things that I don't understand.
Unfortunately it's also a greater risk that it won't work on future
versions! Customize is there to make things easier for you, it is
simple, generally reliable, and *should* be consistent. That can't be
said for hand-editing .emacs. If you really want to hand-edit .emacs,
use Customize instead then look at the difference when you set a
value.
In your original question you said you had added:
'(global-font-lock-mode t nil (font-lock))
Now, if that was somewhere within the
(custom-set-variables
...
)
block, it should have worked *unless* you had something hand-edited
elsewhere that switched it back off. If you just put that line in
outside the custom-set-variables block it isn't going to work.
next prev parent reply other threads:[~2002-10-25 9:42 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-10-24 15:39 Enabling global-font-lock-mode Florian Lindner
2002-10-24 15:43 ` Phillip Lord
2002-10-24 16:49 ` John McCabe
2002-10-24 18:11 ` Florian Lindner
2002-10-25 9:42 ` John McCabe [this message]
2002-10-25 14:27 ` Stefan Monnier <foo@acm.com>
[not found] ` <mailman.1035481346.8205.help-gnu-emacs@gnu.org>
2002-10-27 22:24 ` Tim Cross
[not found] ` <Florian.Lindner@xgm.de>
2002-10-24 17:40 ` Peter S Galbraith
2003-09-25 17:00 ` Obtaining 21.3 Peter S Galbraith
-- strict thread matches above, loose matches on Subject: below --
2003-09-18 7:56 Florian Lindner
2003-09-18 8:52 ` ray
[not found] ` <mailman.381.1063875673.21628.help-gnu-emacs@gnu.org>
2003-09-18 11:19 ` Martin Jost
2003-09-18 12:37 ` Uwe Siart
2003-09-18 16:07 ` Kevin Rodgers
2003-09-19 12:39 ` Martin Jost
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=3db910eb.6104998@news.demon.co.uk \
--to=john.nospam@nospamassen.nospamdemon.co.uk \
/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.
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).