Re: Something wrong/strange about flags?

2011/12/26 Neil Puttock : > > On 25 Dec 2011 23:01, "Thomas Morley" wrote: > >> I think there could be some difficulties to find the correct >> condition, when I create my own definitions/functions: >> >> \version "2.15.20" >> >> displayGrob = >>       \once\override Stem #'after-line-breaking = >

Re: Something wrong/strange about flags?

On 25 Dec 2011 23:01, "Thomas Morley" wrote: > I think there could be some difficulties to find the correct > condition, when I create my own definitions/functions: > > \version "2.15.20" > > displayGrob = > \once\override Stem #'after-line-breaking = > #(lambda (grob) > (let*

Re: Something wrong/strange about flags?

Hi Neil, 2011/12/25 Neil Puttock : > > On 25 Dec 2011 22:27, "Thomas Morley" wrote: > >> 1. IR 3.2.109 stem-interface states: "flag (graphical (layout) object) >>  A pointer to a Flag object." >>    I would have expected: () (there is no flag!) > > The unused flag is suicided.  A pointer to the s

TextScript isn't entirely scaled, while using another "staff-size"

Hi, the following example shows that the markup isn't scaled correct, according to the changed "staff-size" \version "2.15.20" music = { c'-\markup { "XXX" \draw-line #'(0 . 4) } } \new StaffGroup << \new Staff \with { fontSize = #-20 \override StaffSymbol #'staff-spa

Re: Something wrong/strange about flags?

On 25 Dec 2011 22:27, "Thomas Morley" wrote: > 1. IR 3.2.109 stem-interface states: "flag (graphical (layout) object) > A pointer to a Flag object." >I would have expected: () (there is no flag!) The unused flag is suicided. A pointer to the suicided grob still exists. > 2. AFAIK a Grob "

Something wrong/strange about flags?

Hi, while manipulating stems, flags and beams I noticed something strange about flags: \version "2.15.20" displayGrob = \once \override Stem #'after-line-breaking = #(lambda (grob) (let* ((beam (ly:grob-object grob 'beam)) (flag (ly:grob-object grob 'fl

Re: Issue 766 in lilypond: Indent should automatically adapt to instrument names' length.

Updates: Cc: -n.putt...@gmail.com -joenee...@gmail.com nicolas@gmail.com Comment #5 on issue 766 by elu...@gmail.com: Indent should automatically adapt to instrument names' length. http://code.google.com/p/lilypond/issues/detail?id=766 maybe not exactly what is asked for, but look

Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

Comment #29 on issue 1110 by d...@gnu.org: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 Concerning comment #27: I was not complaining, and I have not claimed ownership of this issue anyway. There is not much enthus

Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision

Updates: Labels: Patch-review Comment #2 on issue 2138 by lilypond...@gmail.com: Patch: Doc: NR @knownissues for #'ignore-collision http://code.google.com/p/lilypond/issues/detail?id=2138#c2 Patchy the autobot says: LGTM. ___ bug-lilypond

Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency

Updates: Labels: Patch-review Comment #4 on issue 2136 by lilypond...@gmail.com: Patch: Doc: Usage --include option layout consistency http://code.google.com/p/lilypond/issues/detail?id=2136#c4 Patchy the autobot says: LGTM. ___ bug-lilypo

Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation

Updates: Labels: Patch-review Comment #2 on issue 2137 by lilypond...@gmail.com: Patch: Doc: NR improve 'visibility' of 'q' operation http://code.google.com/p/lilypond/issues/detail?id=2137#c2 Patchy the autobot says: LGTM. ___ bug-lilypon

Issue 2140 in lilypond: warning issued when --default-defining an option that lilypond doesn't know

Status: Accepted Owner: Labels: Warning New issue 2140 by elu...@gmail.com: warning issued when --default-defining an option that lilypond doesn't know http://code.google.com/p/lilypond/issues/detail?id=2140 when you override a known option like point-and-click everything is OK. but whe

Issue 2139 in lilypond: Doc AU: command line options - where to use equal signs in short and long term definitions

Status: Accepted Owner: Labels: Type-Documentation New issue 2139 by elu...@gmail.com: Doc AU: command line options - where to use equal signs in short and long term definitions http://code.google.com/p/lilypond/issues/detail?id=2139 when reading the line -d,--define-default=var=val i

Re: Issue 2111 in lilypond: documentation of include-settings in Usage

Comment #4 on issue 2111 by elu...@gmail.com: documentation of include-settings in Usage http://code.google.com/p/lilypond/issues/detail?id=2111 hi James sorry for the confusion i'm doing, partly due to my disorganized mind, partly to the fact that many of these issues are only minor and i

Re: Collision of hyphen and barline

Phil (mike) On 2 December 2011 07:16, m...@apollinemike.com wrote: > Le Dec 1, 2011 à 6:21 PM, Phil Holmes a écrit : > >> "Christopher Schlosser" wrote in message >> news:loom.2030t213409-...@post.gmane.org... I'm not top posting. >>> >>> %This is e.g. a problem for engraving a choral

Re: Feature request: multiplication should work on notes, chords and all rests

Pavel, On 16 December 2011 03:26, Pavel Roskin wrote: > Quoting Xavier Scheuer : > >> On 15 December 2011 22:58, Pavel Roskin wrote: >>> >>> Hello! >>> >>> For some reason, multiplication only works on full-measure rests >>> and silent rests. >>> >>> It would be nice to make it work on notes, ch

Re: Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision

Updates: Status: Started Owner: pkx1...@gmail.com Labels: -Type-Enhancement Type-Documentation Comment #1 on issue 2138 by pkx1...@gmail.com: Patch: Doc: NR @knownissues for #'ignore-collision http://code.google.com/p/lilypond/issues/detail?id=2138 (No comment was ente

Issue 2138 in lilypond: Patch: Doc: NR @knownissues for #'ignore-collision

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2138 by pkx1...@gmail.com: Patch: Doc: NR @knownissues for #'ignore-collision http://code.google.com/p/lilypond/issues/detail?id=2138 Doc: NR @knownissues for #'ignore-collision Added @knownissue when using #'ignore-collisi

Re: Issue 1110 in lilypond: Wrong octave of repetition chord with \relative and #{ #} syntax

Updates: Labels: -Priority-Medium Comment #28 on issue 1110 by pkx1...@gmail.com: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 Hello Issue 2137 Has been added to allay the documentation concerns. James __

Re: Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation

Updates: Owner: pkx1...@gmail.com Labels: -Type-Enhancement Type-Documentation Comment #1 on issue 2137 by pkx1...@gmail.com: Patch: Doc: NR improve 'visibility' of 'q' operation http://code.google.com/p/lilypond/issues/detail?id=2137 (No comment was entered for this change.)

Re: Issue 2111 in lilypond: documentation of include-settings in Usage

Updates: Status: Started Owner: pkx1...@gmail.com Comment #3 on issue 2111 by pkx1...@gmail.com: documentation of include-settings in Usage http://code.google.com/p/lilypond/issues/detail?id=2111 Eluze, We have a few things going on here, so I'd like to break it down if only

Re: Issue 2136 in lilypond: Patch: Doc: Usage --include option layout consistency

Updates: Status: Started Owner: pkx1...@gmail.com Labels: -Type-Enhancement Type-Documentation Comment #3 on issue 2136 by pkx1...@gmail.com: Patch: Doc: Usage --include option layout consistency http://code.google.com/p/lilypond/issues/detail?id=2136 (No comment was e

Issue 2137 in lilypond: Patch: Doc: NR improve 'visibility' of 'q' operation

Status: New Owner: Labels: Type-Enhancement Patch-new New issue 2137 by pkx1...@gmail.com: Patch: Doc: NR improve 'visibility' of 'q' operation http://code.google.com/p/lilypond/issues/detail?id=2137 Doc: NR improve 'visibility' of 'q' operation Improve visibility of q (repeated chord)