From 83f0e9e0533470e037c5e3954a6707134cf0b66b Mon Sep 17 00:00:00 2001
From: Niels Serup <ns@metanohi.name>
Date: Sat, 13 Aug 2011 23:55:57 +0200
Subject: [PATCH] Fixed StumpWM = modified page

---
 site/writings/stumpwm.org | 47 ++++++++++++++++++++++++---------------
 1 file changed, 29 insertions(+), 18 deletions(-)

diff --git a/site/writings/stumpwm.org b/site/writings/stumpwm.org
index 2402c19..69690db 100644
--- a/site/writings/stumpwm.org
+++ b/site/writings/stumpwm.org
@@ -9,7 +9,29 @@ How I've set up StumpWM on Trisquel
 I use StumpWM instead of e.g. Gnome. StumpWM is a tiling window manager, which
 means that it's a good window manager.
 
-** Problems
+** The setup
+
+I just added a file ~stumpwm.desktop~:
+#+BEGIN_SRC
+[Desktop Entry]
+Encoding=UTF-8
+Type=XSession
+Exec=stumpwm
+TryExec=stumpwm
+Name=StumpWM
+Comment=Stump window manager
+#+END_SRC
+to ~/usr/share/xsessions/~, and then I could login to StumpWM via GDM.
+
+** Links
+
+  + [[http://stumpwm.antidesktop.net/][StumpWM]]
+  + [[https://gitorious.org/nqpz-config/nqpz-config/blobs/raw/master/home/.stumpwmrc][My .stumpwmrc]]
+
+
+** Old problems
+
+/I have fixed these problems. They remain here for historical reasons only./
 
 I never had any problems with StumpWM until I upgraded to Trisquel 4.0 and
 Trisquel 4.5, after which StumpWM irregularly threw errors such as:
@@ -20,16 +42,7 @@ GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting.
 and also some fatal X errors which killed StumpWM and all its running
 programs. This naturally annoyed me. I soon realized that it had nothing to do
 with Trisquel, it was just that dependencies on things like D-Bus was getting
-on StumpWM's nerves. I had always used an Xsession file to login to StumpWM:
-#+BEGIN_SRC
-[Desktop Entry]
-Encoding=UTF-8
-Type=XSession
-Exec=stumpwm
-TryExec=stumpwm
-Name=StumpWM
-Comment=Stump window manager
-#+END_SRC
+on StumpWM's nerves. I had always used an Xsession file to login to StumpWM,
 but clearly, this wasn't good enough. Whenever I ran the default gnome-session
 and whatever window manager was associated to that, there were no problems. And
 while in gnome-session, I could always run:
@@ -41,7 +54,11 @@ was killed --- all windows were maintained. This made me realize that one could
 create a script which starts a new StumpWM instance whenever an old StumpWM
 crashes, to create the illusion of a continually running StumpWM.
 
-** Solution
+*** Solution
+
+I compiled StumpWM from git with SBCL instead of CLISP. Now it doesn't crash.
+
+*** Original solution
 
 I added this to my ~.profile~:
 #+BEGIN_SRC sh
@@ -60,9 +77,3 @@ fi
 
 You may also have to edit ~gnome-panel~ out of
 ~/desktop/gnome/session/required_components~ in ~gconf-editor~.
-
-** Links
-
-  + [[http://stumpwm.antidesktop.net/][StumpWM]]
-  + [[https://gitorious.org/nqpz-config/nqpz-config/blobs/raw/master/home/.stumpwmrc][My .stumpwmrc]]
-