Copying to -bugs for an issue.
--
Phil Holmes
- Original Message -
From: Peter Crighton
To: LilyPond Mailing List
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentation
Hello all,
in the documentation about percussion notation it is said that you ne
This has been fixed already.
Trevor
Phil Holmes wrote Thursday, January 16, 2014 3:25 PM
> Copying to -bugs for an issue.
- Original Message -
From: Peter Crighton
To: LilyPond Mailing List
Sent: Wednesday, January 15, 2014 10:27 PM
Subject: Error in documentation
Hell
"Phil Holmes" writes:
> Peter Crighton wrote:
>>
>>
>> Hello all,
>> in the documentation about percussion notation it is said that you need to
>> include the Parenthesis_engraver in order to use \parenthesize –
>> http://lilypond.org/doc/v2.19/Documentation/notation/common-notation-for-pe
David Kastrup wrote Thursday, January 16, 2014 5:47 AM
> Just pushed a fix for the parenthesis engraver to staging. The chord
> bracket stuff was already fixed shortly before:
>
> commit 4bdb9204b1b682b38bd76afc03e5d629621428f1
> Should cherry-pick into translation, I think, so that this moves
Eluze writes:
> maybe this example makes more sense:
>
> lyr=\lyricsto A \new Lyrics \lyricmode { this is bad. }
> mus=\new Voice= A {a b c}
> << \mus \lyr >>
>
> this triggers an error
>
> writing mus =... (with a space before the equal sign) works as well as
> enclosing the assignment before in
Hello,
Gilberto Agostinho wrote
> When using \autochange, the slope of the beams look ugly against the staff
> lines
Gilberto Agostinho wrote
> [...] this seems to be a problem with any staff changes. So does this
> qualify as a bug? I personally think it doesn't look right at all, and to
> ma
David Kastrup wrote
> Eluze <
> eluzew@
> > writes:
>
>> David Kastrup wrote
>>> A={c d e}
>>> \addlyrics { this is bad }
>>>
>>> would be legitimate, so the assignment is not complete without looking
>>> at the next token, and the next token is \A which is not defined.
>>
>> how then would you
