From: Tim Cross <tcross@nospam.une.edu.au>
Subject: Re: Enabling global-font-lock-mode
Date: 28 Oct 2002 09:24:51 +1100 [thread overview]
Message-ID: <874rb7ldu4.fsf@blind-bat.une.edu.au> (raw)
In-Reply-To: mailman.1035481346.8205.help-gnu-emacs@gnu.org
Peter S Galbraith <GalbraithP@dfo-mpo.gc.ca> writes:
> Florian Lindner <Florian.Lindner@xgm.de> wrote:
>
> > '(global-font-lock-mode t nil (font-lock))
>
> The proper syntax is:
>
> (global-font-lock-mode t)
>
> Or more simply select it from the Options menu (it's the first item) and
> then select "Save Options" from that same menu.
>
Just thought I'd point out that to me the line which the original
poster reported looks ver much like the exact line you get in your
customize variables section if you use the menu option to turn
on global font lock mode. The alternative suggestions are what you use
if you just like doing your own .emacs file rather than use customize.
Personally, I like ot use a mix of both - I've found problems with
just using customize if you do a lot of customization - for example
with emacs 21, if I do extensive customization of face attributes via
customize, I lose the ability to change font sizes/types via the
Shift-Mouse-1 menu. However, if I either use X resources or
set-face-attribute, I don't get these problems.
I also think its easy to get burnt trying to translate settings from
the custom variable/face section to just a standard .emacs
setting. For example, the font-lock setting mentioned above and have a
look at the difference between setting auto-fill-mode via customize
and how it is described in the documentation or FAQ on how to do it
just in your .emacs.
I guess the thing to be careful about is to make sure you read the
documentation regarding some feature and its customization and don't
just expect you can cut lines from the customize variables/faces
section and just drop them in a function, variable setting or add-hook
block.
Tim
next prev parent reply other threads:[~2002-10-27 22:24 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
2002-10-25 14:27 ` Stefan Monnier <foo@acm.com>
[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
[not found] ` <mailman.1035481346.8205.help-gnu-emacs@gnu.org>
2002-10-27 22:24 ` Tim Cross [this message]
-- 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=874rb7ldu4.fsf@blind-bat.une.edu.au \
--to=tcross@nospam.une.edu.au \
/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).