[MPlayer-DOCS] documenting lavdopts debug=0x4000
Diego Biurrun
diego at biurrun.de
Thu Feb 2 13:15:31 CET 2006
On Thu, Jan 26, 2006 at 10:54:11AM -0600, Jeff Clagg wrote:
> Well, there are probably MANY things that could be added to the
> documentation of lavdopts, but currently the easiest way to decipher the
> meaning of the output of "lavdopts debug=0x4000" is a combination of
> rtfs and lavdopts debug=0x4008. However, once we open this can of worms,
> the lavdopts section of the man page might become extremely long.
Patches most welcome :)
> Nevertheless, I'm going to suggest that we add explanations in the man
> page of what each block tint/color actually means. One of my questions
> is, should we stick to the old vertical listing style, which takes up a
> heck of a lot of space, or just list them in sentence form?
I'd be tempted to keep the vertical listing, but this is a secondary
issue. Once we have the text it's easy to reformat it.
> Other cans of worms: if we document these, why not also document all the
> output from debug=8 as well?
I'd love to see it documented..
Diego
More information about the MPlayer-DOCS
mailing list