[EMAIL PROTECTED] writes:
>
> On 28-Jan-05, at 12:38 PM, Han-Wen Nienhuys wrote:
> > lilypond-latex is deprecated. This just reminds me that I should junk
> > it.
>
> ok.
>
> > the messages in lilypond --help comes from lily/main.cc
>
> Wow! I've just committed something that changes lily/main
On 28-Jan-05, at 12:38 PM, Han-Wen Nienhuys wrote:
lilypond-latex is deprecated. This just reminds me that I should junk
it.
ok.
the messages in lilypond --help comes from lily/main.cc
Wow! I've just committed something that changes lily/main.cc! I feel
so special now. :)
Do you remember what yo
[EMAIL PROTECTED] writes:
>
> On 27-Jan-05, at 7:51 AM, Han-Wen Nienhuys wrote:
> > Yes - correct. The observed behavior is what we want. Graham, can you
> > update the docs?
>
> Ok, done in CVS. I don't like my addition to lilypond-latex (I assume
> that's
> what pops up if you do "lilypond --
On 27-Jan-05, at 7:51 AM, Han-Wen Nienhuys wrote:
Yes - correct. The observed behavior is what we want. Graham, can you
update the docs?
Ok, done in CVS. I don't like my addition to lilypond-latex (I assume
that's
what pops up if you do "lilypond --help" ?) but I can't think of a
better way
to
[EMAIL PROTECTED] writes:
> The documentation for Lilypond says that
>
>
> -o, --output=FILE
> write output to FILE
>
> But this is not true:
Yes - correct. The observed behavior is what we want. Graham, can you
update the docs?
--
Han-Wen Nienhuys | [EMAIL PROTECTED]
The documentation for Lilypond says that
-o, --output=FILE
write output to FILE
But this is not true:
lilypond --tex -obug.foo bug.ly
GNU LilyPond 2.4.3
Processing `bug.ly'
Parsing...
Interpreting music... [2]
Preprocessing graphical objects...
Calculating line breaks... [2]
Layou
