Re: Starting xscreensaver

* Joe Giles <[email protected]> [05-05-10 22:02]:
> Myles Green wrote:
> > On May 9, 2005 16:47, Jerry Van Brimmer wrote:
> > > Well, here's the headscratching part. I'm at work right now trying to
> > > get   it working a machine here. At home all I did was add the
> > > xscreensaver command to the ~/.fluxbox/startup script, and it worked
> > > right away. Here at work it won't work. Same Slackware, same fluxbox,
> > > just a different machine. I'm puzzled and stumped; don't know why it
> > > won't work just like at home???
> > Hi, You've probably checked this already, my apologies if you have, but is 
> > the ~/.fluxbox/startup script executable?
> > HTH, Myles
> Not sure if this is relevant to your situation, but I ran into this the other 
> night when I reinstalled. I was executing the Fluxbox command and not 
> startfluxbox. Once I started using startfluxbox (Located in the same directory 
> as Fluxbox (/usr/local/bin on my machine)) the ~/.fluxbox/startup file started 
> working again.
> Hope this helps...
> Joe

Yeah, same situation here. startfluxbox is a simple script which parses
startup file and executes commands in it.

If you're executing $PATH/fluxbox (which many display managers do by
default) then the same effect can be achieved by adding:

[startup] {command}

to your $HOME/.fluxbox/apps file. That fact is well documented in
fluxbox(1) in distinction from the way of loading applications with
startup file. :-)

Apart from OP's question... Why does fluxbox reload those [startup]
lines every time I hit "restart" from the menu? That irritates me. :-) 

-- 
Daniel Vrcic


-------------------------------------------------------
This SF.Net email is sponsored by Oracle Space Sweepstakes
Want to be the first software developer in space?
Enter now for the Oracle Space Sweepstakes!
http://ads.osdn.com/?ad_id=7393&alloc_id=16281&op=click