Speaking of fvwm startup functions, i notice that after doing enough restarts,
i'll get a pipe2 read error and my modules wont start.
Do pipes automagically get closed on restart?
Do i have to manually kill the modules on a restart?
running 2.5.5but above always true.
Heres my
Elliot Sowadsky [EMAIL PROTECTED] writes:
Speaking of fvwm startup functions, i notice that after doing enough restarts
, i'll get a pipe2 read error and my modules wont start.
Do pipes automagically get closed on restart?
Do i have to manually kill the modules on a restart?
running
Speaking of fvwm startup functions, i notice that after doing enough
restarts
, i'll get a pipe2 read error and my modules wont start.
Do pipes automagically get closed on restart?
Do i have to manually kill the modules on a restart?
running 2.5.5but above always true.
Elliot Sowadsky [EMAIL PROTECTED] writes:
Speaking of fvwm startup functions, i notice that after doing enough rest
arts
, i'll get a pipe2 read error and my modules wont start.
Do pipes automagically get closed on restart?
Do i have to manually kill the modules on a restart?
Next Monday is the soonest I could try this on a Sun,
I might even be 5.8 by then.
But no rushwas wondering if someone had a ready made answer.
Maybe you should try something like I did.
See if you can nail down the number of restarts and find
out if its consistently reproducible.
I'll
Hi all,
I know this was a post of a while ago, but has this been implemented
yet? Will it ever be ?
cheers,
Remko
On 13 Aug 2002, Mikhael Goikhman wrote:
Now when I think about this, I see an elegant solution for these problems.
We only need 2 functions (not including Session*Function
On 02 Oct 2002 10:25:05 +0200, Remko Troncon wrote:
On 13 Aug 2002, Mikhael Goikhman wrote:
Now when I think about this, I see an elegant solution for these problems.
We only need 2 functions (not including Session*Function variants),
StartFunction and ExitFunction.
StartFunction may
On 13 Aug 2002 08:29:48 +0200, Remko Troncon wrote:
I am using xplanet to update my background every couple of minutes. When
i quit fvwm, i would like to kill xplanet so that it doesn't keep on
running. A QuitFunction (called only when actually quitting) would be
convenient for this, but i
It's named ExitFunction.
Yes, i saw the ExitFunction. But the man page says that this function is
called on restarts also. I only want to kill xplanet when actually
quitting.
cheers,
Remko
--
Visit the official FVWM web page at URL: http://www.fvwm.org/.
To unsubscribe from the list, send
On 13 Aug 2002 09:00:30 +0200, Remko Troncon wrote:
It's named ExitFunction.
Yes, i saw the ExitFunction. But the man page says that this function is
called on restarts also. I only want to kill xplanet when actually
quitting.
Well, you may start xplanet in StartFunction instead of
Well, you may start xplanet in StartFunction instead of InitFunction
and ExitFunction will work for you like you want.
That's not really what you would want to do with xplanet.
Or run an fvwm wrapper like this:
xplanet
fvwm
killall xplanet # or: kill `pidof xplanet`
This is indeed
On 13 Aug 2002 09:30:11 +0200, Remko Troncon wrote:
Well, you may start xplanet in StartFunction instead of InitFunction
and ExitFunction will work for you like you want.
That's not really what you would want to do with xplanet.
I don't see a problem with this.
Or run an fvwm wrapper
I don't see a problem with this.
It's a pure luxury problem.
When fvwm is restarted, xplanet doesn't have to be restarted because all
it does is update the background. Restarting it on every fvwm restart is
CPU intensive, and causes the background to blank out for a few seconds.
Noone just
Why don't you just start it in the ~/.xinitrc file?
That's what i was planning to do. But for some strange reason, i
preferred to have it in my fvwmrc, and have as less as possible inside my
.xinitrc. (i know, it's a purely subjective principle, but that's just my
feeling :)
Anyway, i'll
On 13 Aug 2002 13:41:15 +0200, Remko Troncon wrote:
Why don't you just start it in the ~/.xinitrc file?
That's what i was planning to do. But for some strange reason, i
preferred to have it in my fvwmrc, and have as less as possible inside my
.xinitrc. (i know, it's a purely subjective
On 13 Aug 2002 13:12:01 +0200, Remko Troncon wrote:
I'm not saying that i _really_ need it, because as you said before, it
can be moved out of fvwm inside a wrapper. But now that i read the
manual more thoroughly, i get your point on needing Pre-restart
functions. I had the impression that
StartFunction may include conditions StartUp and Restart, ExitFunction
may include conditions Restart and Quit, these conditions are always
false anywhere else. This way InitFunction and RestartFunction are not
needed (not that RestartFunction is needed now anyway).
...
Your approach is
17 matches
Mail list logo
