"J.R. Oldroyd" <nn_at_opal.com> writes:
> I recently upgraded from Fvwm 2.2.2.5 to 2.4.14 and then on to 2.5.6.
>
> I notice with the 2.4 and 2.5 versions, that Fvwm loses my command line
> arguments over a Restart. Preprocessing of the fvwmrc file is therefore
> incorrect after the restart.
>
> To illustrate, this is what I do. I invoke fvwm like this:
>
> fvwm2 -cmd "FvwmCpp $HOME/.fvwm2rc -DDPY$DISPSZ=1 ${APM:+-DAPM=1}" &
>
> This will define two Cpp variables: DPYnnnxnnnn and APM. I then test
> these and do appropriate things to the display, based on its size and
> whether or not APM power management is in use. On the first run, this
> works fine.
>
> However, after a restart, it seems these arguments are completely lost
> as neither variable is set when the fvwmrc file is re-processed.
>
> FWIW, this worked perfectly in 2.2.2.5, even after a restart.
There have been some changes in the area of restart.
This is from the man page:
If you need a native restart, we suggest
only to use Restart command without parame
ters unless there is a reason not to. If
you still use an old command 'Restart fvwm2'
that was correct in 2.2.x, all current com
mand line arguments are lost. On Restart
without parameters or with --pass-args, they
are preserved.
There are some other details in the man page that may be of interest.
--
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 Sun Apr 13 2003 - 16:22:30 BST