Thanks for clearing this up, Quentin. I have cabal-install already installed from hackage, but I am not yet sure, how it plays together with darcs. When I enter "cabal list xmonad", I get some xmonad packages. Is this already the darcs-version? By the way: How to remove packages correctly with cabal? There is no uninstall. Ralph Am Samstag, den 23.01.2010, 12:20 +0100 schrieb Quentin Moser:

If you aren't planning anything large-scale, you can use any XMonad install and create modules in your ~/.xmonad/lib directory, which is in the search path when XMonad compiles your config. So, for example:

~/.xmonad/lib/XMonad/Layout/ANewLayout.hs ~/.xmonad/lib/XMonad/Util/SomeUtilityStuff.hs

You can import these in your xmonad.hs as if they were part of xmonad-contrib. Using the same hierarchy as the rest of XMonad also makes it easy to integrate your modules into the xmonad-contrib darcs repo if/when you think they're worth it.

There are a number of problems with this simple method though:

* XMonad will recompile _all_ your imported lib/* modules on each recompile, so you can't keep too much stuff in there. It will also compile them without optimizations to reduce the recompilation time, and Haskell without optimization isn't really that fast anymore.

* You can't modify current modules in this way (unless you want to "overlay" them with a completely new one).

* You still need to cabal-install the darcs version when you want to publish patches, since you need to test them at least once against the current head.

So if you find yourself writing a lot of modules, or sending patches to xmonad-contrib regularly, you'll need to work with cabal-install and the xmonad-contrib darcs repo. It's still fairly simple:

* Perform your modifications in the darcs directory. * Type "cabal install" at its top-level when you're done with a change. * "xmonad --recompile" to recompile your xmonad.hs using the new lib. * And you're working in a darcs repo, so you have version control handy.

As for the Haskell Platform, it contains cabal-install so if you can't find a cabal-install package for Ubuntu you can install that instead., but there's nothing else you need in it.

Hope it helps

Quentin

On Sat, Jan 23, 2010 at 10:50 AM, Ralph Hofmann wrote:

...

I would like to try some haskell coding with xmonad. What is the best xmonad install for this purpose?

Is it essential to use the cabal version? What is your opinion about the "Haskell Platform" instead of ghc --> http://sporkcode.wordpress.com/2009/07/11/installing-the-haskell-platform-in...

So far i am using ghc/xmonad-0.9.1 from debian sid, installed on ubuntu 9.10. If possible i would like to keep this unchanged, because everything works fine.

Ralph

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

* On Saturday, January 23 2010, Quentin Moser wrote:

If you aren't planning anything large-scale, you can use any XMonad install and create modules in your ~/.xmonad/lib directory, which is in the search path when XMonad compiles your config. So, for example: ..snip.. There are a number of problems with this simple method though:

* XMonad will recompile _all_ your imported lib/* modules on each recompile, so you can't keep too much stuff in there. It will also compile them without optimizations to reduce the recompilation time, and Haskell without optimization isn't really that fast anymore.

By default, the keybindings bypass xmonad's recompilation checking. The reason for such is that users would then have to touch part of their config to recompile after upgrading xmonad. You can add a binding that only recompiles what ghc believes is necessary: ] ,("M-q", spawn $ "ghc -e 'XMonad.recompile False >>= flip Control.Monad.unless System.Exit.exitFailure'" ] ++ "&& xmonad --restart")

* You can't modify current modules in this way (unless you want to "overlay" them with a completely new one).

I'll note that errors coming from replacing existing modules can be confusing if you don't know what to expect: For example: in contrib A imports U, and A exports some types defined in B. Then if you make your own copy of U (not A) in ~/.xmonad/lib, and import both U and A in your config, you can end up with type errors on arguments you supply to functions from A as: ] Inferred type: U.Type ] Expected type: "xmonad-contrib-0.9":U.Type Which is solved by also copying A over into ~/.xmonad/lib, which Quentin already noted. -- Adam

Everything with xmonad in its name removed and installed again with "cabal install xmonad xmonad-contrib": it works. Then reinstalled from the darcs directories: it still works. I guess, I have xmonad-darcs working now. Ralph Am Montag, den 25.01.2010, 13:52 +0100 schrieb Ralph Hofmann:

I have decided to move to the darcs version, but now xmonad hangs.

I have downloaded xmonad, XMonadContrib and X11 with darcs and installed them with cabal-install without problems. Xmonad recompiles and starts, but only shows fragmented windows and doesn't react properly on keys and mouse. I have to kill the Xsession with Alt-Print-k in order to return to the login-screen. Even with the most simple xmonad.hs.

Everything was fine, as long as I kept the debian installation, but having both installations, I wasn't sure, which version I was running.

After removing all debian packages related to xmonad, the problem occurred for the first time.

What is wrong? Maybe I have removed to much (for example libghc6-xmonad-dev?), but I had assumed, I would get all needed packages from darcs, except ghc of course.

I use Ubuntu-9.10 with ghc-6.10.4.

Ralph

Am Samstag, den 23.01.2010, 12:20 +0100 schrieb Quentin Moser:

...

If you aren't planning anything large-scale, you can use any XMonad install and create modules in your ~/.xmonad/lib directory, which is in the search path when XMonad compiles your config. So, for example:

~/.xmonad/lib/XMonad/Layout/ANewLayout.hs ~/.xmonad/lib/XMonad/Util/SomeUtilityStuff.hs

You can import these in your xmonad.hs as if they were part of xmonad-contrib. Using the same hierarchy as the rest of XMonad also makes it easy to integrate your modules into the xmonad-contrib darcs repo if/when you think they're worth it.

There are a number of problems with this simple method though:

* XMonad will recompile _all_ your imported lib/* modules on each recompile, so you can't keep too much stuff in there. It will also compile them without optimizations to reduce the recompilation time, and Haskell without optimization isn't really that fast anymore.

* You can't modify current modules in this way (unless you want to "overlay" them with a completely new one).

* You still need to cabal-install the darcs version when you want to publish patches, since you need to test them at least once against the current head.

So if you find yourself writing a lot of modules, or sending patches to xmonad-contrib regularly, you'll need to work with cabal-install and the xmonad-contrib darcs repo. It's still fairly simple:

* Perform your modifications in the darcs directory. * Type "cabal install" at its top-level when you're done with a change. * "xmonad --recompile" to recompile your xmonad.hs using the new lib. * And you're working in a darcs repo, so you have version control handy.

As for the Haskell Platform, it contains cabal-install so if you can't find a cabal-install package for Ubuntu you can install that instead., but there's nothing else you need in it.

Hope it helps

Quentin

On Sat, Jan 23, 2010 at 10:50 AM, Ralph Hofmann wrote:

...

I would like to try some haskell coding with xmonad. What is the best xmonad install for this purpose?

Is it essential to use the cabal version? What is your opinion about the "Haskell Platform" instead of ghc --> http://sporkcode.wordpress.com/2009/07/11/installing-the-haskell-platform-in...

So far i am using ghc/xmonad-0.9.1 from debian sid, installed on ubuntu 9.10. If possible i would like to keep this unchanged, because everything works fine.

Ralph

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

This kind of thing is generally the result of building in the wrong order. Can you try cleaning, re-building, and installing, in order: 1. X11 2. xmonad 3. xmonad-contrib 4. xmonad.hs (cleaning involves taking out any .o's/.hi's from .xmonad and .xmonad/lib) and then let us know if the problem persists? If so, ~/.Xsession-errors, ~/.xmonad/xmonad.errors, or the output of xmonad itself may give more information as well, so please send those. Cheers, ~d Quoting Ralph Hofmann :

Am Montag, den 25.01.2010, 15:11 +0100 schrieb Ralph Hofmann:

...

Everything with xmonad in its name removed and installed again with "cabal install xmonad xmonad-contrib": it works.

Then reinstalled from the darcs directories: it still works.

I guess, I have xmonad-darcs working now.

No, that was too fast. I had just hitten the send-email button and got a freeze.

I am now back to the version from "cabal install xmonad ..." (which freezes too) and have found something, that I can reproduce:

I start the session with metacity, open a terminal and enter "killall metacity && xmonad &". Now I am on xmonad with the terminal still open. When I close the terminal with the kill-shortkey (by default (modm .|. shiftMask, xK_c)) I get a freeze. It's only partial, I can call Gnome-Do for example, but I can't switch workspaces anymore. I also got freezes when starting firefox.

I have added my xmonad.hs, in case someone would like to check it.

Ralph

I have just started xmonad without Gnome: apparently no problem. There seems to be something wrong with the gnome integration of xmonad-darcs. Cheers, Ralph Am Montag, den 25.01.2010, 20:10 +0100 schrieb Ralph Hofmann:

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

Am Montag, den 25.01.2010, 10:58 -0500 schrieb wagnerdm@seas.upenn.edu:

...

This kind of thing is generally the result of building in the wrong order. Can you try cleaning, re-building, and installing, in order:

1. X11 2. xmonad 3. xmonad-contrib 4. xmonad.hs (cleaning involves taking out any .o's/.hi's from .xmonad and .xmonad/lib)

and then let us know if the problem persists? If so, ~/.Xsession-errors, ~/.xmonad/xmonad.errors, or the output of xmonad itself may give more information as well, so please send those.

Cheers, ~d

Quoting Ralph Hofmann :

...

Am Montag, den 25.01.2010, 15:11 +0100 schrieb Ralph Hofmann:

...

Everything with xmonad in its name removed and installed again with "cabal install xmonad xmonad-contrib": it works.

Then reinstalled from the darcs directories: it still works.

I guess, I have xmonad-darcs working now.

No, that was too fast. I had just hitten the send-email button and got a freeze.

I am now back to the version from "cabal install xmonad ..." (which freezes too) and have found something, that I can reproduce:

I start the session with metacity, open a terminal and enter "killall metacity && xmonad &". Now I am on xmonad with the terminal still open. When I close the terminal with the kill-shortkey (by default (modm .|. shiftMask, xK_c)) I get a freeze. It's only partial, I can call Gnome-Do for example, but I can't switch workspaces anymore. I also got freezes when starting firefox.

I have added my xmonad.hs, in case someone would like to check it.

Ralph

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

_______________________________________________ xmonad mailing list xmonad@haskell.org http://www.haskell.org/mailman/listinfo/xmonad

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. Greetings, Ralph