Re: Issue 2057 in lilypond: Hairpin hits barline at line break

Comment #48 on issue 2057 by mts...@gmail.com: Hairpin hits barline at line break http://code.google.com/p/lilypond/issues/detail?id=2057 Hey - sorry to be a patch push nag, but I'd like to get my queue cleared out. This patch hasn't changed since December 6th save the occasional rebase a

Re: Issue 2098 in lilypond: Patch: Now use astyle 2.02.1

Comment #1 on issue 2098 by gra...@percival-music.ca: Patch: Now use astyle 2.02.1 http://code.google.com/p/lilypond/issues/detail?id=2098#c1 Now use astyle 2.02.1 Run astyle (two separate commits, merged together in rietveld) http://codereview.appspot.com/5478072 ___

Re: Issue 460 in lilypond: bar numbers for broken bars

Comment #26 on issue 460 by mts...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460 All the comments from Reinhold (and Neil) were addressed in the patch set from Dec 8. Is it ok to push the patch? Cheers, MS ___

Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions.

Updates: Status: Fixed Comment #5 on issue 2064 by mts...@gmail.com: Patch: Prevents Slur vs Dots collisions. http://code.google.com/p/lilypond/issues/detail?id=2064 Pushed to staging as fb79c584a99fe6571a23a9770efd6e1ede3a5772. ___ bug-li

Issue 2098 in lilypond: Patch: Now use astyle 2.02.1

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2098 by gra...@percival-music.ca: Patch: Now use astyle 2.02.1 http://code.google.com/p/lilypond/issues/detail?id=2098 Now use astyle 2.02.1 Run astyle (two separate commits, merged together in rietveld) http://codereview.ap

Re: Issue 1686 in lilypond: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available

Issue 1686: Compile scheme files to scm/out when using Guile V2.n. Also load and run .go files if available http://code.google.com/p/lilypond/issues/detail?id=1686 This issue is no longer blocking issue 1826. See http://code.google.com/p/lilypond/issues/detail?id=1826 -- You received this mess

Re: Issue 1826 in lilypond: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated

Updates: Status: Fixed Blockedon: -1686 Comment #9 on issue 1826 by ianhuli...@gmail.com: Guile 2.0 compat: `conditional-circle-markup' definition needs to be relocated http://code.google.com/p/lilypond/issues/detail?id=1826 Fixed by work on Issue 2026 - markup is now a separa

Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module

Updates: Status: Fixed Labels: -Patch-push Comment #9 on issue 2026 by ianhuli...@gmail.com: Make markup utility definitions available via new (scm markup-utility-defs) scheme module http://code.google.com/p/lilypond/issues/detail?id=2026 Pushed to staging as f8e03b1..6b15f83

Re: Issue 460 in lilypond: bar numbers for broken bars

Updates: Labels: -Patch-review Patch-needs_work Comment #25 on issue 460 by colinpkc...@gmail.com: bar numbers for broken bars http://code.google.com/p/lilypond/issues/detail?id=460 Comments by Reinhold on Rietveld ___ bug-lilypond mailing

Re: Issue 2026 in lilypond: Make markup utility definitions available via new (scm markup-utility-defs) scheme module

Updates: Labels: -Patch-countdown Patch-push Comment #8 on issue 2026 by colinpkc...@gmail.com: Make markup utility definitions available via new (scm markup-utility-defs) scheme module http://code.google.com/p/lilypond/issues/detail?id=2026 Counted down to 20111211

Re: Issue 2080 in lilypond: Request for better cross referencing of ornaments

Updates: Labels: -Patch-countdown Patch-push Comment #4 on issue 2080 by colinpkc...@gmail.com: Request for better cross referencing of ornaments http://code.google.com/p/lilypond/issues/detail?id=2080 Counted down to 20111211 and not one but two LGTM from Graham

Re: Issue 2076 in lilypond: Doc: improve NR 1.6.3 Instrument names (better to use \with )

Updates: Labels: -Patch-countdown Patch-push Comment #12 on issue 2076 by colinpkc...@gmail.com: Doc: improve NR 1.6.3 Instrument names (better to use \with ) http://code.google.com/p/lilypond/issues/detail?id=2076 Counted down to 20111211

