Re: stdout vs. stderr (was: Patch: small reduction in output from make doc)
in C++ there's std::cout, std::cerr and std::clog, and I use all three in my private projects. p ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: stdout vs. stderr (was: Patch: small reduction in output from make doc)
Am Samstag, 25. Juni 2011, 20:09:50 schrieb Matthias Kilian: > On Sat, Jun 25, 2011 at 05:27:03PM +0100, Graham Percival wrote: > > 1. what's the official unix definition of STDERR vs. STDOUT? > > Quoting the standard: > > 3.358 Standard Error > An output stream usually intended to be used for diagnostic messages. > [...] > > 3.360 Standard Output > An output stream usually intended to be used for primary data output. > > Of course, this definition is meant for typical unix command line > tools, where you want to pipe the output of one program as input > into another program and still see "diagnostic messages" from the > first program. Lilypond is a little bit different. Many GNU applications work like that. On the other hand "tar -v" print the processed filenames to stdout (not to stderr!). (la|pdf|)tex on the other hand prints everything to stderr, so as a user you have no other choice than either silencing tex altogether (i.e. using batchmode) or having the whole excessive output on the console... There is no way (at least none that I'm aware of) to separate the warning messages of latex from the excessive debug output about including file X and file Y and graphics Z etc Cheers, Reinhold -- -- Reinhold Kainhofer, reinh...@kainhofer.com, http://reinhold.kainhofer.com/ * Financial & Actuarial Math., Vienna Univ. of Technology, Austria * http://www.fam.tuwien.ac.at/, DVR: 0005886 * LilyPond, Music typesetting, http://www.lilypond.org ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: stdout vs. stderr (was: Patch: small reduction in output from make doc)
Graham Percival percival-music.ca> writes:
> >
> > Stdout is used for valuable program output, stderr for any kind of
> > message, including progress. The name stdERR is possibly somewhat
> > unfortunate and comes from the days that unix commands would only
> > print something (to stdERR) if there was an error. No news
> > [was considered to be] good news.
And now that users want some good news "successful completion" messages, we
still want it to be separate from the program output on stdout. I still want
to use :
\displayLilyMusic \transpose f d \relative c' {
\key des\major
des\p\< f as des\f
}
c:\> lilypond test > transposed_motif.ly
>
> Questions for those involved:
What does Lilypond currently put on stdout ?
The output of \displayLilyMusic and \displayMusic; anything else?
___
lilypond-devel mailing list
lilypond-devel@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-devel
Re: stdout vs. stderr (was: Patch: small reduction in output from make doc)
On Sat, Jun 25, 2011 at 05:27:03PM +0100, Graham Percival wrote: > 1. what's the official unix definition of STDERR vs. STDOUT? Quoting the standard: 3.358 Standard Error An output stream usually intended to be used for diagnostic messages. [...] 3.360 Standard Output An output stream usually intended to be used for primary data output. Of course, this definition is meant for typical unix command line tools, where you want to pipe the output of one program as input into another program and still see "diagnostic messages" from the first program. Lilypond is a little bit different. Ciao, Kili ___ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
