Jose Romildo Malaquias <romildo_at_uber.com.br> writes:
> Hello.
>
> Starting of applications seems to not be working as expected in my
> FVWM 2.5.5 configuration.
>
> In order to have Eterm started once (at initialization time) and
> FvwmButtons on initialization and restart times, I have the
> following
>
> AddToFunc InitFunction
> + "I" exec Eterm
>
> AddToFunc StartFunction I Module FvwmButtons
>
> in my ~/.fvwm/.fvwm2rc configuration file. When FVWM is started,
> none of Eterm and FvwmButtons is shown, until I press a mouse
> button (if anywhere in the screen, only the Eterm appears, if in
> any window client area, both appear).
>
> Any clues?
First, ignore that advice about using "Exec" instead of "exec".
Fvwm commands are not case sensitive.
If you are getting a delay until you press a button, most
likely you have a command in your .fvwm2rc that needs a target
window. Fvwm is waiting for you to indicate which window you want
the command to operate on.
For example, if you had the command:
Move
in your .fvwm2rc, fvwm wouldn't know which window you want to
move and it would wait until you clicked somewhere
to indicate which window to move. (If you click on the root,
it just aborts the command.)
Look for a command in your .fvwm2rc that needs a window.
If you can't find anything, post your .fvwm2rc here.
--
Dan Espen E-mail: dane_at_mk.telcordia.com
--
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 Mon Dec 09 2002 - 13:05:47 GMT