Re: Issue 2064 in lilypond: Patch: Prevents Slur vs Dots collisions.

Comment #4 on issue 2064 by colinpkc...@gmail.com: Patch: Prevents Slur vs Dots collisions. http://code.google.com/p/lilypond/issues/detail?id=2064 Ping Mike: this has been on patch-push for a week now . . . If I were the nagging type, that's what I'd be doing now! __

Re: Issue 2059 in lilypond: Bar numbering of alternatives

Updates: Labels: -Patch-push Patch-needs_work Comment #16 on issue 2059 by colinpkc...@gmail.com: Bar numbering of alternatives http://code.google.com/p/lilypond/issues/detail?id=2059 Per Neil and Mike's comments on Rietveld. ___ bug-lilyp

Re: Issue 2077 in lilypond: Patch: Provide Scheme sandbox.

Updates: Status: Verified Comment #6 on issue 2077 by colingh...@gmail.com: Patch: Provide Scheme sandbox. http://code.google.com/p/lilypond/issues/detail?id=2077 Verified this is present in the repo. ___ bug-lilypond mailing list bug-lily

Re: Issue 2081 in lilypond: Patch: Remove spurious spaces from music expression display, adapt tests.

Updates: Status: Verified Comment #3 on issue 2081 by colingh...@gmail.com: Patch: Remove spurious spaces from music expression display, adapt tests. http://code.google.com/p/lilypond/issues/detail?id=2081 Verified this is present in the repo. ___

Re: Issue 694 in lilypond: Enhancement: easier use of microtone accidentals

Updates: Status: Accepted Comment #13 on issue 694 by k-ohara5...@oco.net: Enhancement: easier use of microtone accidentals http://code.google.com/p/lilypond/issues/detail?id=694 Yes, this is 80% a documentation issue. The new snippets were originally intended for these documentati

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Comment #5 on issue 2065 by mts...@gmail.com: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065 Slight re-correction: there are actually no SpanBarStubs created in the example above. Everything is done through extra-spac

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Comment #4 on issue 2065 by k-ohara5...@oco.net: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065 The problem is ... not taken into account in the Separation_item::boxes. Just to correct the record, cross-staff items like

Re: Issue 586 in lilypond: Cross-staff slur causes a weird output

Updates: Status: Fixed Comment #4 on issue 586 by mts...@gmail.com: Cross-staff slur causes a weird output http://code.google.com/p/lilypond/issues/detail?id=586 I take it back - I didn't realize that the E was in the tuplet. So the bracket is correct. Marking as fixed. ___

Re: Issue 257 in lilypond: collision accent and tuplet bracket

Comment #3 on issue 257 by mts...@gmail.com: collision accent and tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=257 The workaround is now: \override TupletBracket #'outside-staff-priority = #2. Or if you want the script above, you can set the Script outside-staff-prior

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Updates: Labels: Patch-new Comment #3 on issue 2065 by mts...@gmail.com: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065#c3 Prevents SpanBar Script collisions. http://codereview.appspot.com/5478064

Re: Set global staff size as command line option

On 11 December 2011 01:23, Colin Hall wrote: > > Added as issue 2095 > > http://code.google.com/p/lilypond/issues/detail?id=2095 Thanks! > It looks like the developers have selected some variables, including > paper-size, for inclusion in the ly:set-option feature. I'll create > a feature reque

Re: Issue 1774 in lilypond: Semi-breves unnecessarily shifted

Comment #3 on issue 1774 by d...@gnu.org: Semi-breves unnecessarily shifted http://code.google.com/p/lilypond/issues/detail?id=1774 I am not sure about that. It would easily be possible to write the source in a way that no voice reversal occurs. How would the singer know that a whole note

Re: metronome markings

"Gerard van Reenen" wrote in message news:loom.20111204t181122-...@post.gmane.org... Probably I have interesting information for you about the metronome marks in children's music of Clementi, Burgnuller, Cramer, Bertini and Cramer. If you give me your email adress I can send it to you. Meanwhi

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Comment #2 on issue 2065 by mts...@gmail.com: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065 Interesting - if you add \override Score . Script #'cross-staff = ##f, it doesn't fix the problem. So the cross-staffitude i

Re: Where to put user ly files on OSX?

