
Hi Xmonaders I'm planning to use xmonad as the main vehicle for a 3-hr tutorial on Haskell at the Open Software Convention 2007, in 3 weeks time. The goal is to teach Haskell (not xmonad per se), but by doing it in the context of xmonad I hope to motivate and excite the audience. The audience is professional programmers, not undergrads. They are Java, Ruby, Python experts. I plan to go pretty fast. I want to make use of Quickcheck, maybe HPC, too. So my plan is to show them xmonad and then rapidly zoom in on some small purely-functional part to do some Haskell programming. So I need to - show slides - edit code - recompile - and show the resulting window manager in action Advice is that the safest thing to do is to run xmonad inside xnest, so that the slides, editor etc are not disturbed. SO HERE'S THE QUESTION Can someone give me some idiot-level step by step instructions for how to run xmonad inside xnest, alongside other running applications? I have all the pieces; I just need to know how to set up the config files or whatever. I know some of you have done this. Timescale: I'm going to working on this for the next 3 weeks, and then I have to deliver the tutorial. Needless to say I'd also love to have your suggestions for simple Haskell programming stuff that could be described and demo'd in this way. Don is already thinking about this -- thanks Don. thanks (NB: I'm not on the xmonad list, so pls include me in replies!) Simon

On Fri, Jun 22, 2007 at 01:11:28PM +0100, Simon Peyton-Jones wrote:
Can someone give me some idiot-level step by step instructions for how to run xmonad inside xnest, alongside other running applications? I have all the pieces; I just need to know how to set up the config files or whatever. I know some of you have done this.
I haven't used this for a while, and there might be more bulletproof ways to do this, but I used to run xmonad inside xmonad (with different modkeys) using this shell script (or rather, something like it - I've thrown out some vestigal stuff). Caveat: I haven't tested this before sending - but it ought to be reasonable, I think. -- #!/bin/sh Xnest :1 -name "Xnest" +kb -ac -bw 5 -geometry 1260x780 & XNEST_PROC=$! DISPLAY=:1 xsetroot -display :1 -solid gray /home/gimbo/xmonad/xmonad/dist/build/xmonad/xmonad wait $! kill $XNEST_PROC -- Hope this helps! -Andy -- Andy Gimblett Computer Science Department University of Wales Swansea http://www.cs.swan.ac.uk/~csandy/

| I haven't used this for a while, and there might be more bulletproof | ways to do this, but I used to run xmonad inside xmonad (with | different modkeys) using this shell script (or rather, something like | it - I've thrown out some vestigal stuff). Oh good stuff! It actually works. Thanks. On the original xterm I get some "Could not init font path element" errors, plus "XLib: extension "XINERAMA" missing" but they don't seem to stop the xnest window displaying and xmonad functioning inside it. Ok, so I'm off home base, thanks. Simon

simonpj:
| I haven't used this for a while, and there might be more bulletproof | ways to do this, but I used to run xmonad inside xmonad (with | different modkeys) using this shell script (or rather, something like | it - I've thrown out some vestigal stuff).
Oh good stuff! It actually works. Thanks.
On the original xterm I get some "Could not init font path element" errors, plus "XLib: extension "XINERAMA" missing"
but they don't seem to stop the xnest window displaying and xmonad functioning inside it.
Ok, so I'm off home base, thanks.
Wonderful. Next step is probably to walk through the 'guided tour' to get a sense of the interface, and then try some simple changes to Config.hs;recompile; mod-q to reload the changes and see them reflected. -- Don
participants (3)
-
Andy Gimblett
-
dons@cse.unsw.edu.au
-
Simon Peyton-Jones