From: "Lennart Borgman" <lennart.borgman.073@student.lu.se>
Cc: emacs-devel@gnu.org
Subject: Re: customize-rouge output with emacs -q --no-site-file
Date: Sat, 5 Feb 2005 20:52:24 +0100 [thread overview]
Message-ID: <00a901c50bbc$3a73c530$0200a8c0@sedrcw11488> (raw)
In-Reply-To: 200502051906.j15J6MX07513@raven.dms.auburn.edu
----- Original Message -----
From: "Luc Teirlinck" <teirllm@dms.auburn.edu>
> My suggestion was of course only for the "Erase C" problem, but I
> do believe that this should be solved and I see no big dangers with
> the solution.
>
> The danger is that it eliminates the "Changed outside Custom" warning.
But that is not really the problem here.
> At least the hooks, lists and alists among the variables are
> absolutely _not_ safe to set through Custom (or with setq for that
> matter), even after applying the patch I posted. You have to set them
> in your .emacs using add-hook (for hooks) or add-to-list (for lists).
> If you do not try to set the variables through Custom, you do not run
> in the "Erase Customization" problem either.
So there should perhaps be another warning?
next prev parent reply other threads:[~2005-02-05 19:52 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
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 [this message]
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='00a901c50bbc$3a73c530$0200a8c0@sedrcw11488' \
--to=lennart.borgman.073@student.lu.se \
--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).