Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread Peekay Ex
Mike, Phil, On Mon, Oct 17, 2011 at 7:16 AM, m...@apollinemike.com wrote: > On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote: > >> Status: Accepted >> Owner: >> Labels: Type-Critical Regression >> >> New issue 1971 by philehol...@gmail.com: Slashed flags no longer work >> http://c

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread m...@apollinemike.com
On Oct 17, 2011, at 12:43 AM, Graham Percival wrote: > On Sun, Oct 16, 2011 at 11:02:22PM +0200, m...@apollinemike.com wrote: >> >> I think that by running convert-ly via the script in 10.9.4, >> duplicate Flag #'transparent statements will be issued (every >> time convert-ly sees a Stem #'transp

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread m...@apollinemike.com
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote: > Status: Accepted > Owner: > Labels: Type-Critical Regression > > New issue 1971 by philehol...@gmail.com: Slashed flags no longer work > http://code.google.com/p/lilypond/issues/detail?id=1971 > > The NR > (http://lilypond.org/

Re: Issue 1926 in lilypond: 2.15.12 processing speed problems

2011-10-16 Thread lilypond
Updates: Labels: -Patch-needs_work Patch-review Comment #21 on issue 1926 by k-ohara5...@oco.net: 2.15.12 processing speed problems http://code.google.com/p/lilypond/issues/detail?id=1926 The only outstanding comments are to push as two commits, and it is pretty clear how the commit

Re: Issue 1972 in lilypond: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions

2011-10-16 Thread lilypond
Comment #2 on issue 1972 by k-ohara5...@oco.net: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972 Clearly this is due to the change for issue 1193 so I've put a link here in a comment on Reitveld for tha

Re: Issue 1962 in lilypond: Visible gap in span bar when making lyrics to avoid bar lines

2011-10-16 Thread lilypond
Comment #1 on issue 1962 by brownian@gmail.com: Visible gap in span bar when making lyrics to avoid bar lines http://code.google.com/p/lilypond/issues/detail?id=1962 As many lyrics lines, as many gaps. I've not marked it as critical, because i am too late -- 2.14 already had this (this

Re: Issue 1973 in lilypond: Enhancement request: add ability to create wav/mp3

2011-10-16 Thread lilypond
Updates: Status: Invalid Comment #1 on issue 1973 by percival.music...@gmail.com: Enhancement request: add ability to create wav/mp3 http://code.google.com/p/lilypond/issues/detail?id=1973 Creating audio is not the task of lilypond; that is the job of other projects. You already me

Issue 1973 in lilypond: Enhancement request: add ability to create wav/mp3

2011-10-16 Thread lilypond
Status: Accepted Owner: Labels: Type-Enhancement New issue 1973 by colinpkc...@gmail.com: Enhancement request: add ability to create wav/mp3 http://code.google.com/p/lilypond/issues/detail?id=1973 I use lilypond to create practise tracks for a couple of the choirs willing to put up wit

Re: Issue 1972 in lilypond: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions

2011-10-16 Thread lilypond
Comment #1 on issue 1972 by pkx1...@gmail.com: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972 % this also produces stuck 100% CPU at 'Drawing systems...' \version "2.15.13" \relative c' { \override St

Issue 1972 in lilypond: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions

2011-10-16 Thread lilypond
Status: Accepted Owner: Labels: Type-Crash New issue 1972 by colinpkc...@gmail.com: Seg fault and 100% CPU when using \override Staff.StaffSymbol #'ledger-positions http://code.google.com/p/lilypond/issues/detail?id=1972 Reported by James Lowe: % this produces a segfault \version "2.15.

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread Graham Percival
On Sun, Oct 16, 2011 at 11:02:22PM +0200, m...@apollinemike.com wrote: > > I think that by running convert-ly via the script in 10.9.4, > duplicate Flag #'transparent statements will be issued (every > time convert-ly sees a Stem #'transparent, it adds a Flag > #'transparent for files created befo

Re: wrong alignment when repeating music with different text on one line