"Xavier Scheuer" wrote in message news:CADGqHRejv58mbS=0vewfg4ejoc-go3drmspfrtxvt3qchv5...@mail.gmail.com... On 7 December 2011 02:58, huzzam wrote: Hi-- I'm fairly new to lilypond, and am starting to write my own ly files to include. I want to put them somewhere that will be accessible easi

Issue 2097 in lilypond: Provide lily-include directory

Status: Accepted Owner: Labels: Type-Enhancement New issue 2097 by philehol...@gmail.com: Provide lily-include directory http://code.google.com/p/lilypond/issues/detail?id=2097 Enhancement suggested by Denis Bitouzé: I read the way of including LilyPond files here: http://lilypond.org/doc

Re: $LILYHOME as $TEXMFHOME with LaTeX

"Xavier Scheuer" wrote in message news:cadgqhre_rci+nfxhfltgbakpw8p+lhtcqqz5vde1-aaxgsa...@mail.gmail.com... Could you please add the forwarded feature request to the tracker? Carl said "It seems to me that this would be a useful thing". Graham: "That's a feature request from at least 7 years a

Re: Issue 2048 in lilypond: shiftDurations with negative 2nd argument loops indefinitely

Updates: Status: Verified Comment #11 on issue 2048 by philehol...@gmail.com: shiftDurations with negative 2nd argument loops indefinitely http://code.google.com/p/lilypond/issues/detail?id=2048 (No comment was entered for this change.) __

Re: loglevel=ERROR still emits Warning message

On 11/12/11 11:24, -Eluze wrote: > > when using the recently discussed command line option > > #(use-modules (guile-user)) #(set-global-staff-size mySize) > > the following warning is created WARNING: #f: imported module > (guile-user) overrides core binding `%module-public-interface' > > i tho

Re: Issue 1663 in lilypond: Images missing on web site

Updates: Status: Verified Comment #58 on issue 1663 by philehol...@gmail.com: Images missing on web site http://code.google.com/p/lilypond/issues/detail?id=1663 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-li

Re: Issue 2061 in lilypond: Lyrics collide with bar lines

Updates: Status: Verified Labels: -Patch-push Comment #8 on issue 2061 by philehol...@gmail.com: Lyrics collide with bar lines http://code.google.com/p/lilypond/issues/detail?id=2061 Sorry - my original report should have said 2.15.14, not 2.13.14 - so it was a regression in

Re: loglevel=ERROR still emits Warning message

"-Eluze" wrote in message news:32954783.p...@talk.nabble.com... when using the recently discussed command line option #(use-modules (guile-user)) #(set-global-staff-size mySize) the following warning is created WARNING: #f: imported module (guile-user) overrides core binding `%module-public-i

Re: Issue 2065 in lilypond: Scripts in cross-staff constructions can collide with span bars

Comment #1 on issue 2065 by mts...@gmail.com: Scripts in cross-staff constructions can collide with span bars http://code.google.com/p/lilypond/issues/detail?id=2065 The problem is that the Script is marked as cross-staff and thus not taken into account in the Separation_item::boxes. This

Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

Updates: Labels: Patch-review Comment #2 on issue 2096 by lilypond...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096#c2 Patchy the autobot says: LGTM. ___ bug-l

loglevel=ERROR still emits Warning message

when using the recently discussed command line option #(use-modules (guile-user)) #(set-global-staff-size mySize) the following warning is created WARNING: #f: imported module (guile-user) overrides core binding `%module-public-interface' i thought it's possible to suppress it with the new comm

Re: Issue 2071 in lilypond: Collision of hyphen and barline

Comment #2 on issue 2071 by mts...@gmail.com: Collision of hyphen and barline http://code.google.com/p/lilypond/issues/detail?id=2071 I'm going to mark this as Documentation (i.e. add a paragraph in the dox about whiting out crescendi and lyric hyphens that traverse span bars) unless anyo

Re: Issue 2096 in lilypond: Patch: Implements cross-staff stem avoidance for dynamics.

Comment #1 on issue 2096 by mts...@gmail.com: Patch: Implements cross-staff stem avoidance for dynamics. http://code.google.com/p/lilypond/issues/detail?id=2096#c1 Implements cross-staff stem avoidance for dynamics. http://codereview.appspot.com/5479056