Reinhard Tartler <[email protected]> writes: > On Mi, Okt 05, 2011 at 14:21:43 (CEST), Måns Rullgård wrote: > >> Georgi Chorbadzhiyski <[email protected]> writes: >> >>> Around 10/05/2011 02:11 PM, Diego Biurrun scribbled: >>>> On Tue, Oct 04, 2011 at 10:27:36PM +0100, Måns Rullgård wrote: >>>>> Georgi Chorbadzhiyski <[email protected]> writes: >>>>>> >>>>>> When requesting debug info the user is already instructed to >>>>>> copy the full program output but in addition to that it needs >>>>>> to provide how the program was called. With this change all >>>>>> command line parameters that are used are shown in the output >>>>>> when verbose output is enabled. >>>>> >>>>> Are users now assumed too stupid to copy the command line they typed, >>>>> yet somehow capable of copying the same thing printed by the program. >>>>> Besides, printing it from within the program requires careful quoting to >>>>> make sure arguments containing whitespace or quotes are unambiguously >>>>> printed. I really don't think it's worth the effort. >>>> >>>> I'm with Georgi on this one and consider it a very worthwhile feature. >>>> I just had the same thoughts about the initial implementation that were >>>> already addressed. I'll test it tomorrow, let's see how it reacts to >>>> spaces, etc... >>> >>> The attached patch handles spaces and quotes. >> >> There are still countless cases you're not handling. >> >> This is nothing but pointless bloat for no reason whatsoever. The >> command line used is BY DEFINITION right above the avconv output in the >> terminal. If users can't copy and paste that, what reason is there to >> believe they can copy and paste *anything at all*? > > Not if avconv is invoked by some frontend script or application.
If that is the case, chances are all output is sent to /dev/null anyway, or at least not using a high verbosity level. Can we please focus on solving actual problems rather than imaginary ones? We have plenty of the former. -- Måns Rullgård [email protected] _______________________________________________ libav-devel mailing list [email protected] https://lists.libav.org/mailman/listinfo/libav-devel
