James E. Bailey wrote:
> Maybe I don't understand what role the 2 has in this. But it really
> doesn't work for me
2 is stderr. (0 is stdin, 1 is stdout)
>
> bash-3.2$ lilypond test1.ly 2 > err.txt
There is no space between the "2" and the ">" .
> GNU LilyPond 2.11.47 »test1.ly« wird verarbeitet
James E. Bailey wrote:
> I'm using bash, but on OSX. And I don't really get the results that
> I was looking for with this. I still get my errors in stdout.
I run Lily from the command line in XDarwin and I do exactly what
Gilles said and it works fine here. Since the errors are clearly
output to
Hello.
> I'm using bash, but on OSX. And I don't really get the results that I
> was looking for with this. I still get my errors in stdout.
I don't use/have Mac OSX. I have no idea whether lilypond behaves
differently on different OS.
You should post the exact command you are using; hopefully
I'm using bash, but on OSX. And I don't really get the results that I
was looking for with this. I still get my errors in stdout.
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond-user
Hi.
> how can I get (on linux) the error-messages that lilypond produces in a
> separate text-file, that I can save and read with e.g. kwrite?
"lilypond" outputs its messages to the standard error stream.
So, if you use "bash" as a command interpreter, redirect stderr to a file:
$ lilypond test1
Dear lilypond-users,
how can I get (on linux) the error-messages that lilypond produces in a
separate text-file, that I can save and read with e.g. kwrite?
___
lilypond-user mailing list
lilypond-user@gnu.org
http://lists.gnu.org/mailman/listinfo/lilypond
