Moving the include fixed the appoggiatura problem, but the barNumberChecks
still emit warnings.
Knute Snortum
(via Gmail)
On Sun, May 10, 2015 at 12:16 AM, Federico Bruni wrote:
> I _think_ that this bug report explains the problems you reported here and
> in the previous thread:
> https://co
Added
https://code.google.com/p/lilypond/issues/detail?id=4382
2015-04-27 20:44 GMT+02:00 Carl Sorensen :
> On 4/27/15 10:47 AM, "Federico Bruni" wrote:
>
> >2015-04-27 17:25 GMT+02:00 Kevin Barry :
> >
> >- I'd rather use a conversational approach instead of unordered lists:
> >"Please be awar
Il giorno dom 10 mag 2015 alle 9:26, David Kastrup ha
scritto:
Federico Bruni writes:
Hi Knute
in order to avoid this sort of problems, you should move the include
after the \score block with layout and before the \score with midi.
This tip was recommended on lilypond-user several times
Federico Bruni writes:
> Hi Knute
>
> in order to avoid this sort of problems, you should move the include
> after the \score block with layout and before the \score with midi.
> This tip was recommended on lilypond-user several times but it's not
> present in the documentation:
> http://lilypond
I _think_ that this bug report explains the problems you reported here
and in the previous thread:
https://code.google.com/p/lilypond/issues/detail?id=3696
I suggest using the "workaround" (I see it as a sort of best practice
for using articulate.ly):
move the include after the \score block w
Hi Knute
in order to avoid this sort of problems, you should move the include
after the \score block with layout and before the \score with midi.
This tip was recommended on lilypond-user several times but it's not
present in the documentation:
http://lilypond.org/doc/v2.19/Documentation/notat
