From: "Richard M. Stallman" <rms@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Inconsistency in whole buffer buttons.
Date: Sat, 14 Jan 2006 00:48:49 -0500 [thread overview]
Message-ID: <E1ExeHR-0001xa-MK@fencepost.gnu.org> (raw)
In-Reply-To: <200601130314.k0D3ECv16479@raven.dms.auburn.edu> (message from Luc Teirlinck on Thu, 12 Jan 2006 21:14:12 -0600 (CST))
But there is a difference in single option buffers. The way I
implemented "Erase Customization", it does _not_ ask for confirmation
in single option buffers. The others do. The behavior should be made
uniform in single option buffers one way or the other. I could easily
make the behavior uniform in either way.
I think it is best if none of the buffer buttons
asks for confirmation in a single-option buffer.
So my idea for after the release would be:
Single option buffers: all current State Menu items become whole
buffer buttons (some under a heading "Advanced"), no State button.
I don't like that idea. I think that an option should look the same
whether there are other options in the buffer or not.
Multiple-option buffer: whole buffer buttons and other whole buffer
functionality only available upon setting a defcustomed option,
disabled by default.
I don't think I like that.
next prev parent reply other threads:[~2006-01-14 5:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-13 3:14 Inconsistency in whole buffer buttons Luc Teirlinck
2006-01-13 18:16 ` Drew Adams
2006-01-13 22:17 ` Luc Teirlinck
2006-01-13 23:36 ` Kim F. Storm
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 5:48 ` Richard M. Stallman [this message]
2006-01-15 3:17 ` Luc Teirlinck
2006-01-15 10:55 ` David Kastrup
2006-01-15 16:42 ` Luc Teirlinck
2006-01-15 23:07 ` Richard M. Stallman
2006-01-15 23:08 ` Richard M. 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=E1ExeHR-0001xa-MK@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.