2008/11/27 Thomas Adam <[email protected]>: > 2008/11/27 Dominik Vogt <[email protected]>: >> On Thu, Nov 27, 2008 at 09:13:22AM +0000, Thomas Adam wrote: >>> 2008/11/27 Mikhael Goikhman <[email protected]>: >>> > On 26 Nov 2008 19:00:53 +0100, Dominik Vogt wrote: >>> >> >>> >> This isn't really helpful. Why not simply print the while command >>> >> line that is being executed, and why limit it to just complex >>> >> functions (if that's what it does). I'd rather have >>> >> "TraceFunctions" that prints *everything*. >>> > >>> > If you configure fvwm with --enable-command-log (FVWM_COMMAND_LOG) then >>> > it will print all commands executed, prefixed with the execution context >>> > type and the time. >>> >>> Great -- this invalidates my patch most likely. >> >> Well, mostly. We should still have am option to activate that at >> run time. > > OK -- I'll see exactly what it does print and come up with something.
I'm dropping this one on the floor. I appreciate "./configure --enable-command-log" isn't run-time changable, but then it's sufficient for what my original patch attempted to do. If someone in the future ever asks about such functionality, I might pick it up, but for now, this is going the way of the dodo. -- Thomas Adam
