On Thu, 18 Jul 1996 12:49:49 -0400
Richard Soubyran <soubyran_at_delirium.discreet.qc.ca>
wrote concerning 'FVWM: What next?':
> Hello FVWM'ers!
>
> I have an SGI Indy running IRIX 5.3 I have compiled fvwm 2 on it and everything
> went fine!
>
> I ran the make install to install the whole package... but after that... what
> should I do next? I already have 4Dwm running. Do I need to play with the
> different xdm files? How do I disable the 4Dwm and set up the fvwm running
> instead? Will I still be able to open xwsh shells in fvwm?
Richard
On the SGIs the Xserver is already running. When you "log in" at the
login box you are actually running an xdm "session". As the session
starts a script called /usr/lib/X11/xdm/Xsession is run. This looks for a
file called $HOME/.xsession and runs that if it exists. The first time you
use a .xsession file you will be prompted with a dialog box. Just click
OK (or Continue, can't remember which).
Your .xsession should start clients, window manager, etc. I have a couple
of examples below which also run your .profile, for sh, bash users. You'll
have to hack this if you have csh as your login shell. I like to
run the .profile so that all clients inherit environment variables
(remember this is a "session", not a "login").
I recommend you get the "xsession" program which allows you to manage
your session, change window managers on the fly, etc. Should be available
at your local x.org mirror (I can probably get you an Irix 5.3 binary if
you have trouble). If you get it the following .xsession would be suitable:
######################################################################
## run user's Xdefaults
if [ -f ${HOME}/.Xdefaults ] ; then
xrdb -load ${HOME}/.Xdefaults
fi
## source system profile
if [ -f /etc/profile ] ; then
. etc/profile
fi
## source user's profile
if [ -f ${HOME}/.profile ] ; then
. ${HOME}/.profile
fi
## Clear root window
xsetroot -def
## START CLIENTS HERE
## These must run in the background.
## start an xterm and any other clients here
xterm &
## xsession now takes over management of the session. This must come
## last. Quit xsession to quit X.
xsession -defaultWM fvwm2
######################################################################
If you don't have xsession, use this:
######################################################################
## run user's Xdefaults
if [ -f ${HOME}/.Xdefaults ] ; then
xrdb -load ${HOME}/.Xdefaults
fi
## source system profile
if [ -f /etc/profile ] ; then
. etc/profile
fi
## source user's profile
if [ -f ${HOME}/.profile ] ; then
. ${HOME}/.profile
fi
## Clear root window
xsetroot -def
## start window manager
fvwm2 & wmpid=$!
## START CLIENTS HERE
## These must run in the background.
## start an xterm and any other clients here
xterm &
## wait for the wm to exit, i.e. quitting fvwm will exit the X session
wait $wmpid
######################################################################
A really minimal .xsession would be:
######################################################################
xterm &
fvwm2
######################################################################
Make sure you have a file ${HOME}/.fvwm2rc, otherwise fvwm2 won't run.
Just copy the system.fvwm2rc supplied.
Ric
~~~~~~~~~~~~~~ Richard J. Lister r.j.lister_at_aston.ac.uk ~~~~~~~~~~~~~~~~
Research Assistant, Neural Computing Research Group
Aston University, Birmingham B4 7ET, UK
~~~~~~~~~~~~~~~~~
http://www.ncrg.aston.ac.uk/~listerrj/ ~~~~~~~~~~~~~~~~~~
--
Visit the official FVWM web page at <URL:http://www.hpc.uh.edu/fvwm/>.
To unsubscribe from the list, send "unsubscribe fvwm" in the body of a
message to majordomo_at_hpc.uh.edu.
To report problems, send mail to fvwm-owner_at_hpc.uh.edu.
Received on Fri Jul 19 1996 - 06:00:35 BST