2011-10-16 Thread -Eluze
Phil Holmes-2 wrote: > > This looks to me like correct behaviour. You've created extra Lyrics > contexts, and Lilypond stacks them one above the other. This is as > illustrated in the NR. If I was doing what you're showing, I would use > \skip: > > << > \new Staff { > \new Voice = "

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread m...@apollinemike.com
On Oct 16, 2011, at 10:07 PM, Graham Percival wrote: > On Sun, Oct 16, 2011 at 12:13:27PM +0200, m...@apollinemike.com wrote: >> >> Is there a way to run convert-ly on the docs to eliminate this sorta problem? > > Yes. By some incredible coincidence, it is discussed > in CG 10.9.4 Automatically

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread Graham Percival
On Sun, Oct 16, 2011 at 12:13:27PM +0200, m...@apollinemike.com wrote: > > Is there a way to run convert-ly on the docs to eliminate this sorta problem? Yes. By some incredible coincidence, it is discussed in CG 10.9.4 Automatically update documentation http://lilypond.org/doc/v2.15/Documentatio

Re: Issue 1701 in lilypond: default accidental style prints too many 'extra' naturals

2011-10-16 Thread lilypond
Comment #22 on issue 1701 by percival.music...@gmail.com: default accidental style prints too many 'extra' naturals http://code.google.com/p/lilypond/issues/detail?id=1701 no more 2.14 releases are planned. Let the translators deal with the change. __

Re: Issue 1951 in lilypond: Scripts collide with accidentals

2011-10-16 Thread lilypond
Updates: Labels: Patch-review Comment #8 on issue 1951 by percival.music...@gmail.com: Scripts collide with accidentals http://code.google.com/p/lilypond/issues/detail?id=1951#c8 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list

Re: 2.15.14 will not run on Mac x86

2011-10-16 Thread Stan Sanderson
On Oct 16, 2011, at 4:49 AM, "Phil Holmes" wrote: > "Stan Sanderson" wrote in message > news:0d770350-3bf2-4555-8f4c-ee7b5d86c...@gmail.com... >> Sad to report that LilyPond v 2.15.14-1 fails to run on my iMac. Error >> report follows below. >> As previously reported, v 2.15.8 is the last vers

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-16 Thread lilypond
Comment #5 on issue 1943 by stans...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 I downloaded http://klarinett.li/lilypond/lilypond-2.15.14-1.darwin-x86-no64.tar.bz2 and expanded it. Unfortunately, I am getting the same error

Re: Issue 1912 in lilypond: Horizontal spacing depends on stem 'direction

2011-10-16 Thread lilypond
Updates: Status: Invalid Owner: d...@gnu.org Comment #3 on issue 1912 by d...@gnu.org: Horizontal spacing depends on stem 'direction http://code.google.com/p/lilypond/issues/detail?id=1912 Closed in line with comment #2. May be reopened if evidence is brought forward that t

Re: Issue 625 in lilypond: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby

2011-10-16 Thread lilypond
Updates: Labels: -Type-Enhancement -Priority-Postponed Type-Ugly Comment #4 on issue 625 by pkx1...@gmail.com: lilypond -dpreview ignores extent of bracket unless another outside staff object is nearby http://code.google.com/p/lilypond/issues/detail?id=625 This seems to be an issue st

Re: Issue 1943 in lilypond: lilypond after 2.15.8 fails on x86 Macs

2011-10-16 Thread lilypond
Comment #4 on issue 1943 by chh...@gmail.com: lilypond after 2.15.8 fails on x86 Macs http://code.google.com/p/lilypond/issues/detail?id=1943 Ok, I have stripped the x86_64 parts from the application. In theory it should now work on 10.5 too. Unfortunately, I have no access to such a syst

Re: Issue 637 in lilypond: keep-inside-line doesn't affect crescendoText

2011-10-16 Thread lilypond
Updates: Owner: --- Labels: -Type-Enhancement -Priority-Medium Type-Ugly Comment #2 on issue 637 by pkx1...@gmail.com: keep-inside-line doesn't affect crescendoText http://code.google.com/p/lilypond/issues/detail?id=637 Still an issue in 2.15.15. Attachments: 2_15_15.

Re: Issue 202 in lilypond: merge-differently-headed should work for more than just two voices

2011-10-16 Thread lilypond
Updates: Summary: merge-differently-headed should work for more than just two voices Owner: --- Labels: -Priority-Low Comment #8 on issue 202 by pkx1...@gmail.com: merge-differently-headed should work for more than just two voices http://code.google.com/p/lilypond/issu

Re: Issue 458 in lilypond: Ties from different voices must be handled on the staff level to avoid clashes with notes

2011-10-16 Thread lilypond
Updates: Summary: Ties from different voices must be handled on the staff level to avoid clashes with notes Owner: --- Labels: -Type-Enhancement -Priority-Postponed Type-Ugly Comment #6 on issue 458 by pkx1...@gmail.com: Ties from different voices must be handled on the staf

Re: Issue 584 in lilypond: Outside-staff placement of hairpins is 'too approximate'

2011-10-16 Thread lilypond
Updates: Summary: Outside-staff placement of hairpins is 'too approximate' Owner: --- Labels: -Type-Enhancement -Priority-Medium Type-Ugly Comment #2 on issue 584 by pkx1...@gmail.com: Outside-staff placement of hairpins is 'too approximate' http://code.google.com/p/lil

Re: Issue 609 in lilypond: wrong placement of \markup on MultiMeasureRest

2011-10-16 Thread lilypond
Updates: Owner: --- Labels: -Type-Enhancement -Priority-Low Type-Ugly Comment #4 on issue 609 by pkx1...@gmail.com: wrong placement of \markup on MultiMeasureRest http://code.google.com/p/lilypond/issues/detail?id=609 The results of 2.15.15 are attached. Attached to skips (wo

Re: Issue 556 in lilypond: fingeringOrientations affects cross-voices arpeggio

2011-10-16 Thread lilypond
Updates: Owner: --- Labels: -Type-Defect -Priority-Medium Type-Ugly Comment #2 on issue 556 by pkx1...@gmail.com: fingeringOrientations affects cross-voices arpeggio http://code.google.com/p/lilypond/issues/detail?id=556 Still an issue for 2.15.15 - with some very subtle diffe

Re: Issue 702 in lilypond: "Moment is not increasing" when combining Lyrics in a sequential way

2011-10-16 Thread lilypond
Updates: Summary: "Moment is not increasing" when combining Lyrics in a sequential way Owner: --- Labels: -Priority-Medium Comment #5 on issue 702 by pkx1...@gmail.com: "Moment is not increasing" when combining Lyrics in a sequential way http://code.google.com/p/lilypond/is

Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding

2011-10-16 Thread lilypond
Updates: Labels: -Patch-new -Fixed_2_15_14 fixed_2_15_14 Comment #16 on issue 1855 by tdaniels...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 (No comment was entered for this change.) _

Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse

2011-10-16 Thread lilypond
Updates: Labels: -Patch-new Comment #16 on issue 1846 by tdaniels...@gmail.com: Improves horizontal spacing of axis groups that SpanBar grobs traverse http://code.google.com/p/lilypond/issues/detail?id=1846 (No comment was entered for this change.) __

Re: Issue 1812 in lilypond: NR Context Layout Order rewrite (5.1.7)

2011-10-16 Thread lilypond
Updates: Labels: -Priority-Low -Patch-push fixed_2_15_14 Comment #14 on issue 1812 by tdaniels...@gmail.com: NR Context Layout Order rewrite (5.1.7) http://code.google.com/p/lilypond/issues/detail?id=1812 (No comment was entered for this change.)

Re: Issue 1778 in lilypond: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting

2011-10-16 Thread lilypond
Updates: Labels: -Priority-Medium -Patch-push fixed_2_15_15 Comment #8 on issue 1778 by tdaniels...@gmail.com: slashedGrace function (graces with slashed stems but no slur, e.g. when grace is tied) needs documenting http://code.google.com/p/lilypond/issues/detail?id=1778 (No comment

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

2011-10-16 Thread lilypond
Comment #18 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 While we are at it: what is the desired output of \parallelMusic #'(A B) { 1 | | q | q |} \new Voice { << \relative c' \A \\ \re

Re: Issue 307 in lilypond: collision slur with tuplet bracket

2011-10-16 Thread lilypond
Updates: Status: Fixed Labels: -Patch-push fixed_2_15_15 Comment #22 on issue 307 by tdaniels...@gmail.com: collision slur with tuplet bracket http://code.google.com/p/lilypond/issues/detail?id=307 Mike says: [Fixed] by increasing the slur region based on the height of the ext

Re: Issue 1403 in lilypond: Enhancement: defining postfix commands in Scheme.

2011-10-16 Thread lilypond
Updates: Labels: -Priority-Medium -Syntax fixed_2_15_13 Comment #3 on issue 1403 by tdaniels...@gmail.com: Enhancement: defining postfix commands in Scheme. http://code.google.com/p/lilypond/issues/detail?id=1403 (No comment was entered for this change.)

Re: Issue 451 in lilypond: Enhancement: a more flexible \parallelMusic syntax when used with \relative

2011-10-16 Thread lilypond
Comment #4 on issue 451 by d...@gnu.org: Enhancement: a more flexible \parallelMusic syntax when used with \relative http://code.google.com/p/lilypond/issues/detail?id=451 You can put a \relative around the _uses_ of the identifiers \parallelMusic defines, and this will work as expected, wi

Re: Issue 1403 in lilypond: Enhancement: defining postfix commands in Scheme.

2011-10-16 Thread lilypond
Updates: Status: Fixed Owner: d...@gnu.org Comment #2 on issue 1403 by d...@gnu.org: Enhancement: defining postfix commands in Scheme. http://code.google.com/p/lilypond/issues/detail?id=1403 define-event-function has been implemented with commit 5aac8e8d8e2b1fc490354cba2cdec

Re: Issue 1970 in lilypond: string-tunings-init.scm does not exist

2011-10-16 Thread lilypond
Updates: Status: Fixed Owner: pkx1...@gmail.com Comment #1 on issue 1970 by pkx1...@gmail.com: string-tunings-init.scm does not exist http://code.google.com/p/lilypond/issues/detail?id=1970 Pushed as commit 969556627f76d211db81bd8b5de780f2d179445 Thought this was trivial en

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

2011-10-16 Thread David Kastrup
Reinhold Kainhofer writes: > Am Sonntag, 16. Oktober 2011, 12:29:14 schrieb Werner LEMBERG: >> >> It is extremely helpful in writing keyboard music. >> > >> > Typing aids are the kind of thing that editor macros should do rather >> > than the music processor. >> >> Here I strongly disagree. Th

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

2011-10-16 Thread Reinhold Kainhofer
Am Sonntag, 16. Oktober 2011, 12:29:14 schrieb Werner LEMBERG: > >> It is extremely helpful in writing keyboard music. > > > > Typing aids are the kind of thing that editor macros should do rather > > than the music processor. > > Here I strongly disagree. There must be means to make LilyPond's

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

2011-10-16 Thread Werner LEMBERG
>> It is extremely helpful in writing keyboard music. > > Typing aids are the kind of thing that editor macros should do rather > than the music processor. Here I strongly disagree. There must be means to make LilyPond's `source code' readable by people also which don't use an editor's special l

Re: Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread m...@apollinemike.com
On Oct 16, 2011, at 12:06 PM, lilyp...@googlecode.com wrote: > Status: Accepted > Owner: > Labels: Type-Critical Regression > > New issue 1971 by philehol...@gmail.com: Slashed flags no longer work > http://code.google.com/p/lilypond/issues/detail?id=1971 > > The NR > (http://lilypond.org/

Issue 1971 in lilypond: Slashed flags no longer work

2011-10-16 Thread lilypond
Status: Accepted Owner: Labels: Type-Critical Regression New issue 1971 by philehol...@gmail.com: Slashed flags no longer work http://code.google.com/p/lilypond/issues/detail?id=1971 The NR (http://lilypond.org/doc/v2.15/Documentation/notation/special-rhythmic-concerns)says: "The slash

Re: 2.15.14 will not run on Mac x86

2011-10-16 Thread Phil Holmes
"Stan Sanderson" wrote in message news:0d770350-3bf2-4555-8f4c-ee7b5d86c...@gmail.com... Sad to report that LilyPond v 2.15.14-1 fails to run on my iMac. Error report follows below. As previously reported, v 2.15.8 is the last version to run successfully. The previously suggested workaround was

Re: NR 2.4.3, file for predefined tunings

2011-10-16 Thread Phil Holmes
"Federico Bruni" wrote in message news:4e99bacb.7010...@gmail.com... I think I've found a bug in the doc: Notation Reference 2.4.3 In the "See also" subsection there is: "Installed Files: ‘scm/string-tunings-init.scm’ contains predefined banjo tunings." That file doesn't exist. AFAIK, the f

Issue 1970 in lilypond: string-tunings-init.scm does not exist

2011-10-16 Thread lilypond
Status: Accepted Owner: Labels: Type-Documentation New issue 1970 by philehol...@gmail.com: string-tunings-init.scm does not exist http://code.google.com/p/lilypond/issues/detail?id=1970 Reported by Federico Bruni: Notation Reference 2.4.3 In the "See also" subsection there is: "Instal

Re: musicxml2ly: placement="below|above" in not converted

2011-10-16 Thread Phil Holmes
"Patrick Schmidt" wrote in message news:f28f3dd7-1cc7-495c-aeff-0b1de3b2d...@gmx.de... Hi Reinhold, the values "above" and "below" of the 'placement'-attribute don't seem to show any effect in the -element, e.g. when you substitute "below" for "above" in the following code the result of the c

Issue 1969 in lilypond: Placement attribute in MusicXML has no effect

2011-10-16 Thread lilypond
Status: Accepted Owner: Labels: Type-Scripts New issue 1969 by philehol...@gmail.com: Placement attribute in MusicXML has no effect http://code.google.com/p/lilypond/issues/detail?id=1969 Reported by Patrick Schmidt: the values "above" and "below" of the 'placement'-attribute don't seem

Re: wrong alignment when repeating music with different text on one line

2011-10-16 Thread Phil Holmes
"-Eluze" wrote in message news:32622828.p...@talk.nabble.com... with the following code - derived from the example in NR under Lyrics and Repeats - the text of the 2nd lyric voice is not correctly aligned. this seems to happen when such repeats occur on the same line/system only. Eluze << \

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

2011-10-16 Thread David Kastrup
Werner LEMBERG writes: >> I don't actually like the q feature at all, [...] > > Why not? It is ill-defined (as you can see from the examples I posted) and makes music much less machine-readable. > It is extremely helpful in writing keyboard music. Typing aids are the kind of thing that editor

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

2011-10-16 Thread lilypond
Comment #17 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 Getting back to comment #11 from Werner: IMHO, q is such a useful feature that even a `heavy' solution would be worth to implem

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

2011-10-16 Thread Werner LEMBERG
> I don't actually like the q feature at all, [...] Why not? It is extremely helpful in writing keyboard music. That it is a syntactically difficult issue and causes implementation headaches is something different... Werner ___ bug-lilypond mai

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

2011-10-16 Thread lilypond
Comment #16 on issue 1110 by lemzw...@gmail.com: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 Oh, yes, *now* I remember the whole discussion... Good morning, brain :-) ___

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

2011-10-16 Thread David Kastrup
Peekay Ex writes: > On Sun, Oct 16, 2011 at 8:29 AM, wrote: >> >> Comment #14 on issue 1110 by lemzw...@gmail.com: Wrong octave of repetition >> chord with \relative and #{ #} syntax >> http://code.google.com/p/lilypond/issues/detail?id=1110 >> >> Maybe I'm naïve, but shouldn't q be processed m

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

2011-10-16 Thread Peekay Ex
Hello, On Sun, Oct 16, 2011 at 8:29 AM, wrote: > > Comment #14 on issue 1110 by lemzw...@gmail.com: Wrong octave of repetition > chord with \relative and #{ #} syntax > http://code.google.com/p/lilypond/issues/detail?id=1110 > > Maybe I'm naïve, but shouldn't q be processed much earlier?  What w

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

2011-10-16 Thread lilypond
Comment #15 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 Yes, you are naive. q is processed much earlier, in the lexer and parser. But do you really want to have \relative c' { q }

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

2011-10-16 Thread lilypond
Comment #14 on issue 1110 by lemzw...@gmail.com: Wrong octave of repetition chord with \relative and #{ #} syntax http://code.google.com/p/lilypond/issues/detail?id=1110 Maybe I'm naïve, but shouldn't q be processed much earlier? What we really want IMHO is a shorthand at the input level t