Brian wrote: > Richard Owlett wrote: > > It would more resemble "Who pulls which string when?" > > In one iteration of my experiments I had been burned by not adding > > "exec openbox" as last line of xinitrc.
The man page for xinit says:
An important point is that programs which are run by .xinitrc should be
run in the background if they do not exit right away, so that they
don't prevent other programs from starting up. However, the last long-
lived program started (usually a window manager or terminal emulator)
should be left in the foreground so that the script won't exit (which
indicates that the user is done and that xinit should exit).
And so there is the explanation. If the .xinitrc script exits then
that indicates to xinit that the user is done and that xinit should
exit, ending the X windows session. Therefore we put the window
manager at the end and run it in the foreground not the background.
> > What other scripts are run
> > at boot that would affect whether Openbox runs "correctly" [quotes
> > significant].
>
> A "correctly" set up X on Debian uses ~/.xsession and not ~/.xinitrc.
> (I kept the quotes because you said they are significant).
Brian, I can't tell if you are joking or not. :-) But obviously a
correctly set up X could use either a .xsession file or a .xinitrc
file. The choice depends upon what is trying to be achieved. And
I know you are aware that there is also the .xsessionrc file too.
I use a .xsession file when using one of the xdm programs. But since
recently when gnome and gdm abandoned my hardware I have been using
xinit again and an .xinitrc file. It is working correctly in that
combination.
Richard, Openbox has its own config file. So of course after openbox
starts it will read ~/.config/openbox/*. Those files will also affect
openbox.
Bob
signature.asc
Description: Digital signature
