From: Richard Stallman <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: [dortmann@lsil.com: emacs customization suggestion: 'customize-existing']
Date: Wed, 11 Feb 2004 09:58:10 -0500 [thread overview]
Message-ID: <E1AqvoY-0003yx-7C@fencepost.gnu.org> (raw)
In-Reply-To: <40292B4E.4010900@yahoo.com> (message from Kevin Rodgers on Tue, 10 Feb 2004 12:04:46 -0700)
Why not have 1 command, customize-changed, that by default shows the
unsaved variables (like customize-customized does now) but with a prefix
arg shows either the saved variables (like customize-saved) or both
saved and unsaved variables (like customize-touched)?
I think we should have just one command that shows both the saved and
unsaved customizations. Since each variable shows whether it is saved
or not, this command will be useful for those who want to find only
the saved customizations, and for those who want to find only the
unsaved customizations.
Having just one command in place of the present two will reduce the
overall complexity, and that is desirable, particularly for the kind
of user that the Custom interface is meant for.
I think we should use the name customize-changed-options for this, and
we should rename the existing command named customize-changed-options
to customize-new-options. That name gives a clearer picture of the
command's purpose.
While one could argue pedantically that the name customize-new-options
is incorrect, since not all the options it shows you are new, I think
we should not forego such a good name for pedantic reasons. (And if
anyone should care, the pedantic argument has a response, that any
option that shows up in this command is there because of something new
in Emacs.)
next prev parent reply other threads:[~2004-02-11 14:58 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-02-06 13:42 [dortmann@lsil.com: emacs customization suggestion: 'customize-existing'] Richard Stallman
2004-02-06 15:55 ` Kim F. Storm
2004-02-06 16:19 ` Daniel Ortmann
2004-02-06 23:40 ` Kim F. Storm
2004-02-06 23:30 ` Kevin Rodgers
2004-02-08 15:21 ` Richard Stallman
2004-02-09 18:11 ` Per Abrahamsen
2004-02-10 12:44 ` Richard Stallman
2004-02-10 13:44 ` Per Abrahamsen
2004-02-10 19:04 ` Kevin Rodgers
2004-02-11 11:16 ` Per Abrahamsen
2004-02-11 14:58 ` Richard Stallman [this message]
2004-02-12 15:25 ` Per Abrahamsen
2004-02-12 17:11 ` Kim F. Storm
2004-02-14 17:17 ` Richard Stallman
2004-02-18 15:23 ` Per Abrahamsen
2004-02-18 15:41 ` Jason Rumney
2004-02-19 16:02 ` Per Abrahamsen
2004-02-19 17:45 ` Reiner Steib
2004-02-20 13:42 ` Richard Stallman
2004-02-18 17:03 ` Kim F. Storm
2004-02-18 23:39 ` 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=E1AqvoY-0003yx-7C@fencepost.gnu.org \
--to=rms@gnu.org \
--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).