From: "Richard M. Stallman" <rms@gnu.org>
Cc: wohler@newt.com, emacs-devel@gnu.org
Subject: Re: toolbar conventions
Date: Sun, 18 Dec 2005 23:39:44 -0500 [thread overview]
Message-ID: <E1EoCoK-0000Wi-TE@fencepost.gnu.org> (raw)
In-Reply-To: <200512172022.jBHKMuw15652@raven.dms.auburn.edu> (message from Luc Teirlinck on Sat, 17 Dec 2005 14:22:56 -0600 (CST))
This appears to be a rather radical change in terminology, especially
when supposedly preparing for a release.
A change in documentation terminology is never radical in the way code
changes can be.
Last January we had far to go before a release. Getting the
documentation into shape was the main job that needed doing, and I
found out about a problem in the documentation of Customize. It
needed a simple way to talk about all the things that you can
customize. I tried redefining the term "option" to mean all kinds of
things that appear in Custom buffers.
The change was never extended to the other manuals, and it seems to be
bigger than I thought. So I think that choice was a mistake. We
ought to undo my half-made change. But we still need to address the
original problem, to find some other solution to the original problem,
some other term for "all the things that can appear in a Custom
buffer."
In January, some people argued for "preference". We could use that.
Or perhaps "setting". What do people think of those? Any other
suggestions?
next prev parent reply other threads:[~2005-12-19 4:39 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-12-16 21:36 toolbar conventions Bill Wohler
2005-12-17 19:40 ` Richard M. Stallman
2005-12-17 20:22 ` Luc Teirlinck
2005-12-17 20:52 ` Bill Wohler
2005-12-17 22:51 ` Luc Teirlinck
2005-12-18 0:57 ` Drew Adams
2005-12-18 3:11 ` Luc Teirlinck
2005-12-19 19:58 ` Drew Adams
2005-12-19 4:39 ` Richard M. Stallman [this message]
2005-12-20 1:52 ` Luc Teirlinck
2005-12-20 3:32 ` Drew Adams
2005-12-20 16:33 ` Richard M. Stallman
2005-12-20 18:37 ` user preferences (was RE: toolbar conventions) Drew Adams
2005-12-22 17:52 ` Richard M. Stallman
2005-12-22 18:09 ` Drew Adams
2005-12-23 15:18 ` Richard M. Stallman
2005-12-22 17:52 ` Richard M. Stallman
2005-12-20 5:12 ` toolbar conventions Glenn Morris
2005-12-17 20:26 ` Bill Wohler
2005-12-18 17:15 ` Richard M. Stallman
2005-12-18 20:45 ` Bill Wohler
2005-12-19 23:46 ` Richard M. Stallman
2005-12-17 20:30 ` Luc Teirlinck
2005-12-18 18:41 ` Luc Teirlinck
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=E1EoCoK-0000Wi-TE@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wohler@newt.com \
/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).