On 13 Apr 2003 23:55:29 -0400, J.R. Oldroyd wrote:
On Apr 13, 23:10, Marcus Lundblad wrote:
However, after a restart, it seems these arguments are completely lost
as neither variable is set when the fvwmrc file is re-processed.
What command do you use to restart?
(The full line
Got it. In fact, I see now that this change is even documented in
the man page! Sorry for not having rtfm'd!
Well, with this working, my 2.2.2.5 fvwmrc now works perfectly on
2.5.6. And, 2.5.6 is considerably faster! Great work folks, and
thank you.
-jr
On Apr 14, 09:29, Mikhael
However, after a restart, it seems these arguments are completely lost
as neither variable is set when the fvwmrc file is re-processed.
What command do you use to restart?
(The full line from the menu item or keybinding that restarts).
//Marcus
--
Visit the official FVWM web page at URL:
J.R. Oldroyd [EMAIL PROTECTED] 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
Bound to a menu item, I have:
+ %mini.fvwm.xpm%Restart Fvwm Restart fvwm2
-jr
On Apr 13, 23:10, Marcus Lundblad wrote:
However, after a restart, it seems these arguments are completely lost
as neither variable is set when the fvwmrc file is re-processed.
What command do
