lilypond-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: command index vs. unified index


From: Graham Percival
Subject: Re: command index vs. unified index
Date: Fri, 19 May 2006 21:22:14 -0700

I've finally managed to get them playing nicely together. Commands should be indexed with
@funindex \relative
no @code{} is required.  General concepts continue to be indexed with
@cindex Concept, general

I'm not certain if the command index will be particularly useful, but it's there now and doesn't interfere with the general index.

Cheers,
- Graham

On 19-May-06, at 11:46 AM, Mats Bengtsson wrote:

I actually like having a single index which includes the
commands. However, I don't like the current title of the
index (I know it's not called "Index" for silly technical reasons),
it seems that many people miss that it's actually there.

  /Mats

Graham Percival wrote:

I've been investigating producing an index of commands, but it appears that texinfo can only use each @findex once -- if I have an index of @findex entries, then those entries won't appear in the general index (despite my using @syncodeindex). I've asked for help on the texinfo help list,
http://lists.gnu.org/archive/html/help-texinfo/2006-05/msg00000.html

If it's impossible to use the same @findex entries twice, should we keep our single unified index, or should we split the \commands off into their own index?

- Graham



_______________________________________________
lilypond-devel mailing list
address@hidden
http://lists.gnu.org/mailman/listinfo/lilypond-devel



--
=============================================
        Mats Bengtsson
        Signal Processing
        Signals, Sensors and Systems
        Royal Institute of Technology
        SE-100 44  STOCKHOLM
        Sweden
        Phone: (+46) 8 790 8463                         
       Fax:   (+46) 8 790 7260
        Email: address@hidden
        WWW: http://www.s3.kth.se/~mabe
=============================================






reply via email to

[Prev in Thread] Current Thread [Next in Thread]