bug backlog finished; please re-report anything missing

We have now caught up on our backlog of bugs. If you are aware of any problems that are not fixed in 2.13.26 and have not been added to our tracker, then unfortunately the report has been lost. Please report the bug again by following the guidelines here:

Re: lilypondtool and timidity won't play from the jedit internal midi player.

alex stone wrote: lilypond version 2.13.25 lilypondtool version (D/L direct from jedit plugin repo) 2.12.894 I've been working all day on trying to get the internal midi player in jedit/lilypondtool to work with timidity. (as lilypondtool has no jackmidi as yet) No luck so far. I have timidity

cross staff glissando / slur

I am working on piano music in Lilypond. Can't find in the manual how to create cross staff glissando and cross staff slur. How can that be done? Hans ___ lilypond-user mailing list lilypond-user@gnu.org

Re: lilypondtool and timidity won't play from the jedit internal midi player.

On Mon, Jun 28, 2010 at 2:08 PM, Bertalan Fodor (LilyPondTool) lilypondt...@organum.hu wrote: alex stone wrote: lilypond version 2.13.25 lilypondtool version (D/L direct from jedit plugin repo) 2.12.894 I've been working all day on trying to get the internal midi player in

Re: cross staff glissando / slur

On 28.06.2010, at 20:47, Hans van Eck wrote: I am working on piano music in Lilypond. Can't find in the manual how to create cross staff glissando and cross staff slur. How can that be done? Hans Hello, For cross-staff glissando, see section 1.3.3, Lines, in the selected snippets,

Turn off merge-differently-headed for one note

I have a guitar piece in two voices in which I'm using \mergeDifferentlyHeadedOn in the \score section to merge the same notes in the two voices. However, there are a couple of places where I want the same note played on two different strings and therefore don't want the notes merged. I tried

bad spacing and paginationin 2.13.26

Hello, I downloaded 2.13.26 to compile my overture. The result is bad, because it not only uses more pages, but also reported a (de)crescendo too small warning. I reinstalled 2.13.24-2, then the warning disappeared, and the page amount is back to normal. Are there any spacing changes in 26?

Re: bad spacing and paginationin 2.13.26

Hi Haipeng, Yes there were spacing/breaking changes between 24 and 26. They are in a tricky area of code, so it is quite possible (and even probable) that they caused bad things. Can you provide a minimal example showing the problem? If you only say the result is bad, I believe you but I