From: "Robert Thorpe" <rthorpe@realworldtech.com>
To: help-gnu-emacs@gnu.org
Subject: Re: .emacs - minor mode behavior
Date: 15 Feb 2007 05:13:57 -0800 [thread overview]
Message-ID: <1171545237.688060.257450@p10g2000cwp.googlegroups.com> (raw)
In-Reply-To: <1171403693.631853.279610@m58g2000cwm.googlegroups.com>
> Also - I've read quite a few posts in this group, and it seems like
> most folks lean toward using customize as opposed to hand
> editing .emacs. Am I making things harder on myself?
It depends on what you're doing, some modes don't properly support
customize and of-course you can't write elisp programs in customize.
But where you can use customize it is useful.
I use it for most of my customizations, but some still live in elisp.
next prev parent reply other threads:[~2007-02-15 13:13 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-02-13 21:54 .emacs - minor mode behavior J K
2007-02-14 3:24 ` Kevin Rodgers
2007-02-14 17:04 ` Stefan Monnier
2007-02-15 13:13 ` Robert Thorpe [this message]
-- strict thread matches above, loose matches on Subject: below --
2007-02-14 21:48 A Soare
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=1171545237.688060.257450@p10g2000cwp.googlegroups.com \
--to=rthorpe@realworldtech.com \
--cc=help-gnu-emacs@gnu.org \
/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).