Re: Issue 2215 in lilypond: lost commits jan 7
Comment #2 on issue 2215 by gra...@percival-music.ca: lost commits jan 7 http://code.google.com/p/lilypond/issues/detail?id=2215 try it without a dash in jan7 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2215 in lilypond: lost commits jan 7
Comment #3 on issue 2215 by gra...@percival-music.ca: lost commits jan 7 http://code.google.com/p/lilypond/issues/detail?id=2215 no wait, I can't find those commits in webgit either. Hmm. *shrug* ok, the commits are even more lost than I thought. Somebody needs to figure out if anything's lost at all, track them down if they _are_ lost, and then resubmit them. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1846 in lilypond: Improves horizontal spacing of axis groups that SpanBar grobs traverse
Updates: Labels: Patch-review Comment #19 on issue 1846 by lilypond...@gmail.com: Improves horizontal spacing of axis groups that SpanBar grobs traverse http://code.google.com/p/lilypond/issues/detail?id=1846#c19 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2221 in lilypond: Duplicate node errors in snippets
Updates: Labels: Patch-review Comment #3 on issue 2221 by lilypond...@gmail.com: Duplicate node errors in snippets http://code.google.com/p/lilypond/issues/detail?id=2221#c3 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi
Updates: Labels: Patch-review Comment #1 on issue 2218 by lilypond...@gmail.com: Web: Added Concert to Introduction.itexi http://code.google.com/p/lilypond/issues/detail?id=2218#c1 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2180 in lilypond: beams are detached from stems
Updates: Labels: Patch-review Comment #9 on issue 2180 by lilypond...@gmail.com: beams are detached from stems http://code.google.com/p/lilypond/issues/detail?id=2180#c9 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2220 in lilypond: Undefined references to node in translated manuals
Updates: Labels: Patch-review Comment #3 on issue 2220 by lilypond...@gmail.com: Undefined references to node in translated manuals http://code.google.com/p/lilypond/issues/detail?id=2220#c3 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2200 in lilypond: Dots shouldn't always be placed in one column
Updates: Labels: Patch-review Comment #2 on issue 2200 by lilypond...@gmail.com: Dots shouldn't always be placed in one column http://code.google.com/p/lilypond/issues/detail?id=2200#c2 Patchy the autobot says: LGTM. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: internal LilyPond functions instead of -d options
Ralph Palmer-3 wrote: On Mon, Jan 9, 2012 at 10:54 AM, -Eluze elu...@gmail.com wrote: hi everybody knows how cumbersome it is to write parameters in a shell - it would be nice to have them in a lilypond file. LilyPond provides an alternative for many of the command line options but they are not well documented in an appropriate context. here is a list of the approx 50 command line options provided by LilyPond (with -dhelp or #(ly:option-usage)) with their counterparts in LilyPond. http://old.nabble.com/file/p33107771/doptions%2Bdefine%2Bdefault.csv doptions+define+default.csv most of them work as expected (I only checked about half of the items under Windows 7) with a few exceptions: show-available-fonts --- #(ly:font-config-display-fonts) help --- #(ly:option-usage) read-file-list (get error messages; how is it supposed to be used?) verbose --- #(ly:set-option 'verbose #t) -- no result my suggestion is to add the internal functions to the Application Usage manual. I'm not sure I understand what Eluze is asking - include the internal functions directly into LilyPond, that would be great (2nd step) document their current presence in LilyPond in the Application Usage manual, maybe as a first step! or something else (a combination?). definitely! I'll think about a possibility (next week) Eluze -- View this message in context: http://old.nabble.com/internal-LilyPond-functions-instead-of--d-options-tp33107771p33132825.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
Re: Issue 2092 in lilypond: lily-git.tcl should using a working branch
Updates: Labels: Patch-needs_work Comment #15 on issue 2092 by lilypond...@gmail.com: lily-git.tcl should using a working branch http://code.google.com/p/lilypond/issues/detail?id=2092#c15 Patchy the autobot says: sorry, I'm getting patch does not apply. Tested it twice. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2218 in lilypond: Web: Added Concert to Introduction.itexi
Updates: Status: Fixed Labels: -Patch-review Comment #2 on issue 2218 by pkx1...@gmail.com: Web: Added Concert to Introduction.itexi http://code.google.com/p/lilypond/issues/detail?id=2218 Fri, 13 Jan 2012 11:42:01 + (11:42 +) commit b6731e900a2037112364ad328b8e3b2f7bcd1eb0 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2198 in lilypond: Document use of PATH statement in Windows
Updates: Status: Fixed Labels: -Patch-push Comment #7 on issue 2198 by pkx1...@gmail.com: Document use of PATH statement in Windows http://code.google.com/p/lilypond/issues/detail?id=2198 Fri, 13 Jan 2012 11:48:16 + (11:48 +) commit 1465bed7792a2e2c83dc6643b811183b76db5497 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2191 in lilypond: Web: update to version 2.15, use it in the site: part
Updates: Status: Fixed Labels: -Patch-push Comment #8 on issue 2191 by pkx1...@gmail.com: Web: update to version 2.15, use it in the site: part http://code.google.com/p/lilypond/issues/detail?id=2191 committer James Lowe pkx1...@gmail.com Fri, 13 Jan 2012 11:54:08 + (11:54 +) commit 427bb2b004227f3afc7de10dfd896fc375cbc320 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2092 in lilypond: lily-git.tcl should using a working branch
Updates: Labels: Patch-new Comment #16 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should using a working branch http://code.google.com/p/lilypond/issues/detail?id=2092#c16 Update lilygit.tcl (Issue 2092) Makes lilygit.tcl respect the environment variable $LILYPOND_GIT. If $LILYPOND_GIT is unset, default of $HOME/lilypond-git will be used. Also does all working on dev/local_working branch, instead of master Adds a Push Patch button to push patch to staging. http://codereview.appspot.com/5504092 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2092 in lilypond: lily-git.tcl should using a working branch
Comment #17 on issue 2092 by carl.d.s...@gmail.com: lily-git.tcl should using a working branch http://code.google.com/p/lilypond/issues/detail?id=2092 I'm sorry. I forgot to rebase to staging. Should be good to go now. Carl ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2198 in lilypond: Document use of PATH statement in Windows
Comment #8 on issue 2198 by mats.ben...@ee.kth.se: Document use of PATH statement in Windows http://code.google.com/p/lilypond/issues/detail?id=2198 How about the other command-line utilities like convert-ly? Have you added similar comments in the documentation of these? /Mats ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer.
Comment #8 on issue 2177 by m...@apollinemike.com: Patch: Reverts public interface for simple spacer. http://code.google.com/p/lilypond/issues/detail?id=2177 Could you please check this patch again w/ the new patchy to see if it gets over the column-description.hh hurdle? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2198 in lilypond: Document use of PATH statement in Windows
Comment #9 on issue 2198 by pkx1...@gmail.com: Document use of PATH statement in Windows http://code.google.com/p/lilypond/issues/detail?id=2198 No but you (or anyone else) can add a new tracker issue if you like so this can be done the 'next time'. This specific request/issue is fixed. Put in where you think the link should go (use the URL from the online doc) or similar so it makes it easier for me/doc editors to find. James ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2221 in lilypond: Duplicate node errors in snippets
Updates: Status: Fixed Labels: -Patch-review Fixed_2_15_25 Comment #4 on issue 2221 by julien.r...@gmail.com: Duplicate node errors in snippets http://code.google.com/p/lilypond/issues/detail?id=2221 Pushed as e25565e23b6e7a219c594d359495817d7076eff5 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2220 in lilypond: Undefined references to node in translated manuals
Updates: Labels: -Patch-review Comment #4 on issue 2220 by julien.r...@gmail.com: Undefined references to node in translated manuals http://code.google.com/p/lilypond/issues/detail?id=2220 Pushed to lilypond/translation to merge with Francisco's other xref fixes. Head is now 4a66b6980034a8870121fb4dc40b00a4eaea9ac1 ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2158 in lilypond: Patch: Sketch of not remaking html files
Comment #10 on issue 2158 by julien.r...@gmail.com: Patch: Sketch of not remaking html files http://code.google.com/p/lilypond/issues/detail?id=2158 I'm not found of a try: block that discards the exception (I think that's what it currently does). ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2177 in lilypond: Patch: Reverts public interface for simple spacer.
Updates: Labels: -Patch-needs_work Patch-new Comment #9 on issue 2177 by gra...@percival-music.ca: Patch: Reverts public interface for simple spacer. http://code.google.com/p/lilypond/issues/detail?id=2177 err, ok. I guess this patch was waiting for 6 days just for somebody to change the tag? ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2125 in lilypond: Patch: Build: Don't rebuild everythingeach time unless necessary.
lilyp...@googlecode.com wrote in message news:11-9567054385019064696-16001340212203614722-lilypond=googlecode@googlecode.com... Updates: Labels: -Patch-review Patch-needs_work Comment #11 on issue 2125 by julien.r...@gmail.com: Patch: Build: Don't rebuild everything each time unless necessary. http://code.google.com/p/lilypond/issues/detail?id=2125 make[2]: Circular out-www/essay.texi - essay.tely dependency dropped. make[2]: Circular out-www/extending.texi - extending.tely dependency dropped. make[2]: Circular out-www/learning.texi - learning.tely dependency dropped. make[2]: Circular out-www/music-glossary.texi - music-glossary.tely dependency dropped. make[2]: Circular out-www/notation.texi - notation.tely dependency dropped. make[2]: Circular out-www/snippets.texi - snippets.tely dependency dropped. make[2]: Circular out-www/usage.texi - usage.tely dependency dropped. etc. You want the patch build-checked? -- Phil Holmes Bug Squad ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Problem with convert-ly
Hello, When trying to use convert-ly I obtain $ convert-ly test.ly convert-ly (GNU LilyPond) 2.15.25 convert-ly: Procesando «test.ly»... Traceback (most recent call last): File /usr/local/bin/convert-ly, line 369, in module main () File /usr/local/bin/convert-ly, line 357, in main do_one_file (f) File /usr/local/bin/convert-ly, line 273, in do_one_file (last, result) = do_conversion (input, from_version, to_version) File /usr/local/bin/convert-ly, line 203, in do_conversion ly.progress (_ (Applying conversion: ), newline = False) TypeError: progress() got an unexpected keyword argument 'newline' The line in question is following git-blame 86c0609e scripts/convert-ly.py (Julien Rioux 2011-12-14 08:40:02 -0500 184) ly.progress (_ (Applying conversion: ), newline = False) It is latest git self-compiled lilypond as of today. -- 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: Problem with convert-ly
2012/1/13 Julien Rioux jri...@physics.utoronto.ca: I'm not sure why, but it looks like convert-ly.py and lilylib.py are out-of-sync. Could it be that python imports lilylib from a different version of lilypond? Could you please find the line identify () in convert-ly.py (line 346 here) and add below print lilylib imported from, ly.__file__ exit() Then run the script and see what you get? convert-ly (GNU LilyPond) 2.15.25 lilylib imported from /usr/local/share/lilypond/2.15.15/python/lilylib.pyc Yes it looks out of sync. I have edited usr/local/bin/convert-ly. Now what? Thanks, -- 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: Problem with convert-ly
2012/1/13 Francisco Vila paconet@gmail.com: 2012/1/13 Julien Rioux jri...@physics.utoronto.ca: I'm not sure why, but it looks like convert-ly.py and lilylib.py are out-of-sync. Could it be that python imports lilylib from a different version of lilypond? Could you please find the line identify () in convert-ly.py (line 346 here) and add below print lilylib imported from, ly.__file__ exit() Then run the script and see what you get? convert-ly (GNU LilyPond) 2.15.25 lilylib imported from /usr/local/share/lilypond/2.15.15/python/lilylib.pyc Yes it looks out of sync. I have edited usr/local/bin/convert-ly. Now what? Solved. I killed and recompiled the python/ directory and reinstalled, all goes well now. Thanks! -- 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: Issue 695 in lilypond: slurs may take too much vertical extent
Comment #19 on issue 695 by janek.li...@gmail.com: slurs may take too much vertical extent http://code.google.com/p/lilypond/issues/detail?id=695 I think this will impact the way users use Lily, perhaps quite strongly (thanks, Mike!). However i don't insist on mentioning this in changes. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 1412 in lilypond: programming error: Going back in MIDI time
Comment #3 on issue 1412 by plros...@gmail.com: programming error: Going back in MIDI time http://code.google.com/p/lilypond/issues/detail?id=1412 The same happens with \appoggiatura. It looks like Lilypond tries to borrow time from the previous note, but there is none. It may be OK for standalone grace notes, but it's definitely wrong for acciaccaturas and appoggiaturas. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2153 in lilypond: piano pedal bracket should stop at requested moment
Updates: Status: Verified Comment #8 on issue 2153 by ma...@gregoriana.sk: piano pedal bracket should stop at requested moment http://code.google.com/p/lilypond/issues/detail?id=2153 (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 2123 in lilypond: Patch: Gets cross-staff collisions right for beams.
Updates: Status: Verified Comment #7 on issue 2123 by ma...@gregoriana.sk: Patch: Gets cross-staff collisions right for beams. http://code.google.com/p/lilypond/issues/detail?id=2123 (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 2059 in lilypond: Bar numbering of alternatives
Updates: Status: Verified Comment #20 on issue 2059 by ma...@gregoriana.sk: Bar numbering of alternatives http://code.google.com/p/lilypond/issues/detail?id=2059 (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 1947 in lilypond: Stem Tremoli for double-stemmed notes are too short on the right side.
Updates: Status: Verified Comment #7 on issue 1947 by ma...@gregoriana.sk: Stem Tremoli for double-stemmed notes are too short on the right side. http://code.google.com/p/lilypond/issues/detail?id=1947 (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 2122 in lilypond: Regression in chord-name-exceptions.ly - badly spaced chord names
Comment #9 on issue 2122 by ma...@gregoriana.sk: Regression in chord-name-exceptions.ly - badly spaced chord names http://code.google.com/p/lilypond/issues/detail?id=2122 Running chord-name-exceptions.ly with 2.15.24 gives the same layout as on the picture right. ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
Re: Issue 2084 in lilypond: script-accidental avoidance fails for articulations
Updates: Status: Verified Comment #11 on issue 2084 by ma...@gregoriana.sk: script-accidental avoidance fails for articulations http://code.google.com/p/lilypond/issues/detail?id=2084 (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 2215 in lilypond: lost commits jan 7
Updates: Status: Started Owner: carl.d.s...@gmail.com Comment #5 on issue 2215 by carl.d.s...@gmail.com: lost commits jan 7 http://code.google.com/p/lilypond/issues/detail?id=2215 (No comment was entered for this change.) ___ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
