From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: wohler@newt.com, emacs-devel@gnu.org
Subject: Re: toolbar conventions
Date: Sat, 17 Dec 2005 14:22:56 -0600 (CST) [thread overview]
Message-ID: <200512172022.jBHKMuw15652@raven.dms.auburn.edu> (raw)
In-Reply-To: <E1EnhvF-0001vV-Q9@fencepost.gnu.org> (rms@gnu.org)
Richard Stallman wrote:
Does anyone have any ideas on the issue of how to use the term
"option"? That issue is more important--it is not just an issue of
punctuation, it is inconsistent use of a word. Would someone like to
study the situation and find out which uses occur where?
The name "user option" used to pretty consistently refer to variables,
although occasionally some remarks about them may have applied to
faces too, without this being explicitly mentioned.
It appears that this started to change somewhere around the beginning
of this year, with changes like:
2005-01-30 Richard M. Stallman <rms@gnu.org>
* custom.texi (Easy Customization): Defn of "User Option"
now includes faces. Don't say just "option" when talking
about variables. Do say just "options" to mean "anything
customizable". (Specific Customization): Describe
`customize-variable', not `customize-option'.
This appears to be a rather radical change in terminology, especially
when supposedly preparing for a release. It would require going very
carefully through code and manuals, if we wanted to be consistent. I
believe that the majority of places in the Emacs code and docs still
use the word "user option" to mean "user variable".
The change would require some getting used to it for existing users,
used to the old terminology. Even if we consistently change all code
and manuals, use of the old terminology is likely to find its way back
in, through commits from people unaware of the change. I myself was
unaware of it, until today. I read through custom.texi, but somehow I
just thought that it used "option" in a loose way, for convenience.
Sincerely,
Luc.
next prev parent reply other threads:[~2005-12-17 20:22 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 [this message]
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
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=200512172022.jBHKMuw15652@raven.dms.auburn.edu \
--to=teirllm@dms.auburn.edu \
--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).