Re: Non-ASCII characters in @include search path

2022-02-22 Thread Patrice Dumas
On Tue, Feb 22, 2022 at 08:52:56PM +, Gavin Smith wrote: > On Mon, Feb 21, 2022 at 11:34:00PM +0100, Patrice Dumas wrote: > > On Mon, Feb 21, 2022 at 09:29:06PM +, Gavin Smith wrote: > > > > > > Done in commit 73e922d68b. > > > > I would prefer to have the line numbers in tests, I'll have

Re: Non-ASCII characters in @include search path

2022-02-22 Thread Gavin Smith
On Mon, Feb 21, 2022 at 11:34:00PM +0100, Patrice Dumas wrote: > On Mon, Feb 21, 2022 at 09:29:06PM +, Gavin Smith wrote: > > > > Done in commit 73e922d68b. > > I would prefer to have the line numbers in tests, I'll have a look at > it, but this should be doable without changing the spirit of

Re: Missing first index entry

2022-02-22 Thread Gavin Smith
On Tue, Feb 22, 2022 at 03:46:36PM +0300, Sergey Matveev wrote: > run "makeinfo foo.texi" and info ./foo.info says that no indices found > on "i"/"I" commands. If I rename "My" node to "My Index", then info > won't note about missing indices. I did not find explicit note about > that requirement.

Missing first index entry

2022-02-22 Thread Sergey Matveev
Greetings! I have got strange issues (a bug?) with Texinfo 6.8's info command. First of all, according to info/indices.c:info_indices_of_file_buffer and its "if (strcasestr (tag->nodename, "Index") ..." check, at looks and indices only if node's name contains "Index" word in it. For example I hav

AW: Feature request: api docs

2022-02-22 Thread Reißner Ernst
-Ursprüngliche Nachricht- Von: Patrice Dumas Gesendet: Samstag, 19. Februar 2022 15:55 An: Reißner Ernst Cc: bug-texinfo@gnu.org; rei3...@arcor.de Betreff: Re: Feature request: api docs On Mon, Feb 07, 2022 at 08:30:15AM +, Reißner Ernst wrote: > > Well, I think texinfo was used