Re: png output with transparent background

I think this is a bug in LilyPondTool, because it sends the whole "default arguments" list as one argument to lilypond. As a workaround you can try writing this to the Console window: %lilypond --png -dpixmap-format=pngalpha -dpreview %buffer Hi, When

Re: png output with transparent background

when I run it from jedit using lilypondtool I get an error in the lilypond console: "unrecognized option: foo" where foo is whatever I put as the default arguments in the lilypondtool plugin options. I'm putting the following in the textbox for "default arguments": --png -dpixma

CG lilybuntu link issue

Hi, the link to the LilyBuntu ISO (http://prodet.hu/bert/lilydev/lilybuntu.iso) is currently not working, due to a change in the server location. I think it should be better if it were instead on a subdomain in the lilypond.org domain. I'm happy to host it in the future as well, but I think w

Re: convert-ly can't cope with accented filename

See http://www.amk.ca/python/howto/unicode John Mandereau wrote: Le mardi 05 janvier 2010 à 08:03 +1100, Nick Payne a écrit : Try to run convert-ly on a file with an accented name and I get the following: > convert-ly --edit "/home/nick/lilypond/Bésard_preludio.ly" convert-ly (GNU LilyPon

Re: Incorrect point-and-click URIs of files with non-ASCII content on Windows

Patrick McCarty wrote: On 2009-11-02, Graham Percival wrote: On Mon, Nov 02, 2009 at 01:07:48AM -0800, Patrick McCarty wrote: The second case is much more likely. Graham, I don't want to bug you with this, but would you mind checking the log for mingw::lilypond to see if configure dete

Re: Incorrect point-and-click URIs of files with non-ASCII content on Windows

Patrick McCarty wrote: On 2009-11-01, Bertalan Fodor (LilyPondTool) wrote: 3) UTF-8 characters. In UTF-8 locales, terminals need to know about the byte offset, so I am using the character count to specify this offset. An example would be "3:11:10". The third case is arguably

Re: Incorrect point-and-click URIs of files with non-ASCII content on Windows

3) UTF-8 characters. In UTF-8 locales, terminals need to know about the byte offset, so I am using the character count to specify this offset. An example would be "3:11:10". The third case is arguably misleading, so maybe it should be changed to use the "3:10:10" instead. I am okay wit

Re: Rock guitar power chord symbol A5 B5 C5.. won't print via \chords { c1:5 }

Hi Albert, this is not a bug, but a bit underdocumented feature. If you had googled for it, you would have found the answer in http://www.nabble.com/Defining-new-chord-modifier-td24949997.html c:5^3 is the chord. To make it appear as C5, see http://thread.gmane.org/gmane.comp.gnu.lilypond.ge

Re: Rename \unHideNotes to \unhideNotes

The general rule in the CamelCaseWorld is to change the case on word boundaries. In this sense I also think that unhideNotes should be unhideNotes. Also for a user syntactic keywords and variables are indistinguishable. (And not just for users, as if I remember well \override is a music function

Re: tarball

7-zip extracts it for sure. Jon McNamara wrote: I've downloaded the document tarball for lilly pond twice - and Winzip reports an error each time Downloaded file is apparently called lilypond-2.12.2-1.documentation.tar.bz2.tar Any suggestions as to how to use this file would be appreciated Jo

scheme bug in property-init.ly

The following declarations are bad in property-init.ly: aikenHeads = \set shapeNoteStyles = ##(do re mi fa #f la ti) acredHarpHeads = \set shapeNoteStyles = ##(fa #f la fa #f la mi) The correct is: aikenHeads = \set shapeNoteStyles = #'#(do re mi fa #f la ti) sacredHarpHeads = \set shapeNoteSt