[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachabl
bug#21594: 25.0.50; (elisp): node `Variable Definitions' is not reachable by `i variable definition'
Thu, 1 Aug 2019 13:07:20 -0700 (PDT)
> A node's name is a label, and needs to satisfy
> several requirements, so it isn't always as
> accurate as the section name.
True enough. And one of those requirements is
to be able to use `g' to get to it. A node's
name is something that users see and use. It's
not just an internal label.
> 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'.
The node name is important, and in this case
it's not good.
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.
And you might use substring or multiple-pattern
completion, with input like `var' and `def',
and the result of completion will be `Variable
Definitions', which you will naturally think
takes you to a node about that.
Completion shows you all matches for your input.
Scanning the candidates quickly is another way
to get to a node. It's not about `g' instead
of `i'. It's that `g' is also useful, and node
names should be helpful, not misleading.