[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Merged indexes with subentries
From: |
Akim Demaille |
Subject: |
Merged indexes with subentries |
Date: |
Tue, 19 Nov 2019 21:08:46 +0100 |
Hi!
Structured indexes are great, thanks a lot for this! However they don't work
well for Bison for three different reasons (two "bugs", and one "missing
feature"), presented in the attachement.
> @syncodeindex fn cp
> @syncodeindex vr cp
> @syncodeindex tp cp
>
> @cindex %define @subentry api.cindex
> @vindex %define @subentry api.vindex
> @findex %define @subentry api.findex
>
> @deffn {Directive} {%define @subentry api.prefix} @{@var{prefix}@}
> Foo
> @end deffn
gives in PDF:
> %
>
> %define api.vindex ............................ 1
> %define api.findex ............................ 1
> %define api.prefix ............................ 1
> %define,
> api.cindex................................... 1
1. As you can see, the merged indexes do not get subentries, but plain old
entries.
2. api.cindex is typeset in rm, not in tt as I would expected for the code
index.
3. I would love to be able to use @subentry in @deffn like structures. Indeed,
in Bison that's the way we define our "variable": with its defining %define
directive. Unfortunately that's not what happens here, and I can understand if
you reject this.
Cheers!
bison.texi
Description: Binary data
[Prev in Thread] |
Current Thread |
[Next in Thread] |
- Merged indexes with subentries,
Akim Demaille <=