unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Marshall, Simon" <simon.marshall@misys.com>
Cc: 'Emacs Developers' <emacs-devel@gnu.org>
Subject: RE: customize-saved in the customize menu?
Date: Tue, 16 Apr 2002 10:55:40 +0100	[thread overview]
Message-ID: <FC3DA3DC8D4AD311AB910020352A8FDC0BC62CD0@eagle.midas-kapiti.com> (raw)

> > I think it would be useful for this to be in the "Options/Customize
> > Emacs" menu.  (I was going to write "I think it would be 
> useful if there
> > was such a command" until I realised there was one.)
> > 
> > I think "Recently Changed Options..." entry should be 
> renamed "Recently
> > Changed Options in Emacs..." to avoid potential confusion---users
> > assuming that it is for their own recently changed 
> options---or perhaps
> > instead just change the tooltip from "... recent versions" to "...
> > recent Emacs versions".
> 
> Maybe "New Customization Options..."  would better indicate what's
> intended? 
> 
>  And the tool-tip could read
>  "Customize options added or changed in recent Emacs versions"

Yes, your wording for "Recently Changed Options..." would probably be
better.

So, together with my suggestion to add customized-saved, the menu might
be:

Top-level Customization Group
Browse Customization Groups
Changed Customization Options		(new entry, command
customize-saved)
---
New Customization Options...	(renamed from Recently Changed
Options...)
Specific Option...
[etc.]

The tool-tip for customized-saved could read "Customize options
previously customized by you" or somesuch.

             reply	other threads:[~2002-04-16  9:55 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-04-16  9:55 Marshall, Simon [this message]
  -- strict thread matches above, loose matches on Subject: below --
2002-04-29 13:42 customize-saved in the customize menu? Simon Marshall
2002-04-30  5:18 ` Richard Stallman
2002-04-11 16:14 Marshall, Simon
2002-04-12 13:57 ` Kim F. Storm

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=FC3DA3DC8D4AD311AB910020352A8FDC0BC62CD0@eagle.midas-kapiti.com \
    --to=simon.marshall@misys.com \
    --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).