Simon Albrecht | 5 Mar 12:29 2015

Music function fails

Hello list,

I use a music function to tweak the X and Y-offsets for a grob. This 
function used to work in 2.19.8, but in 2.19.15 and .16 it just remains 
without effect – there are no kind of messages. Any idea where this 
might come from?

Best, Simon
Attachment ( text/x-lilypond, 594 bytes
bug-lilypond mailing list
bug-lilypond <at>
Tom Pennello | 5 Mar 10:13 2015

Bug: a staff thta never breaks in lilypond.

This small program produces a staff that never breaks.
It took me a while to find the problem in a 145-measure score.

\version "2.18.2"

% This produces a staff that never breaks.

\new Staff {
  \time 3/4
  \key f \major
  \relative c'' {
  % The e4 chord is too long.  Remove the . and the bug goes away.
  \chordmode { e2 e4. }
    f4 f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f
    f4 f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f f

I can't attach a png to this email, so I trust you'll be able to reproduce
it yourself easily.

Helge | 3 Mar 07:03 2015

connect directed arpeggio

I have a problem with  connecting arpeggio. The arrow of
 \arpeggioArrowDown or -Up vanishes when I connect the arpeggios of two
 staves. You can reproduce it with the example below. Comment out the
 connectArpeggios line and you see arrows.

 Is this a known bug?

 Regards Helge

 \version "2.18.0"

 upperHarpII = \relative c'' {
   \arpeggioArrowDown  <b c>2\arpeggio r
 lowerHarpII = \relative c' {
   \clef bass
   \arpeggioArrowDown  <a e a,>2\arpeggio r

 \score {
   \new PianoStaff \with {
     connectArpeggios = ##t
   } <<
     \new Staff \upperHarpII
     \new Staff \lowerHarpII


GnuPG fingerprint: EDCE F8C8 B727 6CC5 7006  05C1 BD3F EADC 8922 1F61
(Continue reading)

Simon Albrecht | 25 Feb 21:29 2015

NullVoice and Ambitus crash (regression?)


if in Lily 2.19.15 NullVoice is \consisted with the "Ambitus_engraver", 
there are (for one NullVoice) three instances of

programming error: tried to get a translation for something that is no 
child of mine

which cause the program to abort. This used to work in v2.19.8. Minimal 
example attached.

In case you ask why I’d want this: I have two choir parts assembled in 
one staff using \partcombine. Two NullVoices are required for separate 
lyrics, and for separate ambitus.

Yours, Simon

Attachment ( text/x-lilypond, 175 bytes
bug-lilypond mailing list
bug-lilypond <at>
Luming | 23 Feb 14:25 2015

2 problems using NullVoice to align lyrics

1. When I added a NullVoice into a staff with a existing homophony Voice, 
all previously-correctly-placed rest marks are engraved in a polyphonic
manner (in the lower-half of the staff instead of in the middle), unless it
is a "r" or a "s" in the NullVoice at the same time.
I did not notice any mark besides rest mark having this problem. All notes
are engraved correctly.
Using "\oneVoice" command on the rest marks did not fix this.

2. When using " word __ " to create a extender line in Lyrics, if the note
that the word aligned to is from a NullVoice and followed by "r" or "s", the
extender line will extend all the way until first note after the followed
rests, instead of stopping after last tied/slurred note.

Thank you for reading this.
I'm new to LilyPond and I work with Windows 8.1, Frescobaldi 2.0.16 and
Lilypond 2.18.2
Masamichi Hosoda | 19 Feb 14:57 2015
Picon and don't have \version


In lilypond current master branch, I found that
files don't have ``\version''.

Then, GUB's ``make lilypond'' is failed.
Here is a patch.

--- a/input/regression/	2015-02-19 
22:39:42.810909400 +0900
+++ b/input/regression/	2015-02-19 
22:40:59.826572000 +0900
 <at>  <at>  -1,3 +1,5  <at>  <at> 
+\version "2.19.16"
 \header {
   texidoc = "The numbered time signature style prints a fraction."
--- a/input/regression/	2015-02-19 
22:37:58.662289400 +0900
+++ b/input/regression/	2015-02-19 
22:41:15.639086900 +0900
 <at>  <at>  -1,3 +1,5  <at>  <at> 
(Continue reading)

Simon Albrecht | 18 Feb 18:27 2015

\tweak fails on MultiMeasureRests

Hello list,

it seems that the \tweak command does not have any effect on multi 
measure rests, neither with nor without specifying the grob:

\version "2.19.8"

{ \tweak MultiMeasureRest.color #red R1 \tweak color #red R1 }

I couldn't find an entry in the issue tracker, nor any mention of this 
in the docs. It should probably be mentioned in the Known issues and 
warnings at the bottom of both 

Yours, Simon
Simon Albrecht | 18 Feb 10:46 2015

Hairpin crash

Hello list,

see the attached code: The hairpins collide, if and only if
-- there is a barline in \n (comment to test)
-- and there is a half note or rest or multi-measure-rest in the other part.
Somewhat obscure and difficult to isolate, but easy to work around.

Yours, Simon

Attachment ( text/x-lilypond, 347 bytes
bug-lilypond mailing list
bug-lilypond <at>
Federico Bruni | 17 Feb 21:32 2015

[LSR] remove snippet 142

Hi all

This snippet sounds out-of-date:

As hammer-on and pull-off in tablature are documented:

Should it be deleted?
H. S. Teoh | 13 Feb 02:33 2015

Another example of issue 601: accidentals cause cross-staff arpeggios to collide

# This bug appears to be similar or identical to issue 601: accidentals
# cause cross-staff arpeggios to collide.
# The following example shows the note a4 being struck through by the arpeggio
# lines in both lilypond-2.18.2 and git HEAD (lilypond-2.19.16). The
# attached image shows the output fragment from lilypond-2.19.16.
\version "2.18.1"
\new PianoStaff <<
	\set PianoStaff.connectArpeggios = ##t
	\new Staff \relative c'' { c2.  bes,4\arpeggio }
	\new Staff \relative c' { \clef bass r2 a4 c,\arpeggio }
bug-lilypond mailing list
bug-lilypond <at>
Ralph Palmer | 6 Feb 15:04 2015

Apologies for Issues 4279 and 4280

Greetings -
I didn't realize that Google was using my private email address, so Issue
4279 was not submitted correctly (no issue label), and 4280 was a complete
mistake. I do not know how to delete an issue, so please, someone either
delete or recycle Issue 4280 and give a correct label to Issue 4279.
I will take care to avoid this situation in the future.
I appreciate your time and attention,