Re: Avoid repeats of 'staff-affinity' warning; change text. (issue4278058)

2011-03-22 Thread Joe Neeman
On Mon, Mar 21, 2011 at 8:11 PM, Keith OHara k-ohara5...@oco.net wrote: On Sat, 19 Mar 2011 22:46:51 -0700, Joe Neeman joenee...@gmail.com wrote: It might cause problems if pure is true. When the method is called with pure, it shouldn't cause any side effects. For a concrete example, this

Re: Avoid repeats of 'staff-affinity' warning; change text. (issue4278058)

2011-03-22 Thread Keith OHara
On Mon, 21 Mar 2011 23:06:12 -0700, Joe Neeman joenee...@gmail.com wrote: Unfortunately, if I protect the assignment to the property with an if (!pure), I am letting the page-breaking planning rely on the user-requested affinities, and then changing them for the page-layout phase. The

Re: Avoid repeats of 'staff-affinity' warning; change text. (issue4278058)

2011-03-22 Thread Joe Neeman
On Mon, Mar 21, 2011 at 11:18 PM, Keith OHara k-ohara5...@oco.net wrote: On Mon, 21 Mar 2011 23:06:12 -0700, Joe Neeman joenee...@gmail.com wrote: Unfortunately, if I protect the assignment to the property with an if (!pure), I am letting the page-breaking planning rely on the

midi2ly error

2011-03-22 Thread Martin Tarenskeen
On Mon, 14 Mar 2011, Jan Nieuwenhuizen wrote: Martin Tarenskeen schreef op ma 14-03-2011 om 13:10 [+0100]: Which reminds me: midi2ly still needs a lot of work. In short: it is quite useless. Have a look at the latest version. It's starting to work. Great, it is already much better! I

Re: \repeat percent does not use the beat-slash stencil

2011-03-22 Thread Colin Campbell
On 11-03-22 01:09 AM, Ed Gordijn wrote: Hi Collin, Ok! That is clear! Do you know if it is possible to override the stencil? I try to do that but didn't succeed. Or should I post this question to the list? Thank you, by the way, for this wonderfull support! Greetings, Ed Thanks for the

Question about Windows LP Code and Ghostscript

2011-03-22 Thread James Lowe
Hello, Sorry if this is a basic question, but I have found an issue with Windows 7 and the latest SP1 that causes GS errors during LP compilation A bug has been added to the tracker - actually it was closed as I was not able to reproduce this on a clean system but have subsequently found

Re: Adds automatic numbering to footnotes. (issue4244064)

2011-03-22 Thread bordage . bertrand
Of course, I agree that we should get rid of the two-pass algorithm. But it's really tricky to do it the clean way :o\ As the issues I pointed out need deep changes, I think the two-pass algorithm is better than nothing. For the moment, we can also avoid these issues by displaying footnotes

Re: Question about Windows LP Code and Ghostscript

2011-03-22 Thread Phil Holmes
Top posting - apologies - the penalty of 2 windows users. James - I'm almost certain Ghostscript is completely standalone. In the days when Lily left the .ps files in the directory by default, I wrote a program that I associated with .ps and which called Ghostscript - I found it handy when

