X and Fluxbox :: Fluxbox 0.9.10 NEW

I just deleted my old fluxbox0.9.9.tar.gz and replaced it with 0.9.10 (from repository testing)

(i removed all lines in filetool.lst which where refurring to the old fluxbox and did a new backup so that there are no traces left of the old fluxbox when rebooting)

Rebooted. Saw that flux0.9.10 was installed and then... JUST the prompt (can't find START_FLUXDEV)

Did a <whereis start_fluxdev> but couldn't find it
Did a cd to fluxbox (in opt) and tried to run <fluxbox> (in bin)message: (connection to x-server failed)

HELP?

Please ALWAYS read the documentation provided with an application. In this case it is the info file (also i thought my PM explained this

)...

I removed the wrapper because it's no longer needed. The 0.9.9 extension had one because I couldn't figure out any other way to keep it from messing with the configuration files of Fluxbox stable. Since I got that problem solved, starting 0.9.10 is done in the same way any other window manager would be in a standard setup:
1) Open $HOME/.xinitrc
2) Change the line "fluxbox" to "/opt/fluxbox-0.9.10/bin/fluxbox"
3) Start X with the "startx" command

Hello again,

Some notes: there is NO entry in my .xinitrc for fluxbox (there is a "start_fluxdev" command in my ~/.bash_profile:

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

(i removed the last line but it didn't help me)

Please help?

Ok, I get it....you added start_fluxdev to bash_profile so it would auto start. But start_fluxdev uses it's own xinitrc file, so you didn't need to edit xinitrc.

Remove the fluxdev line from bash_profile and uncomment the previous line.
This way startx will be run instead of start_fluxdev (it was a startx replacement). The last line in .xinitrc should be "fluxbox" or "exec fluxbox", so if it's not, then make it so.

Sorry, I tried to make 0.9.9 easy to use without editing anything, but maybe that made it even more confusing. From now on all my window manager extensions will be the standard "edit xinitrc and restart x".

Here's a hint for using multiple window managers with startx...
Personally I don't care for having ~/.xinitrc limited to one wm at a time, so I wrote something which will allow me to send arguments to xinit, and if no arguments are passed it defaults to fluxbox:

Code Sample

ARG="$@"

# specify the default wm argument here:
DEFAULTWM="fluxbox"

if [ ! $ARG ]; then
ARG=$DEFAULTWM
fi

case $ARG in
evil)
fbsetbg -f ~/image/paper/firepenguin.jpg
root-tail --noinitial --font snap -f --color red4 --whole --cont ........ --cont-color black -g 512x384+4+0 \
${HOME}/.fluxbox/log,red4,'general' \
/var/log/warn,DarkOrange4,'warn' \
/var/log/XFree86.0.log,tomato4,'XFree86' \
/var/log/smpppd/ifcfg-ppp0.log,orange4,'pppd' &
WM='/opt/evilwm/evilwm -term aterm'
;;
ion)
Esetroot -f ~/.fluxbox/backgrounds/doom3.jpg
WM=ion
;;
bb)
WM=blackbox
;;
ob)
WM=openbox
;;
twm)
xterm &
xclock -digital -bg black -fg gray -update 1 -geometry -0+0 &
xsetroot -solid MidnightBlue
WM=twm
;;
kde)
WM=kde
;;
wmi)
WM=/opt/wmi/bin/wmi
;;
xwnc)
WM='Xwnc -ac -geometry 1024x768 :1'
;;
*)
xsetroot -solid Black
WM="$ARG"
;;
esac

# Start the window manager
exec $WM &> ~/.fluxbox/log

This is put at the end of .xinitrc in place of the fluxbox line.
You could simplify it to just this:

Code Sample

ARG="$@"
DEFAULTWM="fluxbox"

if [ ! $ARG ]; then
ARG=$DEFAULTWM
fi
WM="$ARG"
exec $WM

The difference is that the first one allows for abbreviated WM names and additional commands...the second one just launches whatever you use as an argument. For example, you could do "startx firefox" to start an X session with just firefox and no window manager.

Next Page...
original here.