Re: Issue 1063 in lilypond: Reverting nested property fails to restore default value if preceded by override in same grob

Updates: Owner: Carl.D.Sorensen Comment #3 on issue 1063 by Carl.D.Sorensen: Reverting nested property fails to restore default value if preceded by override in same grob http://code.google.com/p/lilypond/issues/detail?id=1063 First review of patch is back to Rodolfo. Once he respond

Re: Issue 1096 in lilypond: ly:parser-parse-string segfaults when directly called at toplevel

Comment #3 on issue 1096 by musiccomposition: ly:parser-parse-string segfaults when directly called at toplevel http://code.google.com/p/lilypond/issues/detail?id=1096 The problem is that the embedded scm causes a recursive yyparse() to be invokved. However, when the string input is parsed,

Re: Issue 1060 in lilypond: Add Funk-style shape note heads

Updates: Owner: Carl.D.Sorensen Comment #8 on issue 1060 by Carl.D.Sorensen: Add Funk-style shape note heads http://code.google.com/p/lilypond/issues/detail?id=1060 By all means, pass them by others. The more the merrier. But I'm confused about the choice of passing them by the typeset

Re: Issue 1060 in lilypond: Add Funk-style shape note heads

Comment #7 on issue 1060 by will.fitzgerald: Add Funk-style shape note heads http://code.google.com/p/lilypond/issues/detail?id=1060 Carl, Let me pass them by the person who typeset the 26th edition of the Harmonia Sacra, ok? And maybe another person or two. Will _

Re: Issue 1060 in lilypond: Add Funk-style shape note heads

Comment #6 on issue 1060 by Carl.D.Sorensen: Add Funk-style shape note heads http://code.google.com/p/lilypond/issues/detail?id=1060 I have completed a draft of Funk note heads. Please comment on these heads. If the aesthetics need to be improved, please share suggestions with me. Thanks,

Re: Issue 1089 in lilypond: DynamicTextSpanner not printed

Comment #3 on issue 1089 by musiccomposition: DynamicTextSpanner not printed http://code.google.com/p/lilypond/issues/detail?id=1089 So, it should be a warning, not just work like it did before? ___ bug-lilypond mailing list bug-lilypond@gnu.org http

Re: Issue 1102 in lilypond: [PATCH] Build: require all glyphs for `font-table.ly'

Updates: Status: Verified Comment #1 on issue 1102 by percival.music.ca: [PATCH] Build: require all glyphs for `font-table.ly' http://code.google.com/p/lilypond/issues/detail?id=1102 Thanks, but this was added as c0dce0a771c0681bd3e44fbf246cd2436b6c20a2 back on 2010-03-12. Hmm...

Issue 1101 in lilypond: PATCH: accessors for note-column's dot-column, accidentals

Status: New Owner: Labels: Type-Enhancement Patch New issue 1101 by neziap: PATCH: accessors for note-column's dot-column, accidentals http://code.google.com/p/lilypond/issues/detail?id=1101 http://lists.gnu.org/archive/html/lilypond-devel/2010-04/msg00042.html

Issue 1100 in lilypond: \line inside \concat should keep its 'word-space

Status: Accepted Owner: Labels: Type-Defect Priority-Low New issue 1100 by brownian.box: \line inside \concat should keep its 'word-space http://code.google.com/p/lilypond/issues/detail?id=1100 Reported by Kieren MacMillan: http://lists.gnu.org/archive/html/bug-lilypond/2010-05/msg00225.

Issue 1102 in lilypond: [PATCH] Build: require all glyphs for `font-table.ly'

Status: New Owner: Labels: Type-Enhancement Patch New issue 1102 by neziap: [PATCH] Build: require all glyphs for `font-table.ly' http://code.google.com/p/lilypond/issues/detail?id=1102 http://lists.gnu.org/archive/html/lilypond-devel/2010-03/msg00198.html

Re: \concat + \line = unexpected behaviour [?]

Hi Dmytro, > I've looked at formatting commands and decided to add this to tracker: > http://code.google.com/p/lilypond/issues/detail?id=1100 Thanks! Kieren. ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.gnu.org/mailman/listinfo/bug-l

Re: \concat + \line = unexpected behaviour [?]

On Wed 26 May 2010, 08:28 Kieren MacMillan wrote: > I'm just pointing out the inconsistency: Lilypond *should* IMHO give > > \markup { \concat { pre \line { a b c } post } } ==> prea b cpost > > but doesn't. I've looked at formatting commands and decided to add this to tracker: http://code

Re: \concat + \line = unexpected behaviour [?]

> I'm just pointing out the inconsistency: Lilypond *should* IMHO give > > \markup { \concat { pre \line { a b c } post } } ==> prea b cpost > > but doesn't. I agree. Werner ___ bug-lilypond mailing list bug-lilypond@gnu.org http://lists.

Re: \concat + \line = unexpected behaviour [?]

Hi Werner, >> i.e., in the snippet >> \markup { \line { pre \concat { a b c } post } } >> the 'word-space should be overridden to not-zero, right? > > The output should be > pre abc post > Everything else is a bug IMHO. I agree... and in this case, Lilypond does the right thing. I'm just poi

Issue 1099 in lilypond: flat collides with stem in some cases

Status: Accepted Owner: Labels: Type-Collision Priority-Medium New issue 1099 by brownian.box: flat collides with stem in some cases http://code.google.com/p/lilypond/issues/detail?id=1099 Reported by Nick Payne: http://lists.gnu.org/archive/html/lilypond-user/2010-05/msg00323.html \versio