From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org, rms@gnu.org, storm@cua.dk
Subject: Re: Visual cleanup for customize buffers
Date: Sun, 15 Jan 2006 12:09:29 -0600 (CST) [thread overview]
Message-ID: <200601151809.k0FI9T403612@raven.dms.auburn.edu> (raw)
In-Reply-To: <43C9717C.4020900@student.lu.se> (message from Lennart Borgman on Sat, 14 Jan 2006 22:47:40 +0100)
Lennart Borgman wrote:
My impression when we started looking at Custom was that not many
developers or advanced users were using it.
We do get bug reports about Custom, so it _is_ used by many people
knowledgeable enough to file bug reports.
Some Emacs developers apparently do not use it. I use it
extensively, but never use the whole buffer buttons in multi-option
buffers, except for testing purposes if I am making code changes to
them. I have the impression that the latter use _still_ means that I
use the whole buffer buttons in multi-option buffers a lot more
extensively than other people do.
Custom is, in as far as I know, the only reliable option browser
Emacs has. The `apropos' facility is not a reliable alternative,
because you can not find non-loaded stuff that way and, in my own
experience, most of the time the options I need to find turn out not
to be loaded. If after using customize-browse, you find the option
you want, it is a lot more convenient to customize it right in the
buffer you have in front of you, than to visit your .emacs and start
writing some Lisp code, no matter how well you know Elisp. So there
are good reasons for advanced users to use it.
Sincerely,
Luc.
next prev parent reply other threads:[~2006-01-15 18:09 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 [this message]
2006-01-15 18:41 ` Kim F. Storm
2006-01-15 19:59 ` Luc Teirlinck
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=200601151809.k0FI9T403612@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--cc=emacs-devel@gnu.org \
--cc=rms@gnu.org \
--cc=storm@cua.dk \
/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.