[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: js-info polishing
From: |
Per Bothner |
Subject: |
Re: js-info polishing |
Date: |
Tue, 27 Apr 2021 12:57:18 -0700 |
User-agent: |
Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.8.1 |
On 4/27/21 12:15 PM, Eli Zaretskii wrote:
It looks like the manual at those URLs doesn't have an Index? If so,
would it be possible to set up a manual with one or more indices, so
that the index search could be test-driven?
I'll try building the Kawa manual (which has an index) this way.
It's a bigger manual, and there may be some issues.
Also, are there plans to implement more keyboard commands? For
example, 'g' could be very useful, especially in large manuals.
No immediate plans, but I expect we would add more commands based
on requests. The 'g' commands some conceptual complications, like
what is a "node name", given that raw node names don't appear in
the manual. Perhaps we should search for both section names and
node names. The implementation while probably not very complicated
is also not something you'd do in an hour or so.
I probably won't implement the 'g' command myself, at least
not in the near future (or before the hoped-for texinfo release).
--
--Per Bothner
per@bothner.com http://per.bothner.com/
- Re: js-info polishing, Per Bothner, 2021/04/27
- Re: js-info polishing, Gavin Smith, 2021/04/27
- Re: js-info polishing, Eli Zaretskii, 2021/04/27
- Re: js-info polishing,
Per Bothner <=
- Re: js-info polishing, Per Bothner, 2021/04/29
- Re: js-info polishing, Eli Zaretskii, 2021/04/29
- Re: js-info polishing, Gavin Smith, 2021/04/29
- Re: js-info polishing, Per Bothner, 2021/04/29
- Re: js-info polishing, Eli Zaretskii, 2021/04/29
- Re: js-info polishing, Gavin Smith, 2021/04/29
- Re: js-info polishing, Per Bothner, 2021/04/30
Re: js-info polishing, Per Bothner, 2021/04/27