Re: info problems

2004-03-22 Thread Eli Zaretskii
> Date: Fri, 19 Mar 2004 12:00:10 -0500
> From: [EMAIL PROTECTED] (Karl Berry)
> 
> >   * lilypond: (lilypond/lilypond)Invoking LilyPond.  Titling LilyPond scores.
> 
> How about simply not including that entry, and just have the top-level
> entry?

Indeed.

> This ties into another topic, handling different types of entries.  For
> instance, there's both a function and a command named printf.  Man
> handles this nicely, with man 1 vs. man 3.  Info has never had a
> graceful way to deal with it.  (I don't have any brilliant ideas,
> either.)

How about

info libc printf
vs
info bash printf

?  Info supports this even now.  To me, this is more intuitive and has
more probability of hitting the right topic than the man-style section
number.  I can never remember whether a specific function is in
section 2 or section 3, or which section describes special files like
etc/fstab.


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: info problems

2004-03-22 Thread Eli Zaretskii
> Date: Fri, 19 Mar 2004 10:37:04 +0100 (CET)
> From: Werner LEMBERG <[EMAIL PROTECTED]>
> 
> > > 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.


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel


Re: bad html formatting

2002-09-29 Thread Eli Zaretskii


On Sat, 28 Sep 2002, Karl Berry wrote:

> What's the reason for the `'?
> 
> It seems that @example and the like always insert  (line 503 of
> insertion.c).  I don't know why, seems like just  would be better.
> I'll see if I can dig up a reason for the , if not, I'll try getting
> rid of it.

Isn't the reason the fact that makeinfo does a close_paragraph?

Anyway, in general, I'd advise against removing code we don't understand, 
it has bitten us in the past...


___
Lilypond-devel mailing list
[EMAIL PROTECTED]
http://mail.gnu.org/mailman/listinfo/lilypond-devel