On Sat, 5 Jan 2002, Dan Espen wrote:
> Alexander Kotelnikov <sacha_at_debian.org> writes:
> > Here is a simple .fvwm2rc that shows this:
> > #
> > DestroyFunc InitFunction
> > AddToFunc InitFunction
> > Module FvwmIconMan
> >
> > DestroyFunc RestartFunction
> > AddToFunc RestartFunction
> > Module FvwmIconMan
> > #
> >
> > Start fvwm with it and you'll get two FvwmIconMan modules, while
> > according to man fvwm only one should appear.
>
> Where did you see that? It should have been:
>
> DestroyFunc InitFunction
> AddToFunc InitFunction
> + I Module FvwmIconMan
>
> DestroyFunc RestartFunction
> AddToFunc RestartFunction
> + I Module FvwmIconMan
>
> But, with recent releases, this would be better:
>
> DestroyFunc
> AddToFunc StartFunction
> + I Module FvwmIconMan
Now I'm confused...
I have a similar problem where the Eterm I launch at startup gets
launched again when I restart. This is undesireable behaviour.
Is there a different place I'm supposed to put it, or how does that work?
I have this:
AddToFunc StartFunction
+ I Exec Esetroot -f /usr/share/pixmaps/vpm_wp_01_1024.jpg &
+ I Exec Eterm -g 26x21+0+552 -F 5x7 -O -T XMessages -e tail -f
$HOME/.X.err
+ I Module FvwmButtons
+ I Module FvwmTaskBar
I do not have an InitFunction or RestartFunction section.
The modules don't seem to be double-started, but the eterm does.
I don't know about the background, since that's kinda hard to test...
*sigh*
-Tenebrae.
--
Visit the official FVWM web page at <URL: http://www.fvwm.org/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_fvwm.org.
To report problems, send mail to fvwm-owner_at_fvwm.org.
Received on Sun Jan 06 2002 - 22:48:39 GMT