Re: Undefined concepts used in Learning Manual
John Sellers wrote In reading through the Learning manual, all concepts seeming to be well introduced before using them in examples. The clarity of these sections could not be better. However in section 2.5.1, Organizing pieces with variables it seems that several concepts are used in examples without having been previously defined. Also new syntax is introduced without explanation. These include paper, variable, types, objects, new kinds of use of backslash, cm, 21.0 (e.g. numbers with decimal points), =, (e.g. quoted strings), line-width (e.g. control variables), etc. This is a valid criticism. An easy solution is to delete this small section, but the real problem is that the tutorial doesn't mention any means of controlling output. The right solution would be to have a short introduction to controlling output, mentioning \paper etc, which would be a suitable vehicle to introduce the other topics you mention. Then the example would flow nicely later. I'll make a note to look at this. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
definition of paper
In the Learning manual, I searched the one page version for paper and found
that the concept
\paper { }
is nowhere defined or explained.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: definition of paper
Am 29.11.2008 um 19:59 schrieb John Sellers:
In the Learning manual, I searched the one page version for paper
and found
that the concept
\paper { }
is nowhere defined or explained.
If you're really interested, in section 3.1 How LilyPond input files
work, there is a brief introduction to these more advanced concepts.
The LilyPond input format is quite free-form, giving experienced
users a lot of flexibility to structure their files however they
wish. But this flexibility can make things confusing for new users.
This section will explain some of this structure, but may gloss over
some details in favor of simplicity. For a complete description of
the input format, see File structure.
The link to file structure (in the Notation Reference) goes on to
say: that, among other things, \paper is an output definition. And
that Such a definition at the toplevel changes the default book-wide
settings.
Also, since the things that can be placed in a \paper block affect
spacing, which isn't covered at all in the Learning Manual, the
relevant section in the Notation Reference re-iterates that a \paper
block affects scores in a book, and that the global paper layout is
affected by the \paper block.
I'm not saying that it's a particularly lengthy explanation, but it
certainly sufficed for me to understand that a \paper block is
similar to a \layout or \midi block, except that it contains things
specific to how things are laid out on the paper.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 498 in lilypond: completion heads loses tie
Updates: Status: Fixed Labels: fixed_2_11_59 Comment #5 on issue 498 by v.villenave: completion heads loses tie http://code.google.com/p/lilypond/issues/detail?id=498 Done. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 517 in lilypond: missing tuplet number in broken tuplet
Updates: Status: Fixed Labels: fixed_2_11_65 Comment #2 on issue 517 by v.villenave: missing tuplet number in broken tuplet http://code.google.com/p/lilypond/issues/detail?id=517 Thanks, I'll verify it with the next release. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-lilypond
