On Wed, Nov 26, 2008 at 06:28:07PM +0000, Thomas Adam wrote:
> 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 didn't think about that, but it's definitely usefull. Even
more, it might print the unexpanded command line as well (with the
$[...] stuff not replaced yet).
> I suppose that's more
> useful, I was just wary of spitting out too much information but I
> shall add this.
As it's only a debugging aid, we shouldn't worry too much about
that.
Ciao
Dominik ^_^ ^_^
--
Dominik Vogt
