From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: monnier@iro.umontreal.ca, rms@gnu.org, drew.adams@oracle.com,
emacs-devel@gnu.org
Subject: Re: Eliminating "changed in Emacs outside of Customize"
Date: Thu, 3 Feb 2005 21:16:20 -0600 (CST) [thread overview]
Message-ID: <200502040316.j143GKf04943@raven.dms.auburn.edu> (raw)
In-Reply-To: <200502040131.j141VC904260@raven.dms.auburn.edu> (message from Luc Teirlinck on Thu, 3 Feb 2005 19:31:12 -0600 (CST))
>From my previous message:
>From my previous message:
After Emacs 21.4 is out we could try to make sure that those lines
basically never will appear, by trying to eliminate the (unfortunately
numerous) situations that give rise to it.
Actually, unlike what I said in a previous message, this would not
eliminate the warnings due to user customizations in .emacs. But I
emphasized the wrong thing in the quote above. The important thing is
not to eliminate "Set outside of Custom" statements _as a goal in its
own right_. The important thing (for after emacs 21.4) is to make sure
that people can safely customize options like `find-file-hook',
`completion-ignored-extensions' and many others, through Custom,
which they can currently not do.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-02-04 3:16 UTC|newest]
Thread overview: 59+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-01-26 0:03 Eliminating "changed in Emacs outside of Customize" Richard Stallman
2005-01-31 10:33 ` Per Abrahamsen
2005-02-01 13:30 ` Richard Stallman
2005-02-01 14:32 ` Per Abrahamsen
2005-02-01 18:58 ` Drew Adams
2005-02-01 20:04 ` Stefan Monnier
2005-02-01 20:38 ` Drew Adams
2005-02-01 20:44 ` David Kastrup
2005-02-01 21:05 ` Drew Adams
2005-02-01 23:52 ` Robert J. Chassell
2005-02-01 21:19 ` Lennart Borgman
2005-02-01 21:35 ` David Kastrup
2005-02-01 22:11 ` Luc Teirlinck
2005-02-01 22:26 ` Lennart Borgman
2005-02-02 1:03 ` Luc Teirlinck
2005-02-02 1:34 ` Drew Adams
2005-02-02 2:11 ` Luc Teirlinck
2005-02-02 2:51 ` Luc Teirlinck
2005-02-03 6:40 ` Richard Stallman
2005-02-01 22:28 ` David Kastrup
2005-02-01 22:40 ` Drew Adams
2005-02-03 6:39 ` Richard Stallman
2005-02-03 7:29 ` Lennart Borgman
2005-02-05 5:27 ` Richard Stallman
2005-02-03 16:54 ` Drew Adams
2005-02-01 22:40 ` Drew Adams
2005-02-01 21:25 ` Lennart Borgman
2005-02-03 6:39 ` Richard Stallman
2005-02-02 7:57 ` Per Abrahamsen
2005-02-02 18:33 ` Drew Adams
2005-02-02 21:04 ` Lennart Borgman
2005-02-02 22:11 ` Drew Adams
2005-02-02 22:55 ` Stefan Monnier
2005-02-02 22:45 ` Luc Teirlinck
2005-02-03 15:49 ` Lennart Borgman
2005-02-03 16:12 ` Luc Teirlinck
2005-02-03 15:51 ` Lennart Borgman
2005-02-03 16:01 ` Lennart Borgman
2005-02-03 19:14 ` Richard Stallman
2005-02-04 7:27 ` Lennart Borgman
2005-02-03 19:12 ` Richard Stallman
2005-02-03 19:45 ` Stefan Monnier
2005-02-03 19:59 ` Lennart Borgman
2005-02-03 20:34 ` Stefan Monnier
2005-02-05 5:31 ` Richard Stallman
2005-02-03 20:53 ` Drew Adams
2005-02-03 22:08 ` Luc Teirlinck
2005-02-03 22:13 ` Luc Teirlinck
2005-02-04 1:04 ` Luc Teirlinck
2005-02-04 1:31 ` Luc Teirlinck
2005-02-04 3:16 ` Luc Teirlinck [this message]
2005-02-03 21:10 ` Robert J. Chassell
2005-02-03 6:39 ` Richard Stallman
2005-02-03 6:41 ` Richard Stallman
2005-02-03 14:42 ` Stefan Monnier
2005-02-03 15:23 ` Luc Teirlinck
2005-02-03 15:48 ` Luc Teirlinck
2005-02-01 15:41 ` Lennart Borgman
2005-02-02 7:40 ` Per Abrahamsen
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=200502040316.j143GKf04943@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
--cc=rms@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).