Re: Info-build-node-completions has an extra `*' node

[Bastien]

Juri Linkov <address@hidden> writes:

>>>> I would prefer the completion to list the possible file names as it
>>>> lists the possible node names in a normal Info node, without the need
>>>> to enter a parenthesis first.
>>>
>>> This would break the standard format of the node name `(FILE)NODE'.
>>>
>>> `g' lists all node names (the virtual Info file `dir' has only one
>>> node `Top' so it is right for `g' to list only this single node.)
>>> And according to this format a file name should be inside parenthesis,
>>> so completion for the file name after parenthesis is more correct.
>>
>> What about putting an opening parenthesis in the default list of
>> completion for the (dir) buffer?  For now the opening parenthesis is
>> like a secret key for those who know that the list of visible items
>> only reflects files, not real nodes.
>
> Why would someone normally want a completion on Info file names instead of
> Info manual names with typing `m TAB'?

I think this boils down to disambiguate what a "menu item" refers to.
In a manual, a menu item is a node; in (dir), a menu item is a really
a file name (a manual.)

My point is that, when listed in (dir), a manual looks like a node.
Hence the user might expect `Info-goto-node' to offer completion on 
the manuals as well.

In fact, I find `Info-menu' and `Info-goto-node' to be a bit redundant,
and the fact that `Info-goto-node' is not helpful in (dir) doesn't help
the two commands to be less redundant.

But maybe I don't know info.el enough and I miss something.

-- 
Bastien