Re: texinfo-5.9.90 pretest available

[Eli Zaretskii]

> Date: Tue, 24 Feb 2015 17:59:53 +0000
> From: Gavin Smith <address@hidden>
> Cc: Karl Berry <address@hidden>, Texinfo <address@hidden>
> 
> On 24 February 2015 at 16:39, Eli Zaretskii <address@hidden> wrote:
> > Next, "make check" fails because info/pseudotty.c cannot be possibly
> > compiled on Windows (and I'm not sure how portable it is to Posix
> > platforms, either).  This is bad news for the MinGW port, because most
> > of the Info brand-new test suite will not run.  I found and ran all
> > the non-interactive tests by hand, but it would be nice if (1) there
> > were a way to at least run those non-interactive tests automatically
> > where pseudotty cannot be used; and (2) how about including in the
> > scripts that implement interactive tests instructions for running them
> > manually?  I think being able to run the tests on any supported
> > platform is important.
> 
> Because pseudotty is in check_PROGRAMS in info/Makefile.am, "make
> check" will first try to build pseudotty. There may be a way round it
> with configure checks and Automake conditionals. Although I don't feel
> it's very important to get the test suite to work under difficult
> situations.

I'm okay with "make -k" as well, as long as it runs the test suite, or
part thereof.  TIA.

> > This is because texi2any.pl uses "#! /usr/bin/env perl", which the
> > version of Bash I use doesn't grok.  Is this really needed? other
> > scripts that are installed by "make install" use just "/bin/perl".
> 
> This is to find the location of the perl executable in the search
> path.

Wouldn't "perl texi2any.pl" work?

> Does "/usr/bin/env" exist for you?

Yes, of course.  That's not the problem.

> (As far as I know the reading of the "#!" line is not done by the
> shell itself, but by the kernel

On Unix, yes.  But I'm running that on Windows, where the "kernel" is
a DLL that implement Posix functionality.  Evidently this feature is
not supported there.

> >      $ ./t/dir-file-sloppily.sh && echo OK
> >      info: adding ./t/infodir to INFOPATH
> >      info: looking for file "FiLe-M"
> >      info: looking for file FiLe-M in ./t/infodir
> >      info: falling back to manpage node
> >      info: No menu item 'FiLe-M' in node '(dir)Top'.
> >      info: writing node (*manpages*)FiLe-M...
> >      info: closing -
> >
> > IOW, it interprets "FiLe-M" as a file name, and then falls back to man
> > pages.  To solve this, I needed to change the command line to this:
> >
> >      $GINFO --output - -f ${srcdir}/t/infodir/dir FiLe-M | grep "^File: 
> > file-menu,"
> >
> 
> That would be a different test. It should be looking for a menu entry
> in the dir file, which I suspect is not being found. I suspect this is
> because the infokey file is not being read.

The infokey file _is_ being read, I just edited out those two
messages.

Which part(s) of the infokey file are supposed to change the behavior
we are talking about?

> For me, I get the
> following output:
> $t/dir-file-sloppily.sh
> info: "./t/Infokey-config", line 2: unknown action `xxx-not-recognized'
> info: "./t/Infokey-config", line 3: cannot bind key sequence to menu-digit
> File: file-menu,   Node: Top
> 
> As you see, there are messages there about reading the init file.

Here's my full output:

     $ ./t/dir-file-sloppily.sh && echo OK
     info: "./t/Infokey-config", line 2: unknown action `xxx-not-recognized'
     info: "./t/Infokey-config", line 3: cannot bind key sequence to menu-digit
     info: adding ./t/infodir to INFOPATH
     info: looking for file "FiLe-M"
     info: looking for file FiLe-M in ./t/infodir
     info: falling back to manpage node
     info: No menu item 'FiLe-M' in node '(dir)Top'.
     info: writing node (*manpages*)FiLe-M...
     info: closing -

Can you add --debug=-1 and show what ginfo prints?  It might give me a
clue where to look.  Or maybe you have an idea where I should look
even without it?