Am Freitag, 28. Mai 2010, um 20:04:41 schrieb Carl Sorensen:
> The first question is: Does the 2.10.33 ouptut match what is asked for from
> the music, i.e. a text crescendo starting on the first note, and ending on
> the second note. I think we both agree that it does not. If you think
> that th
Comment #7 on issue 1092 by pnorcks: Overriding head-direction for
LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1092
Thanks for the explanation, Neil.
Shouldn't LilyPond fail *gracefully* though, in the case of this in
Hi!
I'm experiencing a very annoying (IMO) output with multiline
\header fields.
I don't know if it's a bug or if I'm doing something wrong (actually I
would tend to consider this as a bug).
If I use for example two lines for the "composer" field, the second
line is closer to the following field
Comment #3 on issue 1103 by musiccomposition: Typo in engraver name while
defining new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Thanks for the feedback! I'm attaching a new patch, which should address
your concerns.
Attachments:
Comment #2 on issue 1103 by n.puttock: Typo in engraver name while defining
new contexts causes lilypond to segfault
http://code.google.com/p/lilypond/issues/detail?id=1103
Hi Benjamin,
Thanks for producing this patch so quickly.
Here are a few comments:
+\version "2.12.0"
"2.13.23"
The
Updates:
Labels: -Type-Defect Type-Enhancement
Comment #1 on issue 1100 by n.puttock: \line inside \concat should keep
its 'word-space
http://code.google.com/p/lilypond/issues/detail?id=1100
\concat is basically \markup \override #'(word-space . 0) \line { }, so it
would have
to be
Comment #6 on issue 1092 by n.puttock: Overriding head-direction for
LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1092
Don't override 'head-direction for LaissezVibrerTieColumn. It's not
user-serviceable, since it shou
On 5/28/10 10:31 AM, "Xavier Scheuer" wrote:
> 2010/5/27 :
>
>> Comment #4 on issue 1089 by Carl.D.Sorensen: DynamicTextSpanner not
>>>
>> I actually don't think that 2.10.33 is correct! The crescendo is
>> supposed to end on the 2nd note in the measure according to the input
>> code. But
Hi dear Bug Squad members!
Could you please add this to the tracker as a "new feature request"
(enhancement I think), at least to keep track of this?
Thank you,
Xavier
-- Forwarded message --
From: Xavier Scheuer
Date: 11 May 2010 21:07
Subject: Extend "Completion_heads_engrave
2010/5/15 Neil Puttock :
> Should be pretty simple to do, I'd imagine.
>
> I postponed pushing the fix for #305 since I wanted to incorporate
> some additional features (automatic breaking for \change Staff and
> manual directions), but I'd be happy to work on those features later
> to get this fi
Comment #5 on issue 1092 by pnorcks: Overriding head-direction for
LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1092
I'm getting the segfault too (still).
___
bug-lilypond m
Comment #4 on issue 1092 by brownian.box: Overriding head-direction for
LaissezVibrerTie or LaissezVibrerTieColumn to RIGHT causes segfault
http://code.google.com/p/lilypond/issues/detail?id=1092
On two different ubuntus i've got:
$ LANG=C lilypond lvtie.ly
GNU LilyPond 2.13.22
Processing `.
2010/5/27 :
> Comment #4 on issue 1089 by Carl.D.Sorensen: DynamicTextSpanner not
> printed
> http://code.google.com/p/lilypond/issues/detail?id=1089
>
> There was a decision to add a bit of space to separate the cresc.
> from the p. In so doing, the available space became too short to fit
> both
Updates:
Summary: Enhancement: 'offset for \underline markup function needed (and
proposed)
Comment #2 on issue 1104 by brownian.box: Enhancement: 'offset for
\underline markup function needed (and proposed)
http://code.google.com/p/lilypond/issues/detail?id=1104
Changed Summary field, st
Updates:
Status: Verified
Comment #14 on issue 963 by percival.music.ca: check dependency versions
for 2.14
http://code.google.com/p/lilypond/issues/detail?id=963
I haven't heard any screams from packagers yet, so let's called this done.
_
Updates:
Status: Verified
Comment #12 on issue 771 by percival.music.ca: Instrument names should be
centered accordingly to StartSystem objects in other staves
http://code.google.com/p/lilypond/issues/detail?id=771
(No comment was entered for this change.)
__
Updates:
Status: Verified
Comment #4 on issue 805 by percival.music.ca: Irrelevant configure message
with autoconf and gettext test
http://code.google.com/p/lilypond/issues/detail?id=805
I can't see such warnings any more, so verified.
___
Updates:
Status: Fixed
Labels: fixed_2_13_23
Comment #9 on issue 815 by percival.music.ca: Enhancement: AJAX-powered
search auto-completion for the online documentation
http://code.google.com/p/lilypond/issues/detail?id=815
Pushed as e80874f5c742381c834772cc13ca8c2fa115a712
96
Updates:
Status: Verified
Comment #11 on issue 881 by brownian.box: Arpeggios may collide with
laissezVibrer ties
http://code.google.com/p/lilypond/issues/detail?id=881
(No comment was entered for this change.)
___
bug-lilypond mailing lis
Updates:
Status: Verified
Comment #15 on issue 1056 by brownian.box: Pure-height of stems does not
accurately estimate height
http://code.google.com/p/lilypond/issues/detail?id=1056
(No comment was entered for this change.)
___
bug-lilypon
Updates:
Status: Verified
Comment #4 on issue 1080 by brownian.box: Regression: bar lines in double
bar are positioned too close together
http://code.google.com/p/lilypond/issues/detail?id=1080
(No comment was entered for this change.)
___
21 matches
Mail list logo
