\airytone
takes three arguments: a circle radius, a degree of fullness
(from 0 - 1) and a line thickness. Generally, in the modern rep, an open circle (0) corresponds to all air and a full circle (1) corresponds to a full, robust tone.
What's this? Searching the LSR Browse by date Contributing Snippet database | Browsing items 60−69 out of 924 |
\markup \fill-line { \column { "line1" "line2" ... } \column { "line1" "line2" ... } }
to create text markup in multiple columns (for example, writing out the text of various stanzas after the score). However, the column widths are calculated from the contents, so columns from different markups are not aligned with each other.\columns
macro, which makes each column exactly 1/n of the line-width, thus aligning even columns of different markups. The syntax stays the same, only that one has to use \columns
instead of \fill-line
:
\markup \columns { \column{"default column 1" "line 2"} \column{"column 2, wider than the rest" "line 2"} \column{"c 3" "line 2"} }
ambitus
,
breathing-sign
, clef
, custos
,
staff-bar
, left-edge
, key-cancellation
,
key-signature
, and time-signature
.
In such cases, text marks will be horizontally centered above the object. However this can be changed, as demonstrated on the second line of this example (in a score with multiple staves, this setting should be done for all the staves).
LEFT
, CENTER
or RIGHT
of NoteColumn
grobs by overriding the property
endpoint-alignments
, which is a pair of numbers representing
the left and right ends of the hairpin. endpoint-alignments
are expected to be directions (either -1, 0 or 1). Other values
will be transformed with a warning. The right end of a hairpin
terminating at a rest is not affected, always ending at the left edge
of the rest.
Sometimes you may want to get an sorted index of the pieces contained in a book. Often the \table-of-content
command does this job quite well.
However, the problem with it is, that it sorts always by page numbers. For books containing many songs it is common to have an index sorted by letters or topics.
Both is possible with this snippet. Its code takes the code of ./ly/toc-init.ly and defines three new commands \indexItem
, \indexSection
and \index
. The first two are used to define index items, the last one will create the output.
\indexItem
and \indexSection
both take two arguments (string, markup). The first is used to calculate the order of the items in the output, the second one contains the markup that is actually printed.
\markuplist \index \indexItem #"Berta" \markup "Berta" \indexItem #"Clown" \markup "Clown" \indexItem #"Adam" \markup "Adam"
By setting the first argument of \indexItem
and \indexSection
to a different value than the second it is possible to create heavily customized sorted indices. A topic based index can be achieved by:
\markuplist \index \indexSection #"spring" \markup \smallCaps "Songs of Spring" \indexItem #"spring - I Like the Flowers" \markup "I Like the Flowers" \indexItem #"spring - Der Winter ist vergangen" \markup "Der Winter ist vergangen" \indexSection #"rock" \markup \smallCaps "Rock Songs" \indexItem #"rock - Stairway to Heaven" \markup "Stairway to heaven" \indexItem #"rock - Nothing Else Matters" \markup "Nothing Else Matters"
Limitations:
It is not yet possible to create multiple indices, for example an alphabetical sorted and a topic based one.
To achieve that a few additions to the snippet are nessecary which I had not yet time to implement by now.