Hi --
2008/11/26 Dominik Vogt <[EMAIL PROTECTED]>:
> On Tue, Nov 25, 2008 at 11:58:47PM +0000, Thomas Adam wrote:
>> I've (perhaps crudely) implemented an option to BugOpts called
>> TraceComplexFunctions. Recently in #fvwm on irc.freenode.net,
>> someone there had a nasty workaround in their file to stop some random
>> application from taking focus, by using !FPFocusByFunction. But not
>> really knowing what it did, other than the effect it had, meant that
>> most of his other complex functions weren't working if they were
>> calling Focus.
> [snip]
>
> Good idea. However, I see no reason to limit the debug output as
> much:
>
> "function ('Function') called on window ('~/src/fvwm' : 0x800004)"
>
> 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*.
It will print any function, not just complex functions, so I suppose
it's a slight misnomer. When you say it should print everything, do
you mean the actions in the function as well? I suppose that's more
useful, I was just wary of spitting out too much information but I
shall add this.
> The patch had some whitespace issues that I cleaned up in the
> attached new patch:
Sigh. Thank you -- I told vim numerous times to be nice, but I
suppose it wasn't, I'll beat it a little more for V2 of this patch so
as not to waste your time further.
-- Thomas Adam
