Re: Issue 1796 in lilypond: LilyPond segfaults on make-footer = ##f
Comment #2 on issue 1796 by mts...@gmail.com: LilyPond segfaults on make-footer = ##f http://code.google.com/p/lilypond/issues/detail?id=1796 Fix pushed as 435b36a3e6576cebf794d815ae7cc78b652180f9. Cheers, MS ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1799 in lilypond: output-distance.py does not parse scheme nan values correctly
Comment #4 on issue 1799 by mts...@gmail.com: output-distance.py does not parse scheme nan values correctly http://code.google.com/p/lilypond/issues/detail?id=1799 Fix pushed as 7cd9444ea5dfc80782befa6b64bae015bddbd967. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: oi er e, tr5
2011/8/9 pedro pedro_sous...@hotmail.com: oi, sog gren pjf oej wjpoej fjdkof j skdjf rhfw eoigt w4etg eht er I can not reproduce that in my machine. -- Francisco Vila. Badajoz (Spain) www.paconet.org , www.csmbadajoz.com ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.15.8 change in \cueDuring behavior?
Paul Scott wrote Monday, August 08, 2011 2:47 AM On Sun, Aug 07, 2011 at 10:28:33PM +0200, Reinhold Kainhofer wrote: Am Sunday, 7. August 2011, 22:18:04 schrieb Paul Scott: Hi, This is the first time I have used \cueDuring in 2.15.x. In the following example the note size doesn't return to normal after the cue and the rests during the cue appear to be cue sized. My example seems to match the documentation. Did I miss something? if a voice starts with cue notes you have to create the voice explicitly; That sounds familiar. Should that be considered a minor bug? Yes. There are many situations where contexts must be created explicitly to avoid incorrect behaviour. When this is not obvious they should be noted as Warnings in the Notation Reference. In the case of \cueDuring the warning is given, but only as normal text at the bottom of the first example of \cueDuring. I think this should be elevated to a Warning. Trevor - No virus found in this message. Checked by AVG - www.avg.com Version: 10.0.1392 / Virus Database: 1520/3822 - Release Date: 08/08/11 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1776 in lilypond: Doc: NR - Polymetric Notation \compoundMeter isn't documented
Comment #22 on issue 1776 by pkx1...@gmail.com: Doc: NR - Polymetric Notation \compoundMeter isn't documented http://code.google.com/p/lilypond/issues/detail?id=1776 Francisco, Could you look at http://codereview.appspot.com/4837050 when you have a few moments (just in case you missed the comment there) as I am removing a snippet references from the translated *.tely files in this patch. James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: oi er e, tr5
Werner LEMBERG w...@gnu.org writes: oi, sog gren pjf oej wjpoej fjdkof j skdjf rhfw eoigt w4etg eht er I can not reproduce that in my machine. I can: oi, sog gren pjf oej wjpoej fjdkof j skdjf rhfw eoigt w4etg eht er Actually, the original did not contain any protected space. Likely Francisco's newsreader introduced it before fjdkof, so that may explain why you see different results. -- David Kastrup ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: 2.15.8 change in \cueDuring behavior?
On 11-08-09 02:59 AM, Trevor Daniels wrote: Paul Scott wrote Monday, August 08, 2011 2:47 AM On Sun, Aug 07, 2011 at 10:28:33PM +0200, Reinhold Kainhofer wrote: Am Sunday, 7. August 2011, 22:18:04 schrieb Paul Scott: Hi, This is the first time I have used \cueDuring in 2.15.x. In the following example the note size doesn't return to normal after the cue and the rests during the cue appear to be cue sized. My example seems to match the documentation. Did I miss something? if a voice starts with cue notes you have to create the voice explicitly; That sounds familiar. Should that be considered a minor bug? Yes. There are many situations where contexts must be created explicitly to avoid incorrect behaviour. When this is not obvious they should be noted as Warnings in the Notation Reference. In the case of \cueDuring the warning is given, but only as normal text at the bottom of the first example of \cueDuring. I think this should be elevated to a Warning. Trevor Thanks for the above, added as issue 1811 http://code.google.com/p/lilypond/issues/detail?id=1811 and I'll see if I can have a look at it later today. Cheers, Colin Campbell Bug Squad -- The human race has one really effective weapon, and that is laughter. -- Mark Twain ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Issue 1811 in lilypond: Revise warning re cueDuring font size
Status: Accepted
Owner:
Labels: Type-Documentation Priority-High
New issue 1811 by colinpkc...@gmail.com: Revise warning re cueDuring font
size
http://code.google.com/p/lilypond/issues/detail?id=1811
Reported by Paul Scott:
This is the first time I have used \cueDuring in 2.15.x.
In the following example the note size doesn't return to normal after
the cue and the rests during the cue appear to be cue sized.
\version 2.15.8
notesA = \relative c'' { a4 b c d e f g f e d c b }
\addQuote partA \notesA
notesB = \relative c'' { \cueDuring partA #UP { R1*2 } a4 b c d }
\score{
\new StaffGroup
\new Staff \notesA
\new Staff \notesB
}
***
Comment by Trevor:
There are many situations where contexts must
be created explicitly to avoid incorrect behaviour.
When this is not obvious they should be noted as
Warnings in the Notation Reference. In the case of
\cueDuring the warning is given, but only as normal
text at the bottom of the first example of \cueDuring.
I think this should be elevated to a Warning.
___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Comment #18 on issue 1691 by philehol...@googlemail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 OK. The value is defined in book_snippets.py in the following way: self.option_dict[LINE_WIDTH] = #(- paper-width \ left-margin-default right-margin-default) I haven't a clue what this does - paper-width, for example isn't mentioned in this file. However, if I output the value for self.option_dict[LINE_WIDTH] after this line, I get 160\mm. The easiest way to fix this would therefore be to change the line above to self.option_dict[LINE_WIDTH] = '155\\mm' This is the way INDENT is defined: self.option_dict[INDENT] = '0\\mm' and it would save lots of messing about. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Comment #20 on issue 1691 by percival.music.ca: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 The line you found was not the main one. To understand that line, please read the scheme tutorial in the documentation. Keep looking for a different line in that python/ directory. (hint: it uses \\in for inches, instead of cm or mm) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1691 in lilypond: Ugly bars in PDF documents
Updates: Owner: --- Comment #21 on issue 1691 by pkx1...@gmail.com: Ugly bars in PDF documents http://code.google.com/p/lilypond/issues/detail?id=1691 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1799 in lilypond: output-distance.py does not parse scheme nan values correctly
Updates: Status: Fixed Labels: fixed_2_15_8 Comment #5 on issue 1799 by percival.music.ca: output-distance.py does not parse scheme nan values correctly http://code.google.com/p/lilypond/issues/detail?id=1799 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1720 in lilypond: Incorrect tuplet bracket direction calculation when tuplets contain rests.
Updates: Status: Fixed Labels: -Patch-needs_work fixed_2_15_7 Comment #5 on issue 1720 by n.putt...@gmail.com: Incorrect tuplet bracket direction calculation when tuplets contain rests. http://code.google.com/p/lilypond/issues/detail?id=1720 eed6f105c0b478572ec2b8fa93e1f96c0c5869ba ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1799 in lilypond: output-distance.py does not parse scheme nan values correctly
Updates: Labels: -Patch-review -fixed_2_15_8 fixed_2_15_9 Comment #6 on issue 1799 by n.putt...@gmail.com: output-distance.py does not parse scheme nan values correctly http://code.google.com/p/lilypond/issues/detail?id=1799 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1811 in lilypond: Revise warning re cueDuring font size
Updates: Owner: pkx1...@gmail.com Comment #2 on issue 1811 by pkx1...@gmail.com: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1811 in lilypond: Revise warning re cueDuring font size
Updates: Labels: Patch-review Comment #1 on issue 1811 by pkx1...@gmail.com: Revise warning re cueDuring font size http://code.google.com/p/lilypond/issues/detail?id=1811 http://codereview.appspot.com/4850051 James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1793 in lilypond: Doc: change how lyrics in PianoStaff is documented
Comment #3 on issue 1793 by tdaniels...@googlemail.com: Doc: change how lyrics in PianoStaff is documented http://code.google.com/p/lilypond/issues/detail?id=1793 Many things in Chapter 5 of the NR need a complete rewrite. Context layout order is one of them. We need to combine 5.4.3 into 5.1.7 and rewrite 5.1.7 accordingly to cover the default layout order and the use of alignAboveContext, alignBelowContext. Use an ossia staff and/or lyrics for alignAboveContext and alignBelow Context. The use of \accepts and \denies is now required only when creating new contexts, so any explanation of them should go into 5.1.6. Actually there's probably enough already about them in 5.1.6, so pretty well all of the existing 5.1.7 could just be deleted. Trevor ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 804 in lilypond: Code cleaning: checking types-conversion issues and other build warnings
Updates: Labels: -Patch Patch-new Comment #5 on issue 804 by percival.music.ca: Code cleaning: checking types-conversion issues and other build warnings http://code.google.com/p/lilypond/issues/detail?id=804 The previous patch does not apply cleanly to master. Fortunately, Reinhold has started a new effort to clear up build warnings: http://codereview.appspot.com/4854049 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
