dwm

I didn't notice a thread just for dwm ( http://dwm.suckless.org/ ), so thought I'd start one.

Seems like a very nice window manager once you get it set up the way you want it. Might take a while to get it set up properly though. There's a good tutorial on customization at the site:
http://dwm.suckless.org/customisation/

Also found the info on how to launch it and set up the bar with custom info using xsetroot interesting. See bottom of the page for an example:
http://dwm.suckless.org/tutorial

The one thing I found strange when I was running it was that when I brought up conky in it, conky reported my CPU usage at 100%. Didn't noticed that when just looking at top without conky up though. Anyone run across a situation like this? It certainly seems to be a very lightweight window manager and appears to use less memory than other popular lightweight window managers like fluxbox and openbox, but I was a bit concerned over the reported CPU usage. Either it doesn't like running with conky or I have something in my setup not properly handled.

I also really like the way dmenu (http://tools.suckless.org/dmenu) integrates so nicely with this window manager. Looks even better than it does in other window managers. It just blends in well.

Still working on changing my config.h file. I did like the suggestion on using the Windows key in place of the alt key (http://dwm.suckless.org/customisation/windows_key). That way applications like SciTE (my favorite editor) can make use of the alt key combinations. If anyone has any customization or set up tips to share on dwm, please post. I'm just gettings started with it, but I'd be interested to hear what others have done with it.
 
I've been using dwm for a few years now, and before that used the related wmii; I prefer dwm as it is simpler even than wmii and I really do not mind editing a C header file to tune my preferences, not when compiling and installing happens in the blink of an eye.

Here's top output showing dwm - this instance has been running for several weeks so no, I would not say that it consumes much CPU!

Code:
64523   0 someuser  1  44    0  4520K  1712K select   0:17  0.00% dwm
 
mwatkins said:
I really do not mind editing a C header file to tune my preferences, not when compiling and installing happens in the blink of an eye.

Here's top output showing dwm - this instance has been running for several weeks so no, I would not say that it consumes much CPU!

That looks like really good. Did you do anything special on startup to run it or just call from you .xinitrc file?

I happen to like the fact you can change the settings in the header file, but then I'm a C/C++ programmer. It's one less format you have to learn, if you can just use standard C conventions.
 
I am running dwm via .xinitrc; nothing too special except I like to have my wm launched from within a loop so I can kill it but not the apps; this is handy when changing the dwm configuration and restarting.

If running two displays:

Code:
$HOME/.dwm/dwmstatus | DISPLAY=:0.1 dwm >$HOME/dwm.err 2>&1 & DISPLAY=:0.0 dwm

Currently running just one:
Code:
while true
do
    $HOME/.dwm/dwmstatus | dwm >$HOME/dwm.err
done

I also run a Python-based status bar updater in that loop but as of late it has been dumping out to core once or twice a day; I'll track that down first before publishing it (again).
 
Back
Top