unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
Subject: [dortmann@lsil.com: emacs customization suggestion: 'customize-existing']
Date: Fri, 06 Feb 2004 08:42:51 -0500	[thread overview]
Message-ID: <E1Ap6Fv-0007St-Ny@fencepost.gnu.org> (raw)

Would someone like to do this?

------- Start of forwarded message -------
Sender: dortmann@lsil.com
To: rms@gnu.org
Subject: emacs customization suggestion: 'customize-existing'
From: Daniel Ortmann <dortmann@lsil.com>
Date: 04 Feb 2004 10:16:42 -0600
X-Scanned-By: MIMEDefang 2.39
X-Spam-Status: No, hits=-0.5 required=5.0
	tests=USER_AGENT_GNUS_UA
	version=2.55
X-Spam-Level: 
X-Spam-Checker-Version: SpamAssassin 2.55 (1.174.2.19-2003-05-19-exp)

Sir,

Here is an idea for your consideration:

Suggestion:

    Add a customization option such as 'customize-existing' which fills
    a customize buffer only with currently customized settings.  A
    related command for faces might be 'customize-existing-faces'.

Problem Solved:

    Moving a laptop between the office and home requires customization
    changes in gnus, for example.  The variables which need to change
    are in different groups, however, and are hard to find.

    A 'customize-existing' command would put all of the variables into
    one buffer for quick locating and changing.

A Minor Detail:

    The settings in the buffer should be sorted first by their group,
    and then alphabetically within the group.

- -- 
Daniel Ortmann, LSI Logic, 3425 40th Av NW, Suite 200, Rochester MN 55901
work: Daniel.Ortmann@lsil.com / 507.535.3861 / 63861 int / 8012.3861 gdds
home: ortmann@venturecs.net / 507.288.7732, 2414 30Av NW #D, Rochester MN 55901
gpg/pgp public key: http://wwwkeys.us.pgp.net
jabber: daniel_ortmann@jabber.org / dortmann@jabber.co.lsil.com
------- End of forwarded message -------

             reply	other threads:[~2004-02-06 13:42 UTC|newest]

Thread overview: 22+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-02-06 13:42 Richard Stallman [this message]
2004-02-06 15:55 ` [dortmann@lsil.com: emacs customization suggestion: 'customize-existing'] 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
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=E1Ap6Fv-0007St-Ny@fencepost.gnu.org \
    --to=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).