all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Drew Adams <drew.adams@oracle.com>
Cc: 21594@debbugs.gnu.org
Subject: bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachable by `i variable definition'
Date: Thu, 01 Aug 2019 21:07:48 +0200	[thread overview]
Message-ID: <87v9vgg0vv.fsf@mouse.gnus.org> (raw)
In-Reply-To: <ae6720ed-ad9d-4110-9213-c8abdafa81e6@default> (Drew Adams's message of "Wed, 30 Sep 2015 14:46:26 -0700 (PDT)")

Drew Adams <drew.adams@oracle.com> writes:

> The problem is more the node name than the index entry.  The node title,
> within the node, is `Defining Customization Variables', which is much
> better.
>
> I imagine that the node name was picked because the node is a subnode of
> node `Customization', but that is not a good enough reason.
> `Info-goto-node' handles the nodes of a manual in a flat way.
>
> A node named `Variable Definitions' should cover all of defvar,
> defconst, and defcustom.  Likewise, an index entry named `variable
> definition'.  IOW, someone hunting for info about variable definitions
> should be able to get to general info about all kinds of variable
> definitions.

I'm not quite sure what you want to have done here.  As you say, that
node isn't really about "variable definitions", so it seems like a very
good thing that "variable definition" doesn't take you there, but to
"12.5 Defining Global Variables", which makes more sense.

Or is this something that has been fixed in the intervening years?

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2019-08-01 19:07 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 [this message]
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
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=87v9vgg0vv.fsf@mouse.gnus.org \
    --to=larsi@gnus.org \
    --cc=21594@debbugs.gnu.org \
    --cc=drew.adams@oracle.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 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.