This weekend finally saw enough random free time that I manged a clean install of my laptop, and I think I've gotten it into more-or-less working order.
Anyhow, this is the first time that I've configured my main machine without a desktop environment. I usually run either XFCE or GNOME under my window manager on my primary, and keep crazy things like Screen-as-WM, and odd
bash replacements to my play boxes. Much as I hate to admit it,
x-window-system is still a requirement at an office where you need to co-exist with MS users. Mainly for PDF viewing and documents/spreadsheets, but it also helps to be able to do some image editing if the situation calls for it.
I decided to go with StumpWM over XMonad. The practical differences are minute. XMonad uses a workspace-based structure by default, whereas StumpWM treats windows individually1. Stump treats all windows equally, where XMonad has the concept of a master window in a given layout. StumpWM assumes
C-t as the
mod key, and supports Emacs-style chords out of the box. You can use [XMonad.Actions.Submap](http://xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Actions-Submap.html) to get some of the functionality back, but there are two places it falls short, and those have annoyed me enough to switch back over to the Lisp-based WM.
The first shortfall is, even though you can technically use the submap feature, there doesn't seem to be a good way of simulating the taken keystroke. That is, if you set your XMonad
mod key to
C-t, you now have no way of using
transpose-chars in Emacs or
New Tab in Chrome. StumpWM has a mechanism to let
C-t C-t fake the usual
C-t keystroke to the focused application, but XMonad has nothing similar that I've found.
The second is that certain XMonad keystrokes are designed to have you hold the
mod key, and submap chord keys can't be held. The best example of this is resizing windows. The standard keystrokes are
Mod-l, for growing and shrinking the master window respectively. The way these work is that each invocation grows/shrinks the master window by about 5px, so if you want to do any significant resizing, you'll need multiple calls. If you bind
Mod to a single key, like
Win, you can do a series easily; hold
h h h h h. If on the other hand you want a chorded mod, it gets more complicated;
C+t h C+t h C+t h C+t h C+t h. That's pretty annoying. StumpWM doesn't let you hold chorded keys either, but because they're the default, Stump keys tend to be designed to account for it. For example, the resizing situation above is solved with a separate
interactive-resize setting; you hit
C-R, which puts you into a mode where your arrow keys scale the focused window.
I suppose another solution could have been "get used to
Win as your mod key", but I don't wanna. I'm working on a laptop, so that key is annoyingly narrow, and hitting it properly with my pinkie requires me to scrunch my left hand up somewhat uncomfortably.
So that's that; keeping my hands on the home row without sacrificing functionality is enough to drive me to another window manager.
Other than the WM, I mentioned this was my first time going desktop-less. That produces one or two challenges, the big one being wireless. I'm using
wicd-curses to manage my connections, but that's actually the easy part. The x220 comes with one of three built-in wireless cards, and none of them like Debian very much. What I really ought to do is go out and buy a wifi card that supports free drivers, but in the meantime, this is the one place on my system where I use Debian's
contrib non-free repos. I temporarily added them, and dropped them as soon as I was done installing
I honestly don't know which of those did it, but on the next restart, I had
The other challenge with using a standalone WM is mounting/unmounting USB drives. I don't actually use them very much anymore;
rsync are much more effective at moving files across machines. The only time a thumbdrive comes out is when I need to do a system install, or when I need to exchange non-emailable files with a non-linux user. For those times,
pmount is more than sufficient.
Other than that, I just need to get used to using
acpi to check on my battery periodically, and using
alsamixer to set up the volume the first time. It goes without saying that
caps-lock is an additional
The list of things installed on my system at this point is pretty short actually. Here's a script that duplicates most of the install
### with the contrib non-free repos enabled
apt-get install firmware-iwlwifi firmware-ralink firmware-realtek
### disabled again
apt-get install wireless-tools wicd-curses
apt-get install sbcl clisp erlang erlang-doc
apt-get install make screen dmenu htop gnupg git-core gitk emacs stumpwm slime pmount
apt-get install pacpl mplayer alsa imagemagick gimp inkscape conkeror chromium-browser
I haven't even bothered with databases or web servers yet, though I'm sure I'll have to eventually. I did grab a few applications from source just for the hell of it, and set up my usual utility scripts2,
quicklisp, plus 7 or so
There are a couple of big things I've changed, that you may have noticed, and one big thing I've changed that you definitely didn't. Most of it is pruning things that I've noticed I don't use. The languages I didn't bother installing this time include
> Edit from 2016: Lies! I'm never going back!
Finally, the latest version of
git-core no longer ships with
git.el. That's not entirely a bad thing; I've had to hack a lot of additional pieces onto it for my purposes, and I always sort of wished that it just worked out of the box. It turns out I was one of the ~3 people on the planet not using
magit. Luckily, the lack of direct
git-core has forced me to try it out, and it seems that this mode supports everything I was adding and then some. One or two annoyances, but I haven't run into anything that takes more than a trivial change in my workflow.
So yeah. Net gain, all told.
- You can use groups to approximate the XMonad model, but I haven't played with it much yet.↩
- Though I will be porting the useful ones away from Ruby very shortly.↩
- Which I've been playing around with periodically, but haven't used for anything serious.↩
- Which I'm definitely coming back to at some point, but don't have the time for at the moment.↩
- Which was enough of a pain in the ass to install properly that I'm avoiding it until I actually decide to use it.↩
- Which I'm really sad about actually. However, I haven't used it for anything but scripts for the last little while. The number of scripts I've been writing in it has also been going downhill since I started using