Comment #6 on issue 1700 by carl.d.s...@gmail.com: Chord names collide when
several note-columns lay in between
http://code.google.com/p/lilypond/issues/detail?id=1700
Here's a workaround. Set noChordSymbol to "", and then use an r after the
offending chord.
\version "2.12" % same in
Comment #3 on issue 2069 by k-ohara5...@oco.net: Patch: More nuanced
BarLine extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
Carl, can you post the reason /why/ you like the old version?
Is it only because the chord names are un
Comment #2 on issue 2069 by carl.d.s...@gmail.com: Patch: More nuanced
BarLine extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
In screenshot.png above, I prefer the behavior of the old version with
respect to the barlines -- I
Comment #1 on issue 2071 by mts...@gmail.com: Collision of hyphen and
barline
http://code.google.com/p/lilypond/issues/detail?id=2071
I think this issue should be marked as Invalid. There is no obvious
workaround for it. Like any other grob, LyricHyphen can be whited out if
this interse
Ok ... bon... d'accord mais encore ???
2011/12/2 alice
> installer lilypond
>
>
> ___
> bug-lilypond mailing list
> bug-lilypond@gnu.org
> https://lists.gnu.org/mailman/listinfo/bug-lilypond
>
___
bug-lil
Updates:
Status: Verified
Comment #14 on issue 1723 by ma...@gregoriana.sk: beam fails to extend over
rest, intermittently
http://code.google.com/p/lilypond/issues/detail?id=1723
(No comment was entered for this change.)
___
bug-lilypond m
2011/11/30 Christopher Schlosser
> %This is e.g. a problem for engraving a choral piece with barlines in
> mensural
> style. Maybe this is a special case of bug #2061, but I wasn't sure.
>
> \version "2.14.2"
> \new StaffGroup <<
>\new Staff { r1 r}
>%Collision of hyphen and barli
Status: Accepted
Owner:
Labels: Type-Ugly
New issue 2071 by ma...@gregoriana.sk: Collision of hyphen and barline
http://code.google.com/p/lilypond/issues/detail?id=2071
This is e.g. a problem for engraving a choral piece with barlines in
mensural
style.
\new StaffGroup <<
\new S
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2070 by d...@gnu.org: Patch: Don't wrap EventChord around
rhythmic events by default.
http://code.google.com/p/lilypond/issues/detail?id=2070
Don't wrap EventChord around rhythmic events by default.
This changes quite a num
Updates:
Status: Fixed
Comment #35 on issue 1567 by pkx1...@gmail.com: Add documentation for
footnotes
http://code.google.com/p/lilypond/issues/detail?id=1567
Pushed to staging
995c53474b89205d2261207fd76ffe08307427e0
James
___
bug-lilyp
Updates:
Status: Started
Owner: mts...@gmail.com
Labels: -Patch-new Patch-review
Comment #1 on issue 2069 by pkx1...@gmail.com: Patch: More nuanced BarLine
extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2069 by mts...@gmail.com: Patch: More nuanced BarLine
extra-spacing-height to allow tighter horizontal spacing
http://code.google.com/p/lilypond/issues/detail?id=2069
More nuanced BarLine extra-spacing-height to allow tighte
Updates:
Status: Verified
Comment #37 on issue 11 by ma...@gregoriana.sk: beamlet on wrong side of
tuplet sixteenth
http://code.google.com/p/lilypond/issues/detail?id=11
(No comment was entered for this change.)
___
bug-lilypond mailing li
Comment #7 on issue 2067 by mts...@gmail.com: Patch: Give \displayLilyMusic
and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Hey,
Just got through thinking about this - there are several times when, while
debugging Scheme code, I'll include
Updates:
Status: Verified
Comment #25 on issue 1572 by ma...@gregoriana.sk: Change chord name
separator and inversion separator, separately
http://code.google.com/p/lilypond/issues/detail?id=1572
(No comment was entered for this change.)
_
Updates:
Status: Verified
Comment #15 on issue 1838 by ma...@gregoriana.sk: Make accidental styles
available as context mods
http://code.google.com/p/lilypond/issues/detail?id=1838
(No comment was entered for this change.)
___
bug-lilypond
Updates:
Status: Verified
Comment #8 on issue 2014 by ma...@gregoriana.sk: Patch: Improve HTML output
of regression tests
http://code.google.com/p/lilypond/issues/detail?id=2014
(No comment was entered for this change.)
___
bug-lilypond ma
Valentin Villenave writes:
> On Fri, Dec 2, 2011 at 10:14 AM, David Kastrup wrote:
>
>> Upgrade, rinse and repeat. Up to now, your problems have exclusively
>> been unrelated to the nature of the patches, but rather because of
>> bugs slipping through the current regtest net that could be fixed
Updates:
Status: Verified
Comment #19 on issue 2051 by ma...@gregoriana.sk: Patch: Better pure
heights for slurs
http://code.google.com/p/lilypond/issues/detail?id=2051
(No comment was entered for this change.)
___
bug-lilypond mailing lis
Updates:
Status: Verified
Comment #8 on issue 2052 by ma...@gregoriana.sk: Patch: Asserts that
footnotes are being numbered correctly.
http://code.google.com/p/lilypond/issues/detail?id=2052
(No comment was entered for this change.)
___
bu
Updates:
Status: Verified
Comment #5 on issue 2055 by ma...@gregoriana.sk: Patch: Make 2-argument
form of \accidentalStyle
http://code.google.com/p/lilypond/issues/detail?id=2055
(No comment was entered for this change.)
___
bug-lilypond m
On Fri, Dec 2, 2011 at 10:14 AM, David Kastrup wrote:
> The port-line/port-filename values that it had when reading a literal
> string. Of course, this approach would not work when we are talking
> about a constructed string.
[Which precisely happens to be what I'm using eval-line for in my
fram
Le Dec 2, 2011 à 10:41 AM, lilyp...@googlecode.com a écrit :
>
> So Mike: can you recheck your 5ac2664c2207e8dfa1734d786e5c7b214b275521
> checkin using --no-optimize or whatever else it was we used to check for
> undead objects?
I'm a bit short on time now, but I'll do my best to check it in t
installer lilypond
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Status: New
Owner:
Labels: Type-Enhancement Patch-new
New issue 2068 by gra...@percival-music.ca: Patch: Doc: CG: add
instructions for staging branch
http://code.google.com/p/lilypond/issues/detail?id=2068
Doc: CG: add instructions for staging branch
http://codereview.appspot.com/544008
Valentin Villenave writes:
> On Fri, Dec 2, 2011 at 1:05 AM, David Kastrup wrote:
>> The reason is that eval-string in Guile does not set
>> port-line/port-filename to sensible values and I use them for making
>> sensible error messages actually pointing to the source of the error.
>
> What woul
Updates:
Status: Fixed
Labels: -Patch-push fixed_2_15_21
Comment #7 on issue 2011 by gra...@percival-music.ca: configure doesn't
like clang++
http://code.google.com/p/lilypond/issues/detail?id=2011
pushed 2b76b924d478e68baaacfca52c6819d4c15b4c56
_
Updates:
Cc: mts...@gmail.com
Comment #6 on issue 2067 by d...@gnu.org: Patch: Give \displayLilyMusic and
\displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
That patch does not just touch page breaking, but it also introduces Grob
arrays.
Comment #5 on issue 2067 by pkx1...@gmail.com: Patch: Give
\displayLilyMusic and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
I can but not until later today - although I note that this checkin was
done '13 hours' ago (for comparison) wherea
Comment #4 on issue 2067 by d...@gnu.org: Patch: Give \displayLilyMusic and
\displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Interesting but I can't imagine it being related. Can you double-check
that the message is introduced by this particula
Updates:
Labels: -Patch-new Patch-needs_work
Comment #3 on issue 2067 by pkx1...@gmail.com: Patch: Give
\displayLilyMusic and \displayMusic optional port arguments.
http://code.google.com/p/lilypond/issues/detail?id=2067
Passes make but make check gives me
--snip--
/home/jlowe/lilypo
Comment #6 on issue 2066 by mts...@gmail.com: Patch: Prevents accidentals
from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
Well, so much for that idea.
At least I have a test case. Use this snippet of code:
{
%\override Staff . BarLine #'extra-spacing-
Updates:
Labels: -Patch-new Patch-review
Comment #29 on issue 2057 by pkx1...@gmail.com: Hairpin hits barline at
line break
http://code.google.com/p/lilypond/issues/detail?id=2057
PAsses make and make check
James
___
bug-lilypond mailing
On Fri, Dec 2, 2011 at 1:05 AM, David Kastrup wrote:
> The reason is that eval-string in Guile does not set
> port-line/port-filename to sensible values and I use them for making
> sensible error messages actually pointing to the source of the error.
What would be "sensible values" here? Does it
Comment #5 on issue 2066 by mts...@gmail.com: Patch: Prevents accidentals
from hanging over barlines.
http://code.google.com/p/lilypond/issues/detail?id=2066
That's a good question.
I'm honestly not sure how to automate this (one could override the BarLine
#'extra-spacing-height, but this w
35 matches
Mail list logo
