\autochange bug

2015-12-01 Thread Gilberto Agostinho 

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 PianoStaff \autochange \A

\new Staff \B

>>

<<

\new PianoStaff \autochange \A

\new Staff \C

>>

Producing: 
http://s7.postimg.org/scnuvn1ij/Screenshot_from_2015_12_02_01_30_42.png



Let me know if I can be of any further help with this.

Cheers,
Gilberto
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: lily-git.tcl not fully ready to run on LilyDev 4

2015-12-01 Thread Paul Morris 
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-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: lily-git.tcl not fully ready to run on LilyDev 4

2015-12-01 Thread Federico Bruni 
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 tried it today.  Not a big problem since as it goes on to say:


  If this is not the case you can easily turn it on by adding the 
following line in ~/.bashrc:

  # add lily-git to the PATH
  PATH=$LILYPOND_GIT/scripts/auxiliar:"${PATH}"


This worked fine, but it would be better not to have to take this 
extra step, for those using lily-git.tcl


-Paul



Hi Paul

Thanks for the reminder. I probably forgot it when working on this:
https://github.com/fedelibre/LilyDev/pull/4

I'll add it tomorrow


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond

Re: Assertion failed

2015-12-01 Thread anders . vinjar 
> 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/src/lilypond-git.sv.gnu.org--lilypond.git-release-unstable/flower/include/interval.hh:227:
A> T Interval_t::center() const [with T = double]: Assertion
A> `!is_empty ()' failed.  Exited with exit status 1.

I'm hitting the same break here (also in a complex score).  The commit
which makes it break is from May:

  a4cc910a  Issue 2787: Sanitize usage of -DDEBUG, -DNDEBUG and assert

The commit is empty, but message indicates some flags vs. debugging or
optimisation related to asserting things were being changed, which fits
well with the break message.  What was changed which might be looked
into?

I tried tuning some flags with current sources, without getting
anywhere.  Is there something to pass to ../configure to get rid of
(this) asserts?

Thanks,

-anders


___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond