From: Eli Zaretskii <eliz@gnu.org>
To: Drew Adams <drew.adams@oracle.com>
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, 02 Aug 2019 09:46:41 +0300 [thread overview]
Message-ID: <83d0hogj3i.fsf@gnu.org> (raw)
In-Reply-To: <02aef894-7fda-4061-943e-24115490c85e@default> (message from Drew Adams on Thu, 1 Aug 2019 13:07:20 -0700 (PDT))
> Date: Thu, 1 Aug 2019 13:07:20 -0700 (PDT)
> From: Drew Adams <drew.adams@oracle.com>
> Cc: drew.adams@oracle.com, 21594@debbugs.gnu.org
>
> > the assumption that someone might look up this
> > node by its name, or be surprised that only
> > defcustoms are described there, is misguided, IMO.
>
> No one made such an assumption, if by "look up"
> you mean only `i'.
But you just did:
> Use `i' and you get to the right node for
> `variable definition'. No problem there.
>
> Use `g' with completion and you get to the
> wrong node for the same input.
My point is exactly that this is a wrong analogy. When one uses 'g',
one needs to know the node's name in advance, not use that name as a
means for searching for some specific subject. The latter is done
via 'i'.
> It's that `g' is also useful, and node names should be helpful, not
> misleading.
They are, but by definition much less so than 'i'.
And let's please stop this discussion here by agreeing to disagree,
OK?
next prev parent reply other threads:[~2019-08-02 6:46 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 ` bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachable by `i variable definition' Drew Adams
2019-08-02 6:46 ` Eli Zaretskii [this message]
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
2015-09-30 21:46 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
2019-08-04 2:58 ` Richard Stallman
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=83d0hogj3i.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=21594@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--cc=larsi@gnus.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 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).