Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding
Comment #5 on issue 1855 by reinhold...@gmail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 Sorry, what am I missing? There are two measures added to the beginning, but the last two measures exactly match the previous version, sans the collision... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
Comment #5 on issue 1858 by percival.music.ca: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 out/bin/lilypond -ddump-profile ../input/regression/lyric-tie.ly more ../input/regression/lyric-tie.profile Git master gives me weird amounts: cells: 2258113 cells: 4877296 cells: 4877296 cells: 4877296 release/2.15.9-1 gives me: cells: 2257347 cells: 2257347 cells: 2257347 Unfortunately I've got caught up in other stuff, so I couldn't complete the git bisect before I had to go. But there's definitely a change between release/2.15.9-1 and master! ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1855 in lilypond: Prevents nested tuplets from colliding
Updates: Labels: -Patch-needs_work Patch-review Comment #6 on issue 1855 by tdaniels...@googlemail.com: Prevents nested tuplets from colliding http://code.google.com/p/lilypond/issues/detail?id=1855 You're right, Reinhold. Perhaps I hadn't quite woken up earlier :) LGTM now. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1595 in lilypond: lilypond-book papersize gives margin warnings
Comment #4 on issue 1595 by reinhold...@gmail.com: lilypond-book papersize gives margin warnings http://code.google.com/p/lilypond/issues/detail?id=1595 Using paper size does not solve the problem, AFAICS. We are currently obtaining the correct line width from latex/texinfo, and lilypond-book sets this width accordingly and passes it to lilypond. There are just a few problems: 1) If you give lilypond a line-width of, say, 154mm, the created image WILL be larger (the line-width is 154mm, but there is a bar line on the right, which can't be cut in the middle, so the image is cropped after the barline, adding some space). 2) The other problem is how lilypond handles line-width, paper-size and the margins. There is no way to increase the left/right margin for quote by a given amount. Rather, one has to give the new margins or line-width in absolute values. Now, the problem is that in lilypond-book, we only have the auto-detected line-width and nothing else. if paper-size is given, we don't really have the paper-width, the margins or the line-width (short of hardcoding most paper-sizes and margins in lilypond-book, too). Now, with quote we need to increase the left margin by 0.4in... The #(set-paper-size...) clears the line-width variable, so we cannot adjust an existing line-width, but if we are using auto-detected variables, we only have line-width available to adjust. In other words, the handling of the quote options needs to be different, depending on whether papersize was given or not. Lilypond-book's structure, on the other hand, is designed so that each option can more or less be handled independently from the others... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1825 in lilypond: convert-ly produces no output having run on up-to-date source
Updates: Status: Fixed Labels: fixed_2_15_10 Comment #6 on issue 1825 by reinhold...@gmail.com: convert-ly produces no output having run on up-to-date source http://code.google.com/p/lilypond/issues/detail?id=1825 Pushed as 45a78dfa12df96f7271de565c3d9ad8da7ccc065 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1293 in lilypond: lilypond-book should use "quote" environment of LaTeX (instead of "quotation")
Updates: Status: Fixed Labels: fixed_2_15_10 Comment #4 on issue 1293 by reinhold...@gmail.com: lilypond-book should use "quote" environment of LaTeX (instead of "quotation") http://code.google.com/p/lilypond/issues/detail?id=1293 Pushed as 464b5926b0ed7165c89a5e3ecb79c5a22d3051f7 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1638 in lilypond: lilypond-book [quote] hard-codes 5\in
Comment #6 on issue 1638 by reinhold...@gmail.com: lilypond-book [quote] hard-codes 5\in http://code.google.com/p/lilypond/issues/detail?id=1638 See also my comment to bug 1595 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings
Updates: Labels: -Patch-needs_work Patch-new Comment #4 on issue 1805 by reinhold...@gmail.com: Ambitus engraver produces false warnings http://code.google.com/p/lilypond/issues/detail?id=1805 New patch is up at http://codereview.appspot.com/4904049/, which now uses Neil's approach of the slurs only listening to inline-accidentals... ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1595 in lilypond: lilypond-book papersize gives margin warnings
Comment #5 on issue 1595 by percival.music.ca: lilypond-book papersize gives margin warnings http://code.google.com/p/lilypond/issues/detail?id=1595 I still think an *internal* (see later definition) paper size would work. Steps: 1. latex tells lilypond-book how much horizontal space it can use. 2. lilypond-book does subtractions for quote and related options. 3. lilypond-book tells lilypond how much horizontal space it can use. 4. lilypond creates an image that corresponds to that horizontal space. The problem is that at the moment step 3 is done in terms of line-width, but line-width does not include the instrument name (and other non-staff horizontal width). I think that if lilypond-book told lilypond that the paper width was something like 150mm (not hard-coded; I'm just guesstimating what would be left on an a4 paper, after latex margins and lilypond-book margins like quote), then lilypond would / should be able to figure out that if it has an instrument name that's 25mm long and needs 5mm padding, then the staff line width should be 120mm. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
Comment #6 on issue 1858 by percival.music.ca: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 oops, that was looking at (apparently) the wrong problem; this specific issue was about a memory thing between 2.15.8 and 2.15.9. Git bisect points at this one. seems a bit weird, but that's what I found... (?) 2a42ed162649920caf54eaee1f41563ecfe3b4e2 is the first bad commit commit 2a42ed162649920caf54eaee1f41563ecfe3b4e2 Author: Reinhold Kainhofer Date: Thu Aug 4 16:11:00 2011 +0200 GUILE debug: Revert part of 52bea08ef73a55ee, so the file of an error is shown ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
Comment #7 on issue 1858 by reinhold...@gmail.com: unexplained increase in profile reports http://code.google.com/p/lilypond/issues/detail?id=1858 That commit turned on debugging in guile again... So the question now is, what was the case before Ian turned debugging off in february with commit 52bea08ef73a55ee? Was the cell count back then just as high as it is now, or did something else change meanwhile? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04
Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04 using apt-get. No apparent errors in install but on attempt to run $ lilypond GNU LilyPond 2.12.3 warning: not relocating, no 2.12.3/ or current/ found under /home/mark/share/lilypond/ ERROR: In procedure primitive-load-path: ERROR: Unable to find file "lily.scm" in load path ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken
On Fri 02 Sep 2011, 21:42 lilyp...@googlecode.com wrote: > Updates: > Status: Verified > > Comment #8 on issue 1295 by percival.music.ca: Support for Mac OSX > 10.3.9 "Panther" is broken > http://code.google.com/p/lilypond/issues/detail?id=1295 > > Every item in "issues to be verified" should be verified. Yes. However I was not so wrong this time .) For some reason "Invalid" issues need not to be verified, please compare: http://code.google.com/p/lilypond/issues/list?can=1&q=status%3Ainvalid http://code.google.com/p/lilypond/issues/list?can=7 I am not sure this is bad. What do you think? -- Dmytro O. Redchuk Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04
On Fri, Sep 02, 2011 at 12:18:32PM +1000, Mark Chapman wrote: > Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04 using apt-get. No > apparent errors in install but on attempt to run Report that to ubuntu. We're not responsible for their broken packages. Cheers, - Graham ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1858 in lilypond: unexplained increase in profile reports
On Sat, Sep 3, 2011 at 12:05 PM, wrote: > > Comment #7 on issue 1858 by reinhold...@gmail.com: unexplained increase in > profile reports > http://code.google.com/p/lilypond/issues/detail?id=1858 > > That commit turned on debugging in guile again... > > So the question now is, what was the case before Ian turned debugging off in > february with commit 52bea08ef73a55ee? Guile debugging store a lot more information about the Scheme source code, so it could easily explain increased memory usage. -- Han-Wen Nienhuys - han...@xs4all.nl - http://www.xs4all.nl/~hanwen ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1295 in lilypond: Support for Mac OSX 10.3.9 "Panther" is broken
Am Saturday 03 September 2011, 19:28:08 schrieb Dmytro O. Redchuk: > On Fri 02 Sep 2011, 21:42 lilyp...@googlecode.com wrote: > > Updates: > > Status: Verified > > > > Comment #8 on issue 1295 by percival.music.ca: Support for Mac OSX > > 10.3.9 "Panther" is broken > > http://code.google.com/p/lilypond/issues/detail?id=1295 > > > > Every item in "issues to be verified" should be verified. > > Yes. > > However I was not so wrong this time .) > > For some reason "Invalid" issues need not to be verified, please compare: http://code.google.com/p/support/issues/detail?id=2612 However, duplicate reports are still in the list to verify, which they shouldn't... Cheers, Reinhold -- -- Reinhold Kainhofer, Vienna University of Technology, Austria email: reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial and Actuarial Mathematics, TU Wien, http://www.fam.tuwien.ac.at/ * Edition Kainhofer Music Publishing, http://www.edition-kainhofer.com/ * LilyPond music typesetting software, http://www.lilypond.org/ signature.asc Description: This is a digitally signed message part. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1852 in lilypond: manuals needs more explicit dependencies
Comment #4 on issue 1852 by julien.r...@gmail.com: manuals needs more explicit dependencies http://code.google.com/p/lilypond/issues/detail?id=1852 Well, not a problem, 2.6 is not really needed so I removed that. In the meantime I also found another bug, namely that global_options.format was used as the file extension, which works by chance for texi and html output, but is otherwise completely wrong. Attachments: 1852-make-doc-dependencies-v2.patch 1.5 KB ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Explicit fingering direction (^3) has no effect if Fingering #'direction is set
If the Fingering grob has an explicit direction set, it is NOT possible to
override it with an explicit direction in the input:
\override Fingering #'direction = #DOWN
c'4-3 c'4^3 c'4_3 c'4-3 |
In this example, all fingerings will be below the staff, but the second one
should still be above, since ^ is explicitly given. Full example is attached.
The only way to override is with an explicit
\once\override Fingering #'direction = #UP
Cheers,
Reinhold
PS: For other grobs, like DynamicText or DynamicLineSpanner an explicit
direction (^ or _) overrides the Grob's direction.
--
--
Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/
* Financial & Actuarial Math., Vienna Univ. of Technology, Austria
* http://www.fam.tuwien.ac.at/, DVR: 0005886
* LilyPond, Music typesetting, http://www.lilypond.org
fingering-direction-override.pdf
Description: Adobe PDF document
\version "2.15.10"
\paper { line-width = 9\cm tagline =##f}
\markup\wordwrap { Fingering direction is set to DOWN, but explicit
directions should override. The given directions here are: default, UP, DOWN, default
}
\score{
\new Staff {
\override Fingering #'direction = #DOWN
c'4-3 c'4^3 c'4_3 c'4-3 |
}
}___
bug-lilypond mailing list
bug-lilypond@gnu.org
https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04
Hello, On Fri, Sep 2, 2011 at 3:18 AM, Mark Chapman wrote: > Install problem Lilypond 2.12.3 on Linux Ubuntu 11.04 using apt-get. No > apparent errors in install but on attempt to run > > $ lilypond > GNU LilyPond 2.12.3 > warning: not relocating, no 2.12.3/ or current/ found under > /home/mark/share/lilypond/ > ERROR: In procedure primitive-load-path: > ERROR: Unable to find file "lily.scm" in load path > ___ > bug-lilypond mailing list > bug-lilypond@gnu.org > https://lists.gnu.org/mailman/listinfo/bug-lilypond > Don't use apt-get to install LilyPond, the packaging for this is something that Ubuntu are responsible for and 2.12.3 is very old now. Download and install the most current 2.14.x from lilypond.org instead. You could report this to ubuntu and ask them to repackage the later version, but I have not had any feed back when I asked them to update their packages about 6 months ago. So I just use the binaries from lilypond.org. James -- -- James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1805 in lilypond: Ambitus engraver produces false warnings
Updates: Labels: -Patch-new Patch-review Comment #5 on issue 1805 by pkx1...@gmail.com: Ambitus engraver produces false warnings http://code.google.com/p/lilypond/issues/detail?id=1805 passes make and reg tests ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Explicit fingering direction (^3) has no effect if Fingering #'direction is set
Reinhold Kainhofer wrote: > > If the Fingering grob has an explicit direction set, it is NOT possible to > override it with an explicit direction in the input: > > \override Fingering #'direction = #DOWN > c'4-3 c'4^3 c'4_3 c'4-3 | > > In this example, all fingerings will be below the staff, but the second > one > should still be above, since ^ is explicitly given. Full example is > attached. > > The only way to override is with an explicit > \once\override Fingering #'direction = #UP > > Cheers, > Reinhold > > PS: For other grobs, like DynamicText or DynamicLineSpanner an explicit > direction (^ or _) overrides the Grob's direction. > > using \set fingeringOrientations = #'(…) to set directions you can override its behavior ad hoc (with _ or ^)! cheers Eluze -- View this message in context: http://old.nabble.com/Explicit-fingering-direction-%28%5E3%29-has-no-effect-if-Fingering--%27direction-is-set-tp32393852p32394705.html Sent from the Gnu - Lilypond - Bugs mailing list archive at Nabble.com. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
