From: Richard Stallman <rms@gnu.org>
Cc: monnier+gnu/emacs@rum.cs.yale.edu, emacs-devel@gnu.org
Subject: Re: customize-mark-as-set for M-x foo-mode
Date: Wed, 21 Aug 2002 19:57:54 -0600 (MDT) [thread overview]
Message-ID: <200208220157.g7M1vs110540@wijiji.santafe.edu> (raw)
In-Reply-To: <200208211529.g7LFT5e24786@rum.cs.yale.edu> (monnier+gnu/emacs@rum.cs.yale.edu)
> For one thing, there are only a few modes you can control with the
> menu bar, but there are dozens, maybe hundreds, you can control
> with commands. Should all of them update your .emacs file?
> Maybe they should, but that is a lot of change.
AFAIK customize-mark-as-set does not itself update the .emacs file.
It just marks the variable as "changed by customize" rather
than "changed by some external thingy". It might indeed cause the
variable to be saved later on if you custom-save-all. I don't know
how important that is.
Please excuse my inadequate memory. I see no possible harm in marking
the variable as changed. So the question is simply whether we should try
to change as many minor modes as possible, or only some of them, or none.
If we succeed in changing most minor modes this way, but a few
(perhaps user-implemented) remain unchanged, will the inconsistency be
confusing, or will that be better than nothing?
next prev parent reply other threads:[~2002-08-22 1:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-19 20:55 customize-mark-as-set for M-x foo-mode Stefan Monnier
2002-08-21 0:12 ` Richard Stallman
2002-08-21 15:29 ` Stefan Monnier
2002-08-22 1:57 ` Richard Stallman [this message]
2002-08-22 15:23 ` Stefan Monnier
2002-08-26 12:22 ` Per Abrahamsen
2002-08-27 19:05 ` Richard Stallman
2002-08-28 0:03 ` Stefan Monnier
2002-08-28 23:32 ` 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=200208220157.g7M1vs110540@wijiji.santafe.edu \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=monnier+gnu/emacs@rum.cs.yale.edu \
/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).