Other Help Topics :: Fluxbox 0.9.9

Quote (henk1955 @ Sep. 21 2004,05:13)

this what i did:
put flutbox.0.9.9.tar.gz in c:\

changed /home/dsl/.bash_profile to:

Code Sample

#!/bin/bash
export IRCNICK=DSL
SSH=`env | grep SSH_CONNECTION`
#if [ -z "$SSH" ]; then startx; fi
start_fluxdev

changed /home/dsl/.xinitrc to:

Code Sample

# put X windows programs that you want started here.
# Be sure to add at the end of each command the &
grep enhance /proc/cmdline >/dev/null
if [ $? == 0 ]; then
enhance &>/dev/null &
fi
#dillo -f /usr/share/doc/damnsmall/getting_started.html &>/dev/null &
#/opt/firefox/firefox &
#icewm-session
#wmaker
fluxbox

add /home/dsl/.bash_profile to the filetool.lst
and now the fluxbox-0.9.9. starts

That works, but it's unnecessary to backup .xinitrc if you're using only flux-dev. It uses a copy of .xinitrc instead of the original. Simply changing the .bash_profile line to start_fluxdev is enough. This script is an alternative to startx, so that you can use it to start flux-dev, and fall back on startx for your regular window manager.

<edit>
error in test procedure.
all below is BS
</edit>

a funny thing i found was:
even if there is an: export XINITRC=$HOME/....
and xinit man says:
XINITRC This variable specifies an init file containing shell
commands to start up the initial windows. By default,
.xinitrc in the home directory will be used.

it seems xinit first runs ~/.xinitrc and than $XINITRC
so if you have an ~/xinitrc make sure it doesnt point to an old windowmanager you dont want to use

This might seem to be the case, but it is not. $XINITRC tells xinit which configuration file to use. If that variable is not set, it looks for $HOME/.xinitrc.
Startx apparently ignores $XINITRC, but I haven't verified this.

"by default" means that if there are no available alternatives, it falls back on .xinitrc...it doesn't mean that it uses .xinitrc always.
My $HOME/.xinitrc is not used whenever I load flux-dev or evilwm

original here.