I've been trying out #openbox as my window manager. So far, I *really* like it, though I might be using it in a pretty weird way.
(Weird meaning I've turned off all mouse controls, set it up as a static tiling WM, and am configuring it using x-expressions instead of XML)
@codesections Yes, that is a bit weird.. as the mouse support is pretty much the only thing that separates it from a tiling wm. You would probably get more configurability of keyboard nav in a tiling too.
Are you just playing around or why didn't you go with a tiling?
> Yes, that is a bit weird.. as the mouse support is pretty much the only thing that separates [openbox] from a tiling wm. You would probably get more configurability of keyboard nav in a tiling too. Are you just playing around or why didn't you go with a tiling?
Well, I basically *am* using it as a manual/static tiling window manager (like Ratpoison). I don't really like dynamic tiling, but I haven't found a static tiling WM with a config syntax I like, other than #stumpwm
Basically, my goal is to turn #openbox into a tiling window manager with the same feature set as #stumpwm (static tiling, lisp configuration) but without the high memory usage and occasional crashes that annoyed me with StumpWM.
I admit that starting with Openbox is a bit of an odd choice, but it seems to be working so far. But I'd be open to other ideas, if you think a different WM would fit those goals better.
CC @hitime since you asked the same thing in a separate reply
@codesections @hitime hmmm... when it comes to footprint Openbox is surely a good pick. I don't think there are anything out there with those specs. Not that I know anyway. I am biased toward Bspwm but I don't think it matter much. You would have to rewrite whatever you pick.
I would recommend using something like sxhkd though for nav conf. It is really really good. Loose the ob menu and all that stuff because you will not need it.
> I am biased toward Bspwm but I don't think it matter much.
Funially enough, #bspwm was the other WM I've been playing with/considering. I really like the idea of splitting the WM and keyboard handler into separate programs.
> I would recommend using something like sxhkd though for nav conf. It is really really good.
I also really like sxhkd. In fact, I left off a key feature requirement: good support for key chains (e.g., my binding for dmenu is C-Space; C-x; C-f)
The syntax for that binding in sxhkd would be:
control + space; control + x; control + f
And in openbox (with my setup) it would be:
(keybind ((key "C-Space))
(keybind ((key "C-x))
(keybind ((key C-f))
(action ((name "Execute")) "dmenu_run))))
To me, the second is a bit easier to read/work with, but I see how others could disagree.
And I am still thinking about bspwm/sxhkd. Anything else you really like about it/them?
@shellkr @codesections @hitime I've been using XMonad for about 7 years now, and it's great. Except when it comes time to hack on the config ... then it's difficult for me, because I don't speak Haskell. But on the other hand, it speaks multiple monitors very well, which was great when I had 4 screens.
I'd be tempted to try qtile. But sadly for $dayjob I now have a Mac, so the best I can manage is using ShiftIt to do some simple rearrangements.