^ visit the WM section.

new openbox -



new fluxbox -

At request of vastone, working on an openbox theme for VSIDO 2 -

Results to date:

 

Some minor changes to VSIDO aesthetics -

1. Added a clock to the top lxpanel, and this panel is no longer treated as a dock with reserved space to maximize vertical screen real estate.
2. Cleaned up the conky_ob_rc file - removed some double entries and balanced out the linear spacing with ${offset xx}; no changes to colour or system variables.
3. Using a comptonobx.conf - adds some shadows, fade effects, conky window and lxpanel are now excluded from compton effects.

Many additions to rc.xml file to provide window movement and resizing; key binding control to launch VSIDO apps.

thoughts -

Decided to keep openbox around for a while so went ahead and configured it:

@dizzie and devilone - some nice i3 setups.

Clean install of new iso - let the tweaking begin:

@ozitraveller

the i3 version in debian stable is 4.2.x, testing and sid have 4.6.x - there were several changes between those versions; xft font support being one as well as some feature enhancements for container management.

if you want to live on the edge, there is a debian repo you can add to get the latest development release -> http://i3wm.org/docs/repositories.html

No problem -

http://wall.alphacoders.com/big.php?i=362410

at wallpaper abyss if that link is whacked.

Bamboo sort of day -



some cwm minimalism.

@vrkalak - which fluxbox style is that?

finally got around to ripping some cd's -

Does it happen if you are not running compositing?

^ nice one, new look for velociraptor.

@statmonkey - dmenu will compile without issue/patching on debian.

Or are you looking to add some 3rd-party patches? I have seen some configurations that use x,y coordinates and control the width - so it will look like the fluxbox menu; and I think xft fonts require a patch.

back on topic - compiled fvwm the other day -

Back to fluxbox today; using statmonkey's script to burn the latest vsido iso to usb:

Okay, some whacked behavior on my end so hope this doesn't end up posted 3-4 times -

Yes, the default behavior is good; dmenu sources the system $PATH and then narrows the list as you type - so typing "g..c..o.." will allow you to select gcolor2 from the list with arrow keys. As long as you can type the first couple letters of the app, you're good (screenshot)



As far as I know, dmenu still only sources the system $PATH, not the $PATH variable in the user's .bashrc so to make your custom $PATH available to dmenu, it will need to be added to the system $PATH. I have -

export PATH=$PATH:~/bin:~/conky

in my ~/.fluxbox/startup and other wm startup scripts. It works, but may be obsolete.

If you're a script-kiddie of sorts, then dmenu becomes a really powerful tool. Menus for whatever you do - i.e. music, movies, coding, internet - can be created and menu(s) piped to dmenu with key bindings.

If you uninstall and then build dmenu from source, dmenu, dmenu_run, and stest will be installed to /usr/local/bin by default.

It also appears that the vertical patch referred to in the arch forum is now included, but not the x,y,z coordinate configurations they are posting.

@vastone - if you will continue to include i3 with VSIDO, I recommend that dmenu be added; it's the common/standard method of generating a menu for tiling or minimal window managers.

It's actually a very powerful/flexible piece of software - custom menus that include scripts can be piped to dmenu; I've seem some pretty clever menus generated by power users.

Found this -

#!/bin/sh
cachedir=${XDG_CACHE_HOME:-"$HOME/.cache"}
if [ -d "$cachedir" ]; then
cache=$cachedir/dmenu_run
else
cache=$HOME/.dmenu_cache # if no xdg dir, fall back to dotfile in ~
fi
APP=$(
IFS=:
if stest -dqr -n "$cache" $PATH; then
stest -flx $PATH | sort -u | tee "$cache" | dmenu "$@"
else
dmenu "$@" < "$cache"
fi
)

grep -q -w "$APP" ~/.dmenu_term && urxvtc -e $APP || echo $APP | ${SHELL:-"/bin/sh"} &

it's a replacement script for dmenu_run that will launch terminal apps that are listed in the $HOME/.dmenu_term file.

original link at arch forums - https://bbs.archlinux.org/viewtopic.php?pid=1088164#p1088164

You can replace urxvtc with your terminal of choice, and change location/name of .dmenu_term if you prefer; edit script accordingly. The .dmenu_term file is just a plain text list of apps that run in a terminal - I tested it with htop, works fine. It accepts all the dmenu customizations so you can change the colors, font etc ...

create a script that runs the terminal and then calls the script you want to run:

simple example -

#!/bin/sh
uxterm -e <kick-ass-script>

key bind the new script.