>
> Hi guys,
>
> I recently made the switch from fvwm to enlightenment as my default window
> manager.
>
> Currently, my .xsession file looks like this and works fine:
>
> enlightenment
Yep, that should work fine -- but is a bit bland. I can see why you
would want to spiff it up some.
>
> But when I tried to add other progs at startup using the new .xsession file:
>
> enlightenment &
> swisswatch &
> xload &
> xbiff &
>
Yep, that should work lousily. I can see why you don't like this
version ;-).
> it wouldn't work. My .xsession-errors file is as follows:
>
> Imlib Init
> X connection to :0.0 broken (explicit kill or server shutdown).
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> Error: Can't open display: :0
> Xlib: connection to ":0.0" refused by server
> Xlib: Client is not authorized to connect to Server
> Error: Can't open display: :0
>
> Am I going about this the wrong way, is there a better way to do it?
You are -almost- going about it the right way.
The .xsession file is not treated as a configuration file by X, it's
treated as a program to run. Traditionally, it's a shell script, but
technically it could be any program. This is why the .xsession file
has to be executable, for instance.
When the .xsession file exits, that signals X that your session is
over, and it can/should exit as well.
So what is going on here?
In the original case, when you said
enlightenment
you were saying, in effect "Run enlighenment in the forground, and wait
for it to finish. Then exit." Since .xsession didn't finish until
after E finished, all was well.
However, in the refined case, when you said
enlightenment &
xload &
you were saying "Run E in the background, and DON'T wait for it to
finish; then run xload in the background, and DON'T wait for it to
finish; then exit". Since .xsession didn't wait on anything to finish,
it quickly started E, xload, swissclock, and xbiff, then quit. That
caused X to quit.
The easiest way to fix this is to simply have the last program in your
.xession file run in the forground
enlightenment &
xload
Then, when xload exits, X will exit. When I do it this way, I find
that I exit my window manager, and xload will still be running, but I
have to way to kill it! So what I would recommend would be:
xload &
exec enlightenment
The exec says "replace .xsession with enlightenment, rather than
running it separately". It saves one process and probably a miniscule
amount of memory, so it's not necessary, but it's tidy.
>
> Thanks alot in advance
>
--
Buddha Buck [EMAIL PROTECTED]
"Just as the strength of the Internet is chaos, so the strength of our
liberty depends upon the chaos and cacaphony of the unfettered speech
the First Amendment protects." -- A.L.A. v. U.S. Dept. of Justice
