From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: lennart.borgman.073@student.lu.se, rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Visual cleanup for customize buffers
Date: Sun, 15 Jan 2006 13:59:16 -0600 (CST) [thread overview]
Message-ID: <200601151959.k0FJxGn04672@raven.dms.auburn.edu> (raw)
In-Reply-To: <m3bqydl4eq.fsf@kfs-l.imdomain.dk> (storm@cua.dk)
Kim Storm wrote:
Whatever the reason for the "feature", it is IMHO completely broken as
a user interface.
(The "feature" being that the whole buffer buttons ignore hidden items.)
As I pointed out before, this is too dangerous to mess with before the
release, because Custom internals rely too heavily on it, as well as
for some other reasons. After the release, this has to be considered
in conjunction with other possible changes which might completely
change the problem, or even make it irrelevant. I do not see what the
purpose of continuing to discuss this _right now_ is.
What is easy and safe to do right now is to better inform people that
these buttons do not operate on groups, hidden options or options
changed outside Custom, by saying that in the text above these
buttons, as I proposed earlier.
Sincerely,
Luc.
next prev parent reply other threads:[~2006-01-15 19:59 UTC|newest]
Thread overview: 57+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-12 21:58 Visual cleanup for customize buffers Kim F. Storm
2006-01-12 23:45 ` Luc Teirlinck
2006-01-13 12:37 ` Kim F. Storm
2006-01-13 14:18 ` Luc Teirlinck
2006-01-13 15:16 ` Kim F. Storm
2006-01-13 19:05 ` Drew Adams
2006-01-13 19:16 ` David Kastrup
2006-01-13 23:28 ` Luc Teirlinck
2006-01-13 23:34 ` Luc Teirlinck
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 0:08 ` Luc Teirlinck
2006-01-14 0:44 ` Luc Teirlinck
2006-01-14 1:56 ` Kim F. Storm
2006-01-14 2:58 ` Chong Yidong
2006-01-14 6:10 ` Drew Adams
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 16:14 ` Richard M. Stallman
2006-01-14 20:50 ` Lennart Borgman
2006-01-14 21:32 ` Luc Teirlinck
2006-01-14 21:47 ` Lennart Borgman
2006-01-15 18:09 ` Luc Teirlinck
2006-01-15 18:41 ` Kim F. Storm
2006-01-15 19:59 ` Luc Teirlinck [this message]
2006-01-14 21:58 ` Drew Adams
2006-01-14 22:17 ` Drew Adams
2006-01-15 1:40 ` Luc Teirlinck
2006-01-15 23:08 ` Richard M. Stallman
2006-01-16 4:19 ` Luc Teirlinck
2006-01-19 17:44 ` Richard M. Stallman
2006-01-17 4:20 ` Luc Teirlinck
2006-01-17 20:00 ` Richard M. Stallman
2006-01-20 0:18 ` Luc Teirlinck
2006-01-13 16:40 ` Stefan Monnier
2006-01-13 19:04 ` Bill Wohler
2006-01-14 1:28 ` Luc Teirlinck
2006-01-14 1:46 ` Bill Wohler
2006-01-14 5:49 ` Richard M. Stallman
2006-01-14 15:28 ` Luc Teirlinck
2006-01-13 0:08 ` Luc Teirlinck
2006-01-13 15:24 ` Kim F. Storm
2006-01-13 19:33 ` martin rudalics
2006-01-13 0:24 ` Luc Teirlinck
2006-01-14 5:48 ` Richard M. Stallman
2006-01-14 5:49 ` Richard M. Stallman
2006-01-14 15:07 ` Luc Teirlinck
2006-01-14 23:05 ` Luc Teirlinck
2006-01-15 4:40 ` Luc Teirlinck
2006-02-05 0:07 ` Kim F. Storm
2006-02-06 2:07 ` Richard M. Stallman
2006-02-06 4:30 ` Luc Teirlinck
2006-02-06 7:21 ` Eli Zaretskii
2006-02-06 17:35 ` Luc Teirlinck
2006-01-14 23:27 ` Luc Teirlinck
2006-01-14 23:45 ` Drew Adams
2006-01-15 18:59 ` Kim F. Storm
2006-01-15 4:17 ` Luc Teirlinck
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
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=200601151959.k0FJxGn04672@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=lennart.borgman.073@student.lu.se \
--cc=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).