[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: info problems
From: |
Eli Zaretskii |
Subject: |
Re: info problems |
Date: |
Sat, 20 Mar 2004 16:51:11 +0200 |
> Date: Fri, 19 Mar 2004 10:37:04 +0100 (CET)
> From: Werner LEMBERG <address@hidden>
>
> > > Hmm. If I now say `info lilypond', I don't see the top lilypond
> > > page but `5 Invoking LilyPond', one level too deep.
> >
> > That is because that node name is an exact match:
> >
> > * lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond
> > scores.
> >
> > If you type `info GNU LilyPond', you get the top page. If the
> > Invoking LilyPond node is renamed to something that matches worse,
> > you get the top page. Do we want that. Suggestions for a name?
>
> The name is OK -- there is no better name. Other info files like that
> for dvips have the same problem. I suggest to add a new command to
> texinfo which maps certain command line arguments to certain nodes,
> e.g.
>
> @commandlineargtonode lilypond,top
This will cause more trouble than help, I think: when a user types
"info lilypond" it is not at all clear to me that she wants to see
the Top node.
It is IMHO much better to modify the @direntry line so that the
resultant DIR menu item says
* Using lilypond: (lilypond/lilypond)Invoking LilyPond. Titling LilyPond
scores.
or some such. In general, it's a bad idea to have Usage style nodes
referenced by menu items that are labeled with the program's name.