[xmonad] Recommended setup for coding

Ralph Hofmann hofmann2004 at arcor.de
Tue Jan 26 04:00:10 EST 2010

Am Montag, den 25.01.2010, 19:02 -0600 schrieb Spencer Janssen:
> On Mon, Jan 25, 2010 at 08:10:02PM +0100, Ralph Hofmann wrote:
> > The problem persists. 
> > 
> > But: The only window, that makes xmonad hang, seems to be the terminal
> > window, where I killed metacity and started xmonad. As long, as I keep
> > it open, everything seems to be fine. I can open another terminal and
> > close it without a problem. But as soon, as I kill the switching
> > terminal, xmonad hangs. Other windows are having problems only after
> > that.
> > 
> > When I start a session with xmonad from the beginning, in order to avoid
> > the terminal, xmonad hangs instantly.
> > 
> > xmonad.errors is empty and Xsession-errors has only some errors about
> > "atk-bridge-WARNING: AT_SPI_REGISTRY was not started at session
> > startup.", which I am having since long before I started using xmonad.
> > Nothing about xmonad.
> > 
> > Regards,
> > 
> > Ralph
> I think I see what is going on.  When you close the terminal, a SIGHUP signal
> is sent.  The default action for that signal is to immediately exit.  You have
> a few options:
>     * don't close that terminal
>     * don't start xmonad from a terminal; start it with GNOME's regular
>       facilities for starting the WM
>     * run xmonad in a wrapper such as screen or nohup

Starting xmonad with Gnome's regular facilities hangs too.

With xmonad-0.9.1 installed  as debian package from debian sid, which I
used until recently, the reaction on closing the terminal you described
above doesn't occur. So I find it hard to believe, that it should be the
normal behaviour.

For the time being, I will keep the terminal open or use xmonad without
gnome. Maybe I will get used to it.



More information about the xmonad mailing list