[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: lilypond too noisy on the cmd line
From: |
David Santamauro |
Subject: |
Re: lilypond too noisy on the cmd line |
Date: |
Sat, 1 Jan 2011 02:25:57 -0500 |
Hi,
On Sat, 1 Jan 2011 10:19:18 +0000
Graham Percival <address@hidden> wrote:
> On Sat, Jan 01, 2011 at 09:49:10AM +0000, Mark Veltzer wrote:
> > - version, progress and general messages which are not error
> > messages should go to stdout and NOT stderr.
>
> Good point; I've added this as
> http://code.google.com/p/lilypond/issues/detail?id=1468
>
> > - a --quiet flag should be added to shut down all of the regular
> > messages which are not error messages (meaning those going to
> > stdout).
>
> http://code.google.com/p/lilypond/issues/detail?id=1074
> Patches appreciated. Unfortunately I doubt that anything will
> happen unless you personally work on it, but it's "on the books".
This is something I'd be interested in jumping in on. I've more-or-less
already done it in my sandbox.
Question: Should the be_verbose_global variable control this? I'm not
sure a new command line argument is really needed as long as it is
agreed upon what verbose is and isn't.
I added a be_quiet_global in my sandbox but reading the thread makes me
think that simplification is needed and not an expansion.
David
- lilypond too noisy on the cmd line, Mark Veltzer, 2011/01/01
- Re: lilypond too noisy on the cmd line, Graham Percival, 2011/01/01
- Re: lilypond too noisy on the cmd line,
David Santamauro <=
- Re: lilypond too noisy on the cmd line, Graham Percival, 2011/01/01
- Re: lilypond too noisy on the cmd line, Bertalan Fodor (LilyPondTool), 2011/01/02
- Re: lilypond too noisy on the cmd line, David Santamauro, 2011/01/02
- lilypond logging (Re: lilypond too noisy on the cmd line), David Santamauro, 2011/01/03
- Re: lilypond logging (Re: lilypond too noisy on the cmd line), Matthias Kilian, 2011/01/03
Re: lilypond too noisy on the cmd line, David Kastrup, 2011/01/01