On 08/10/2010 12:31 PM, Derek Scherger wrote:
Sorry, I've been away and I'm late to the party on this but I'm not sure
I like the --verbosity, --quiet, --debug and --reallyquiet options all
that much.
What about this as an alternative:
- default verbosity is 0 as described above
- verbosity can by increased with --verbose (-v) options: -v -v or -vv
would set verbosity to 2
- verbosity can be decreased with --quiet (-q) options: -q -q or -qq
would set verbosity to -2
- remove --debug, --reallyquiet and --verbosity in favour of multiple -v
or -q options?
I basically like it, except you never know where you are. That is, if
someone has their defaults set to "-q" or "-q -q", any frontend they use
needs to be able to turn warnings and progress output back on without
enabling debug output, or turn warnings back on without enabling
progress output, etc.
Hm. We don't currently allow (remote-)automate stdio users to turn on
debug mode (the messages aren't captured, and in the remote case it
would probably allow too much information leakage), so just giving "-v
-v" would always set "normal" mode.
If a frontend wants warnings but not standard P() messages... these are
sufficiently distinguished in automate stdio output, and low enough in
volume, that we can say frontends just have to deal with it.
So if frontends can all use 'automate stdio' for everything, then I
suppose it really isn't an issue. Or we could just say, setting this
option in your defaults may do bad things to frontends/scripts that
don't expect it.
--
Timothy
Free public monotone hosting: http://mtn-host.prjek.net
_______________________________________________
Monotone-devel mailing list
Monotone-devel@nongnu.org
http://lists.nongnu.org/mailman/listinfo/monotone-devel