On Sat, Oct 09, 2010 at 02:54:33PM +0200, Ingo Wardinski wrote:
> Hi there,
> I have a simple question concerning ewmh and fvwm. Recently I was
> forced to recompile fvwm on my machine, since then I have been getting
> (.xsession-errors)
>
> [fvwm][__execute_function]: <<ERROR>> No such command 'EWMHActivateWindowFunc'
>
> which caused by this line in my settings
>
> DestroyFunc EWMHActivateWindowFunc
>
> at least this is the only occurence of it. I thought that I have
> missed something while compiling fvwm, because
Yes -- that's right. Some actions on windows (such as when activity happens
if a window were in a EWMH-compliant taskbar) would trigger this window.
The error is harmless in this case, and you're definitely better off doing:
DestroyFunc EWMHActivateWindowFunc
Than you are doing this:
AddToFunc EWMHActivateWindowFunc I Nop
As that still grabs the window, which might be undesirable in some
situations. But either way, FVWM will still spit that line out to STDERR if
the function cannot be found, as the code expects to call it.
> fvwm --version gives
>
> fvwm 2.5.26 compiled on Oct 8 2010 at 12:29:31
> with support for: ReadLine, RPlay, Stroke, XPM, PNG, SVG, Shape, XShm,
> SM, Xinerama, XRender, XCursor, XFT, NLS
>
> How can I add EWMH hints to the support list? I guess this is done
> while configuring the makefile, at least the manpage is telling that
> it should be possible to compile fvwm with EWMH hints.
No, you get them all for free, you can't turn them off.
> p.s.: For some reasons I would like to stay with fvwm 2.5.26
Why?
-- Thomas Adam
--
"Deep in my heart I wish I was wrong. But deep in my heart I know I am
not." -- Morrissey ("Girl Least Likely To" -- off of Viva Hate.)
