Re: \displayLilyMusic function

[James Lowe]

Thanks,

Then I guess if you run LilyPond at the CLI (on Windows anyway) with 
just this statement in the *.ly file you get

> C:\Users\jlowe\Desktop>lilypond test.ly
> GNU LilyPond 2.13.10
> Processing `test.ly'
> Parsing...
> { a, cis e fis g }
>
> Interpreting music...
> Preprocessing graphical objects...
> Solving 1 page-breaking chunks...[1: 1 pages]
> Drawing systems...
> Layout output to `test.ps'...
> Converting to `./test.pdf'...

If I run it as

C:\Users\jlowe\Desktop>lilypond test.ly >display.txt

Then I get a display.txt file with *just* the '{ a, cis e fis g }' 
stated (including the braces).

If this is the same for Linux then I could remove the 'what happens 
under windows' comment in the itely file (as a patch)

James


Graham Percival wrote:
> On Tue, Apr 6, 2010 at 12:16 PM, James Lowe <address@hidden> wrote:
> > >   By default, LilyPond will print these messages to the console along with
> > > all the other mes-
> > > sages. To split up these messages and save the results of \display{STUFF},
> > > redirect the output
> > > to a file.
> > > lilypond file.ly >display.txt
> > Now this all seems to work however I always get a PDF file created even if
> > the *.ly file contains
> >
> > \version "2.13.6"
> >
> > {
> >  \displayLilyMusic \transpose c a, { c4 e g a bes }
> > }
>
> This is correct.  If you look at the console (umm... this would depend
> on the way you run lilypond, I guess?), you should see a bunch of
> extra text that you wouldn't see if the \displayLilyMusic wasn't
> there.
>
> The >display.txt  just saves that extra text into a separate file,
> instead of forcing people to scroll back through their console output
> to find the stuff they want to see.
>
> Cheers,
> - Graham