Hello list,
Here is a bizarre little bug I came across today: for some reason, an
invisible rest on a different Staff seems to affect the kneed beamed
stems on a PianoStaff when using \autochange. See:
\version "2.19.28"
A = { c'''16[ c''' c''' c] }
B = {s4\p}
C = {r4\p}
<<
\new PianoSta
Hi Federico,
> On Dec 1, 2015, at 10:56 AM, Federico Bruni wrote:
>
> Thanks for the reminder. I probably forgot it when working on this:
> https://github.com/fedelibre/LilyDev/pull/4
>
> I'll add it tomorrow
That’s great, thanks!
-Paul
___
bug-lilyp
Il giorno lun 30 nov 2015 alle 23:06, Paul Morris
ha scritto:
In CG 2.2, under “Where to get lily-git" it reads:
If you are using LilyDev (see LilyDev) then lily-git should already
be installed and ready to run.
But it seems that this is not the case with LilyDev 4. At least not
when I
> On Tue, 27 Oct 2015 12:18:27 +1100, Andrew Bernard
> said:
A> Using 2.19.30, hoping to avoid the core dumps from 2.19.29, I get
A> the following error on my moderately large score: Preprocessing
A> graphical objects...lilypond:
A>
/home/gub/NewGub/gub/target/linux-64/s
