From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: lennart.borgman.073@student.lu.se, emacs-devel@gnu.org
Subject: Re: customize-rouge output with emacs -q --no-site-file
Date: Fri, 4 Feb 2005 18:47:15 -0600 (CST) [thread overview]
Message-ID: <200502050047.j150lFl14115@raven.dms.auburn.edu> (raw)
In-Reply-To: <200502042348.j14NmsN14084@raven.dms.auburn.edu> (message from Luc Teirlinck on Fri, 4 Feb 2005 17:48:54 -0600 (CST))
>From my earlier message:
If we now make changes to Emacs that require adding other
elements to these hooks, lists or alists, or removing elements, the
user does not get those values, because he hardwired the old value in
his .emacs.
Actually, thinking about it, this particular problem can occur when
customizing _any_ hook, list or alist through Custom. Basically,
whenever you are not supposed to just setq an option, setting it
through Custom is dangerous, because you _are_ setq-ing it. For
instance, I have before-save-hook set through Custom. This is
currently not a rogue variable, no problem. But whenever somebody
would, say fix a bug or implement a new feature by adding a function
to before-save-hook, my Emacs will not see it. My .emacs will
override it. In other words, before-save-hook is not rogue now, but
anytime that I update my CVS, it could become rogue. Personally, I
will get rid of this entry in custom-set-variables and use add-hook in
my .emacs. Much safer.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-02-05 0:47 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-04 16:03 customize-rouge output with emacs -q --no-site-file Lennart Borgman
2005-02-04 19:14 ` Lennart Borgman
2005-02-04 21:57 ` Lennart Borgman
2005-02-04 22:17 ` Lennart Borgman
2005-02-04 23:48 ` Luc Teirlinck
2005-02-05 0:47 ` Luc Teirlinck [this message]
2005-02-05 17:39 ` Richard Stallman
2005-02-05 0:03 ` Luc Teirlinck
2005-02-05 0:06 ` Luc Teirlinck
2005-02-05 17:39 ` Richard Stallman
2005-02-05 1:56 ` Luc Teirlinck
2005-02-05 3:51 ` Luc Teirlinck
2005-02-05 9:08 ` Lennart Borgman
2005-02-05 14:51 ` Luc Teirlinck
2005-02-06 12:42 ` Richard Stallman
2005-02-06 19:54 ` Luc Teirlinck
2005-02-05 19:06 ` Luc Teirlinck
2005-02-05 19:52 ` Lennart Borgman
2005-02-05 21:16 ` Luc Teirlinck
2005-02-07 20:51 ` Richard Stallman
2005-02-07 21:27 ` Lennart Borgman
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=200502050047.j150lFl14115@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
/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).