From: "Robert J. Chassell" <bob@rattlesnake.com>
To: emacs-devel@gnu.org
Subject: Re: always put Customizations in `custom-file', never in `user-init-file'
Date: Tue, 11 Dec 2007 03:02:45 +0000 (UTC) [thread overview]
Message-ID: <m1J1vOP-002K4JC@rattlesnake.com> (raw)
In-Reply-To: <DHEEKFAFJEFOJHLCFPFDKELJCCAA.drew.adams@oracle.com>
The entire `custom-file' is generally not intended to be edited by
a user ...
Over the past 30 years or so, one of the great advantages of Emacs has
been its easy and built-in programming. Whether an expert user or new
user, everyone not only has been able to learn but has been encouraged
to learn. As far as I am concerned -- especially since I am not an
expert programmer -- that makes Emacs better than other window
managers with editing libraries.
I agree, faces and fonts are confusing. At least, I am confused by
them. For me, it is worth making them simple to set. Thus, regarding
faces, it is easy to see and change, and change again (and perhaps
again and again) by modifying
(custom-set-faces
'(bold ((t (:background "DodgerBlue4" :foreground "coral1"))))
...
Moreover, it is easier for me to remember the name of one
customization file, a .emacs file, than two.
--
Robert J. Chassell GnuPG Key ID: 004B4AC8
bob@rattlesnake.com bob@gnu.org
http://www.rattlesnake.com http://www.teak.cc
next prev parent reply other threads:[~2007-12-11 3:02 UTC|newest]
Thread overview: 44+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-12-10 19:02 always put Customizations in `custom-file', never in `user-init-file' Drew Adams
2007-12-10 19:21 ` Eric Hanchrow
2007-12-10 20:30 ` Lennart Borgman (gmail)
2007-12-10 21:19 ` Stephen J. Turnbull
2007-12-10 21:25 ` Lennart Borgman (gmail)
2007-12-10 22:12 ` Drew Adams
2007-12-10 22:35 ` Lennart Borgman (gmail)
2007-12-10 23:09 ` Drew Adams
2007-12-10 23:19 ` Lennart Borgman (gmail)
2007-12-10 23:44 ` Drew Adams
2007-12-11 0:05 ` Jason Rumney
2007-12-11 0:16 ` Lennart Borgman (gmail)
2007-12-10 22:56 ` Stephen J. Turnbull
2007-12-10 23:06 ` David Kastrup
2007-12-11 0:07 ` Stephen J. Turnbull
2007-12-10 23:08 ` Drew Adams
2007-12-11 0:31 ` Stephen J. Turnbull
2007-12-10 22:08 ` Drew Adams
2007-12-10 23:45 ` Stephen J. Turnbull
2007-12-11 0:14 ` Lennart Borgman (gmail)
2007-12-11 1:04 ` Stephen J. Turnbull
2007-12-11 6:05 ` Drew Adams
2007-12-11 0:47 ` Drew Adams
2007-12-11 2:20 ` Stephen J. Turnbull
2007-12-11 6:15 ` Drew Adams
2007-12-11 9:53 ` Stephen J. Turnbull
2007-12-11 16:57 ` Drew Adams
2007-12-12 10:00 ` Stephen J. Turnbull
2007-12-12 16:31 ` Drew Adams
2007-12-11 19:01 ` Richard Stallman
2007-12-11 19:12 ` Drew Adams
2007-12-10 21:58 ` Drew Adams
2007-12-11 4:00 ` Stefan Monnier
2007-12-11 6:04 ` Drew Adams
2007-12-11 14:52 ` Stefan Monnier
2007-12-11 16:58 ` Drew Adams
2007-12-11 22:12 ` David Kastrup
2007-12-10 22:07 ` Jason Rumney
2007-12-10 23:08 ` Drew Adams
2007-12-11 3:02 ` Robert J. Chassell [this message]
2007-12-11 6:06 ` Drew Adams
2007-12-11 11:39 ` Robert J. Chassell
2007-12-11 16:58 ` Drew Adams
2007-12-11 19:00 ` Richard Stallman
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=m1J1vOP-002K4JC@rattlesnake.com \
--to=bob@rattlesnake.com \
--cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).