Dave Goldberg <dsg_at_linus.mitre.org> wrote:
>
> Instead of starting them in .xsession, create an InitFunction in your
> .fvwmrc and start them from there. If you must put them in .xsession,
> you'll have to use sleep to wait before running the apps to give fvwm
> a chance to start up.
>
I knew I could do that, I just want to avoid doing that;
it is a very unclean solution to the problem. I always start up
one xterm so if fvwm fails and my session falls back on a wm I don't
have configured (or no wm at all), I will have a shell to work in. I
considered it a bug since I have never seen this behavior in another
window manager (MWM).
FVWM must be getting the information it uses to decorate the window
from somewhere. It looks to me as if it is accessing something that
hasn't finished initializing, but it doesn't seem to know that it's
not finished initializing, and continues.
--- Carl
--
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Thu Oct 12 1995 - 20:31:02 BST