On Sun, Jan 22, 2023 at 01:05:26PM +0100, Arash Esbati wrote:
> Hi all,
>
> I'm observing an issue where backslashes and possibly & signs in node
> names don't work. The following calls of node names work:
>
> info '(latex2e)Overview'
> info '(latex2e)Document classes'
>
> But this one breaks:
>
> info '(latex2e)\indent & \noindent'
> => info: ./(latex2e)\indent & \noindent: No such file or directory
I have just tried this and it works fine, so it must be something Msys2
specific.
It is probably related to the use of backslash as a directory path
separator. I tested a node name with a forward slash and this had the
same problem:
$ info '(texinfo)Format with TeX/texindex'
info: ./(texinfo)Format with TeX/texindex: No such file or directory
while "info texinfo -n 'Format with tex/texindex'" does work.
What seems to be happening is that the slash means that the argument
is being taken as a relative path to the current directory. This is
what makes "info ./MANUAL" look for MANUAL.info in the current directory,
while "info MANUAL" looks for MANUAL in the dir file first.
The fix that comes to mind is that if the argument begins with a "(",
to try it as a "(MANUAL)NODE" specification first.
