all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: rms@gnu.org
Cc: 21594@debbugs.gnu.org, larsi@gnus.org
Subject: bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachable by `i variable definition'
Date: Fri, 2 Aug 2019 21:45:26 -0700 (PDT)	[thread overview]
Message-ID: <9f119133-45c1-452f-883c-739c5326edea@default> (raw)
In-Reply-To: <E1htjdQ-0001gF-Uv@fencepost.gnu.org>

> How about changing the node name to Customization Definitions
> or User Option Definitions?

Yes, thank you.  How about it?

There are several such possibilities.  Both
of those you suggest are fine.

I suggested also `Defining User Options' and
`Defining Customization Variables' (the current
title, inside the node).  (But if we do go with
"option" then the title too should reflect that.)

Nearly anything suggesting defcustom, option
definition, or custom variable definition.

The main thing is to avoid `Variable Definitions',
which invites confusion.

> I suggest defining the term "user option" in the parent node,
> the chapter Customization Settings.

I guess you mean instead of in node `Variable
Definitions', where it's defined now.

That too makes sense, as there we currently
introduce the term "customization items" and
we speak of customizing variables and faces,
without saying that the former are options.
(But the menu refers to user options.)





  reply	other threads:[~2019-08-03  4:45 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-09-30 21:46 bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachable by `i variable definition' Drew Adams
2019-08-01 19:07 ` Lars Ingebrigtsen
2019-08-01 19:23   ` Eli Zaretskii
2019-08-01 19:57   ` Drew Adams
2019-08-03  2:19     ` Richard Stallman
2019-08-03  4:45       ` Drew Adams [this message]
2019-08-04  2:58         ` Richard Stallman
     [not found] <<ae6720ed-ad9d-4110-9213-c8abdafa81e6@default>
     [not found] ` <<87v9vgg0vv.fsf@mouse.gnus.org>
     [not found]   ` <<83k1bwhepu.fsf@gnu.org>
2019-08-01 20:07     ` Drew Adams
2019-08-02  6:46       ` Eli Zaretskii
2019-08-02 11:25         ` Lars Ingebrigtsen
     [not found] <<<ae6720ed-ad9d-4110-9213-c8abdafa81e6@default>
     [not found] ` <<<87v9vgg0vv.fsf@mouse.gnus.org>
     [not found]   ` <<<83k1bwhepu.fsf@gnu.org>
     [not found]     ` <<02aef894-7fda-4061-943e-24115490c85e@default>
     [not found]       ` <<83d0hogj3i.fsf@gnu.org>
2019-08-02 15:21         ` Drew Adams

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=9f119133-45c1-452f-883c-739c5326edea@default \
    --to=drew.adams@oracle.com \
    --cc=21594@debbugs.gnu.org \
    --cc=larsi@gnus.org \
    --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 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.