Re: Removing parser DIGIT (was: PATCH - DOC: Added @knownissue to NR for fingering

2011-03-22 Thread David Kastrup
Graham Percival gra...@percival-music.ca writes: On Sat, Mar 12, 2011 at 12:48:21PM +0100, David Kastrup wrote: Perhaps i'll aim for obliterating DIGIT altogether. I certainly can't think of any case in which we actually need/want a DIGIT. I see that DIGIT was added in release/0.1.49, back

Re: midi2ly error

2011-03-22 Thread Jan Nieuwenhuizen
Martin Tarenskeen schreef op di 22-03-2011 om 08:47 [+0100]: But please try the attached example (testmidi.mid). Nice bug. Fixed in HEAD. Thanks, Jan -- Jan Nieuwenhuizen jann...@gnu.org | GNU LilyPond http://lilypond.org Freelance IT http://JoyofSource.com | Avatar®

Lilypond-book and recursive processing of input and include

2011-03-22 Thread Julien Rioux
Dear list, It seems there is some inconsistency in how lilypond-book processes a master tex file with inputed and included tex files. First I would like to get a clear idea of the current behavior and it's intended use case. So, this is what I found. Upon a call to lilypond-book

Re: Removing parser DIGIT (was: PATCH - DOC: Added @knownissue to NR for fingering

2011-03-22 Thread Carl Sorensen
On 3/22/11 11:20 AM, David Kastrup d...@gnu.org wrote: Graham Percival gra...@percival-music.ca writes: On Sat, Mar 12, 2011 at 12:48:21PM +0100, David Kastrup wrote: Perhaps i'll aim for obliterating DIGIT altogether. I certainly can't think of any case in which we actually need/want a

Re: Removing parser DIGIT (was: PATCH - DOC: Added @knownissue to NR for fingering

2011-03-22 Thread Neil Puttock
On 22 March 2011 17:20, David Kastrup d...@gnu.org wrote: This. URL:http://codereview.appspot.com/4311041 Please improve/discuss.  This looks totally insane but does not actually change the existing absurd realities for single-digit unsigned numbers. I'm afraid I can't even get as far as

Re: \repeat percent does not use the beat-slash stencil

2011-03-22 Thread Neil Puttock
On 22 March 2011 12:59, Colin Campbell c...@shaw.ca wrote: @dev: Ed's question comes from the recent changes to percent repeats and beat slashes: is it possible to revert the double slash now used for short (1/8) notes and mixed note patterns, to a single slash as used prior to 2.13.51? Yes:

Fix 1569: Bad behavior of NoteNames context (issue4312043)

2011-03-22 Thread Carl . D . Sorensen
Reviewers: , Message: Here's a proposed patch for Issue 1569. Please review. Thanks, Carl Description: Fix 1569: Bad behavior of NoteNames context Changed default value of 'staff-affinity to #UP Changed default spacing parameters to be the same as for Lyrics context Added some

Re: Fixes accidental suggestions in the beam collision engraver (issue4271054)

2011-03-22 Thread Neil Puttock
On 21 March 2011 01:59, Han-Wen Nienhuys hanw...@gmail.com wrote: The intention of the fix is incorrect, but can you make the logic explicit? That is, add an interface symbol for normal accidentals (normal-accidental-interface, inline-accidental-interface, ... ?) and acknowledge that

Re: Fixes accidental suggestions in the beam collision engraver (issue4271054)

2011-03-22 Thread m...@apollinemike.com
On Mar 22, 2011, at 6:46 PM, Neil Puttock wrote: On 21 March 2011 01:59, Han-Wen Nienhuys hanw...@gmail.com wrote: The intention of the fix is incorrect, but can you make the logic explicit? That is, add an interface symbol for normal accidentals (normal-accidental-interface,

Re: Fixes accidental suggestions in the beam collision engraver (issue4271054)

2011-03-22 Thread Neil Puttock
On 22 March 2011 22:48, m...@apollinemike.com m...@apollinemike.com wrote: Would an acceptable alternative be giving the TrillPitchAccidental the inline-accidental-interface? Sounds good to me. Cheers, Neil ___ lilypond-devel mailing list

Re: Removing parser DIGIT (was: PATCH - DOC: Added @knownissue to NR for fingering

2011-03-22 Thread David Kastrup
Neil Puttock n.putt...@gmail.com writes: On 22 March 2011 17:20, David Kastrup d...@gnu.org wrote: This. URL:http://codereview.appspot.com/4311041 Please improve/discuss.  This looks totally insane but does not actually change the existing absurd realities for single-digit unsigned

Re: Gets the beam collision engraver to handle autobeams (issue4287061)

2011-03-22 Thread n . puttock
On 2011/03/20 12:00:34, MikeSol wrote: This is now fully functional. The only issue is that, for auto-beams, I don't have a good method yet for keeping note-heads that are part of the beam out of the covered grobs list. This is doable, though - I just have to think of the cleanest way.

Re: Adds automatic numbering to footnotes. (issue4244064)

2011-03-22 Thread Neil Puttock
On 10 March 2011 10:06, m...@apollinemike.com m...@apollinemike.com wrote: On Mar 9, 2011, at 10:17 PM, n.putt...@gmail.com wrote: Does `annotation-whiteout' do anything special?  If not, the existing property `whiteout' should suffice. It puts a whiteout only around the annotation instead

Allows glissandi to be continuous at line breaks (issue4273098)

2011-03-22 Thread mtsolo
Reviewers: , Message: I'm using this is in a piece I'm working on and figured it may be useful in LilyPond. Let me know what you think! Description: Allows glissandi to be continuous at line breaks Please review this at http://codereview.appspot.com/4273098/ Affected files: M

Re: Fixes accidental suggestions in the beam collision engraver (issue4271054)

2011-03-22 Thread Han-Wen Nienhuys
On Tue, Mar 22, 2011 at 7:54 PM, Neil Puttock n.putt...@gmail.com wrote: On 22 March 2011 22:48, m...@apollinemike.com m...@apollinemike.com wrote: Would an acceptable alternative be giving the TrillPitchAccidental the inline-accidental-interface? Sounds good to me. Sorry - I was confused.