Sender: rich AT phekda DOT freeserve DOT co DOT uk
Message-ID: <3E14235C.8FD96120@phekda.freeserve.co.uk>
Date: Thu, 02 Jan 2003 11:32:44 +0000
From: Richard Dawe <rich AT phekda DOT freeserve DOT co DOT uk>
X-Mailer: Mozilla 4.77 [en] (X11; U; Linux 2.2.23 i586)
X-Accept-Language: de,fr
MIME-Version: 1.0
To: djgpp-workers AT delorie DOT com
Subject: Re: libc's index
References: <200301011915 DOT h01JF8H21395 AT speedy DOT ludd DOT luth DOT se>
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
Reply-To: djgpp-workers AT delorie DOT com

Hello.

ams AT ludd DOT luth DOT se wrote:
> 
> Hello.
> 
> While looking in the infomanual of libc I'd like to be able to hit "i"
> and the start of a function name and <TAB> to be able to move around
> quickly between functions. (Today I have to go to the alphabetical
> index and scroll down or search for the function.)
> 
> (We actually have one entry in this index, namely radix-64!)

If I hit 'i', I get an error: "No indicies found."
 
> Is that supposed to work and something broke?

I think Eli mentioned once that we need function and variable indices.
 
> Or what is necessary to enable this?

See:

    info texinfo 'printing indices'
    info texinfo indices indexing

Basically: Add index nodes to libc.tex. Use @findex and @vindex respectively
in the texinfo mark-up. We probably should also @tindex for a type index. We
could modify makedoc to generate an @findex per node, but it might be safer to
hand-write them. Maybe someone could write a Perl script to check all the
texinfo sources (.txh) for index entries of appropriate types: at least a
@findex or @vindex per node; a @tindex for nodes that have struct defintions -
"struct foo { ... };".

Bye, Rich =]

-- 
Richard Dawe [ http://www.phekda.freeserve.co.uk/richdawe/ ]