Re: How to 'unstuff' lilypond-2.12.0-1.darwin-ppc.tar.bz2

2008-12-30 Thread Graham Percival
bunzip2 file.bz2 or tar -xjf file.bz2 I'm surprised that you can't open it by double-clicking; 10.4 does this without any fuss. Cheers, - Graham On Wed, Dec 31, 2008 at 01:02:46AM +, Vic Saravia wrote: > Hi There, > > The concept of being able to > once again put music on my computer b

How to 'unstuff' lilypond-2.12.0-1.darwin-ppc.tar.bz2

2008-12-30 Thread Vic Saravia
Hi There, The concept of being able to once again put music on my computer beckons. I used to use Passport on my PC to do this, but now am using a Mac. Clicking on the .bz2 file produces no result, [I'm using OS X 10.3.9 on a G4 Titanium Mac] How can one open this file? Appreciate any guidan

Issue 391 in lilypond: using relative filepath in \include "foo.ly"

2008-12-30 Thread codesite-noreply
Comment #10 on issue 391 by v.villenave: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 Does that imply that we would also have the corresponding ly:set-option? If so, I happily vote for it :-) -- You received this message because you a

Re: Strange parsing of define output-suffix "AA"

2008-12-30 Thread Reinhold Kainhofer
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Am Dienstag, 30. Dezember 2008 11:41:13 schrieb Villum Sejersen: > lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too > > The other day I tried to spare myself some post-file-renaming, (in the > \global section in a rather simple 5-voice

Issue 391 in lilypond: using relative filepath in \include "foo.ly"

2008-12-30 Thread codesite-noreply
Comment #9 on issue 391 by joeneeman: using relative filepath in \include "foo.ly" http://code.google.com/p/lilypond/issues/detail?id=391 I'm not keen on having two different \include commands with subtly different behaviour, especially if one of them is only around for historical reasons.

Strange parsing of define output-suffix "AA"

2008-12-30 Thread Villum Sejersen
lilypond 2.12.0-1 - 2.11.65-1 and most likely older versions too The other day I tried to spare myself some post-file-renaming, (in the \global section in a rather simple 5-voice choral score) using: #(define output-suffix "SAATB_d-major") To my surprise the resulting filename