unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: wohler@newt.com, emacs-devel@gnu.org
Subject: Re: toolbar conventions
Date: Sun, 18 Dec 2005 12:41:45 -0600 (CST)	[thread overview]
Message-ID: <200512181841.jBIIfj929988@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?

If we use the name "User Option" for both variables and faces, then
that term would be only useful when discussing the Customize interface
in the Emacs manual.  Apart from the similarity in the way you
customize them through that interface, user variables and faces are
very different.  They even have different name spaces.  (Which makes
talking about "the option foo" meaningless.  This is a nuisance, even
when discussing the Customize interface.)

Calling something a "User Option" in the Elisp manual would be
meaningless, you would have to consistently call them "User Variables".
That means that all uses of defopt in all manuals should be changed to
`@defvr {User Variable}'.  The discussion of defopt in the Texinfo
manual would have to be changed, since the reference to Emacs would no
longer be valid.  This is just one example of all the problems we
would run into and all the work we would have to do to consistently
implement this terminology change.

Sincerely,

Luc.

      parent reply	other threads:[~2005-12-18 18:41 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
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 [this message]

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=200512181841.jBIIfj929988@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).