Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread lilypond
Comment #7 on issue 1322 by tdanielsmusic: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 We can't so that (do away with \new and \context). The context names would then have to be defined in the parser, preventing users from

Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread lilypond
Comment #8 on issue 1322 by v.villenave: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 Carl: This is very convenient when combining multiple input files in different ways to produce multiple editions. This is more or less

Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread Trevor Daniels
Graham wrote Wednesday, October 13, 2010 4:43 AM Comment #3 on issue 1322 by percival.music.ca: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 I took about 30 seconds to think about it. Then spend a little longer. - I

Re: Issue 1323 in lilypond: Back to documentation index tocframe link is broken in online dev manuals

2010-10-13 Thread lilypond
Comment #4 on issue 1323 by paconet.org: Back to documentation index tocframe link is broken in online dev manuals http://code.google.com/p/lilypond/issues/detail?id=1323 It's still broken in Spanish. Go to http://lilypond.org/doc/latest/Documentation/notation/ In Firefox, press

Enhancement: adapt the \skip command to automatically-aligned lyrics mode

2010-10-13 Thread Valentin Villenave
NR 2.1.2 states that The \skip command must be followed by a number, but this number is ignored in lyrics which derive their durations from the notes in an associated melody through \addlyrics or \lyricsto. Each \skip skips a single note of any value, irrespective of the value of the following

Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread lilypond
Comment #9 on issue 1322 by Carl.D.Sorensen: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 As Trevor posted in the list (but not on the issue here), a change requiring \context to include a name for the context would be

Re: Slur/fermata collision

2010-10-13 Thread Graham Percival
On Wed, Oct 13, 2010 at 05:56:36PM +0100, Phil Holmes wrote: In the attached PNG, you can just see that the first slur collides with the fermata, and the second collides with the note-head. Would this count as a minor bug, or something not even worth bothering with? It's not something to get

Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread lilypond
Comment #10 on issue 1322 by tdanielsmusic: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 I'm with Carl, except I think I'd prefer \new to continue working if the context is named, /provided/ that the context does not exist. If

Re: Issue 1322 in lilypond: \context must die (whenever \new can be used instead)

2010-10-13 Thread lilypond
Comment #11 on issue 1322 by percival.music.ca: \context must die (whenever \new can be used instead) http://code.google.com/p/lilypond/issues/detail?id=1322 @comment 7 Trevor: it's not impossible to let a user add items to the parser. I'm claiming this would be easy, or that it might

Re: Issue 1323 in lilypond: Back to documentation index tocframe link is broken in online dev manuals

2010-10-13 Thread lilypond
Updates: Status: Started Comment #5 on issue 1323 by percival.music.ca: Back to documentation index tocframe link is broken in online dev manuals http://code.google.com/p/lilypond/issues/detail?id=1323 Needs to support translations in line 357 of

Issue 1324 in lilypond: Ugly cross-staff collisions

2010-10-13 Thread lilypond
Status: Accepted Owner: Labels: Type-Collision New issue 1324 by RalphBugList: Ugly cross-staff collisions http://code.google.com/p/lilypond/issues/detail?id=1324 in the cross-staff + beamed notes = sucks dpt, I'm pretty sure I've already seen this one (more than once), but when looking at

Re: Ugly cross-staff collisions: duplicate?

2010-10-13 Thread Ralph Palmer
On Fri, Oct 8, 2010 at 6:32 AM, Valentin Villenave valen...@villenave.netwrote: Hi everybody, in the cross-staff + beamed notes = sucks dpt, I'm pretty sure I've already seen this one (more than once), but when looking at the tracker I can find dozens of similar issues but not quite this one

Issue 1325 in lilypond: Volta bracket going over to next line

2010-10-13 Thread lilypond
Status: Accepted Owner: Labels: Type-Defect New issue 1325 by RalphBugList: Volta bracket going over to next line http://code.google.com/p/lilypond/issues/detail?id=1325 I did look through the tracker but nothing obvious. I have also tested this with 2.12.latest and get the same issue.

Re: Problem with volta bracket going over to next line

2010-10-13 Thread Ralph Palmer
On Sun, Oct 10, 2010 at 4:54 PM, James Lowe james.l...@datacore.com wrote: Hello, I did look through the tracker but nothing obvious. I have also tested this with 2.12.latest and get the same issue. This is the snippet that is as small as I can seem to get it (from a piece I was