From droundy at darcs.net Sat Dec 1 07:15:40 2007 From: droundy at darcs.net (David Roundy) Date: Sat Dec 1 07:11:24 2007 Subject: [xmonad] Prompt: Keys not working In-Reply-To: <20071201015210.GB3130@localhost.localdomain> References: <20071129170022.GA7029@dbruhn.de> <20071129171808.GE1252@laptop.nowhere.net> <20071129172737.GA23195@dbruhn.de> <20071130115047.GF1252@laptop.nowhere.net> <20071130124624.GH12228@darcs.net> <20071130173156.GA15071@laptop.nowhere.net> <20071130175034.GE29431@darcs.net> <20071201015210.GB3130@localhost.localdomain> Message-ID: <20071201121527.GI29431@darcs.net> On Fri, Nov 30, 2007 at 05:52:10PM -0800, Stefan O'Rear wrote: > On Fri, Nov 30, 2007 at 12:50:56PM -0500, David Roundy wrote: > > On Fri, Nov 30, 2007 at 06:31:57PM +0100, Andrea Rossato wrote: > > > On Fri, Nov 30, 2007 at 07:46:41AM -0500, David Roundy wrote: > > > > (Obviously) sounds like a memory leak. Presumably we're allocating X > > > > resources and never freeing them. But since they're unused, they get > > > > swapped out. I suppose this means carefully auditing all X calls. I wish > > > > we had *slightly* higher-level X calls that did GC for us (i.e. had > > > > finalizers to destroy objects when they're no longer in use). It'd be > > > > slightly problematic, since finalizers aren't guaranteed to be called at > > > > exit, so we might leak something when we restart, but that seems like a > > > > small danger relative to that of leaking while we run. > > > > > > I just want to make it clear that I suffer from this problem well > > > *before* switching to xmonad, so I don't think this is related to > > > xmonad. > > > > > > allbery_b once suggested it could be firefox, which is well know for > > > allocating tons of pixmaps without freeing them... > > > > Ah, I didn't catch this. That's a real bummer--it makes it far more > > challenging to catch bugs like this. :( > > (Install and) run 'xrestop' to remove all doubt. Hmmmm. For some reason xrestop shows xmonad as "". Is there something we could to to make this remove more doubt? I can identify xmonad in the list by restarting xmonad, but that seems like a poor trick for catching leaks... -- David Roundy Department of Physics Oregon State University -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071201/f100f3f9/attachment-0001.bin From mailing_list at istitutocolli.org Sun Dec 2 06:41:51 2007 From: mailing_list at istitutocolli.org (Andrea Rossato) Date: Sun Dec 2 06:38:16 2007 Subject: [xmonad] Prompt: Keys not working In-Reply-To: <20071201015148.GA3130@localhost.localdomain> References: <20071129170022.GA7029@dbruhn.de> <20071129171808.GE1252@laptop.nowhere.net> <20071129172737.GA23195@dbruhn.de> <20071130115047.GF1252@laptop.nowhere.net> <20071130124624.GH12228@darcs.net> <20071201015148.GA3130@localhost.localdomain> Message-ID: <20071202114151.GC15071@laptop.nowhere.net> On Fri, Nov 30, 2007 at 05:51:48PM -0800, Stefan O'Rear wrote: > On Fri, Nov 30, 2007 at 07:46:41AM -0500, David Roundy wrote: > > (Obviously) sounds like a memory leak. Presumably we're allocating X > > resources and never freeing them. But since they're unused, they get > > swapped out. I suppose this means carefully auditing all X calls. I wish > > we had *slightly* higher-level X calls that did GC for us (i.e. had > > finalizers to destroy objects when they're no longer in use). It'd be > > slightly problematic, since finalizers aren't guaranteed to be called at > > exit, so we might leak something when we restart, but that seems like a > > small danger relative to that of leaking while we run. > > Not a problem. The X connection file descriptor, if memory serves, is > marked as FD_CLOEXEC, so when xmonad execs itself, the connection is > closed. Then the X server reads an EOF on the connection and deletes > all resources, same as it does when an X program crashes. I must confess I cannot relate to this description. I'm using very few X applications: firefox, urxvt and xpdf, at the present moment. Plus xmonad and xmobar. This is the output of xrestop and top with and without firefox and xpdf. I must confess I don't understand: I don't think xmonad and xmobar may be leaking so much (I'm quite careful in freeing all resource). Anyway before tonight I will have to restart X, since *all* my swap memory is almost gone. In xmonad only tabbed creates a GC, pixmaps and a FontStruct. Or it must be the server itself. Andrea With Firefox and XPdf ===================== xrestop - Display: localhost:0 Monitoring 23 clients. XErrors: 0 Pixmaps: 33497K total, Other: 253K total, All: 33751K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 1400000 687 45 1 690 338 30417K 26K 30443K 2397 Firefox 0a00000 0 0 0 1 1 1536K 24B 1536K ? 0600000 1 12 1 12 2 672K 1K 673K ? 2600000 65 24 7 89 8 510K 9K 519K ? xpdf 2800000 65 22 7 52 8 357K 9K 366K ? xpdf 0c00000 0 1 0 0 4166 0B 97K 97K ? 0e00000 8 1 13 0 452 0B 23K 23K ? 0800000 1 2 1 0 888 0B 21K 21K ? screensaver 1000000 2 5 17 1 50 3K 18K 21K 2235 urxvt 1c00000 2 5 6 1 36 156B 7K 7K 26141 urxvt 3000000 59 8 1 0 138 0B 5K 5K ? 1200000 2 5 4 1 27 624B 4K 5K 2298 urxvt 1600000 2 5 3 1 25 156B 3K 3K 2436 mc - /tmp 1a00000 2 5 3 0 23 0B 3K 3K 16418 mc - ~/devel/haskell/src/ghc/ghc/compiler/rename 1800000 2 5 3 0 23 0B 3K 3K 2500 mc - ~/devel/haskell/src/xmonad-lib/XMonadContrib 2e00000 2 5 3 0 6 0B 3K 3K 22313 ssh 2a00000 2 5 3 0 6 0B 3K 3K 5504 urxvt 2000000 2 5 3 0 6 0B 3K 3K 20716 arossato@haskell.org: /srv/code/XMonadContrib 1e00000 2 5 3 0 6 0B 3K 3K 2697 urxvt 0400000 0 2 3 0 2 0B 3K 3K ? 0200000 0 1 1 0 0 0B 1K 1K ? 2c00000 1 1 0 0 0 0B 48B 48B ? xrestop 2400000 1 0 0 0 0 0B 24B 24B ? top - 12:18:33 up 18 days, 4:24, 18 users, load average: 0.42, 0.47, 0.25 Tasks: 169 total, 1 running, 165 sleeping, 3 stopped, 0 zombie Cpu(s): 1.7%us, 0.7%sy, 0.0%ni, 86.1%id, 11.3%wa, 0.3%hi, 0.0%si, 0.0%st Mem: 515900k total, 502000k used, 13900k free, 18712k buffers Swap: 987988k total, 837844k used, 150144k free, 63904k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 2397 andrea 15 0 282m 149m 14m S 0.0 29.8 141:15.99 firefox-bin 21804 andrea 16 0 86732 79m 2368 S 0.0 15.8 249:11.65 emacs-21.4-no-x 2009 root 15 0 704m 63m 2440 S 1.0 12.7 211:45.85 X 1985 root 15 0 19004 16m 1388 S 0.0 3.2 17:14.57 tor 23166 andrea 15 0 42432 13m 8712 S 0.0 2.7 0:01.53 ghc-6.6.1 15071 andrea 15 0 15168 11m 1584 S 0.0 2.3 0:37.14 mutt 28932 apache 15 0 50604 5332 2732 S 0.0 1.0 0:05.53 httpd 1650 apache 15 0 49280 4600 2732 S 0.0 0.9 0:07.02 httpd 1652 apache 15 0 49284 4600 2732 S 0.0 0.9 0:08.19 httpd 1648 apache 15 0 49284 4592 2732 S 0.0 0.9 0:07.65 httpd 1651 apache 15 0 49280 4592 2732 S 0.0 0.9 0:06.96 httpd 1649 apache 15 0 49280 4536 2684 S 0.0 0.9 0:07.30 httpd 2186 andrea 15 0 19892 4492 1228 S 0.0 0.9 0:15.68 xpdf 28935 apache 15 0 49280 4488 2668 S 0.0 0.9 0:04.68 httpd 1756 apache 15 0 49284 4348 2732 S 0.0 0.8 0:06.40 httpd 19565 andrea 15 0 32356 3540 1640 S 0.3 0.7 129:21.36 xmobar 15056 mysql 16 0 101m 3536 1992 S 0.0 0.7 0:03.07 mysqld 16418 andrea 15 0 10004 3164 1144 S 0.0 0.6 0:03.09 urxvt 19566 andrea 15 0 9564 2740 1676 S 0.0 0.5 3:07.43 xmonad 31730 andrea 17 0 7332 2508 1856 S 0.0 0.5 0:00.21 aspell Without Firefox and Xpdf ======================== xrestop - Display: localhost:0 Monitoring 19 clients. XErrors: 0 Pixmaps: 2212K total, Other: 181K total, All: 2394K total res-base Wins GCs Fnts Pxms Misc Pxm mem Other Total PID Identifier 0a00000 0 0 0 1 1 1536K 24B 1536K ? 0600000 1 12 1 12 2 672K 1K 673K ? 0c00000 0 1 0 0 4191 0B 98K 98K ? 0e00000 5 1 13 0 367 0B 21K 21K ? 1000000 2 5 17 1 50 3K 18K 21K 2235 urxvt 1c00000 2 5 6 1 36 156B 7K 7K 26141 urxvt 1200000 2 5 4 1 27 624B 4K 5K 2298 urxvt 1600000 2 5 3 1 25 156B 3K 3K 2436 mc - /tmp 1a00000 2 5 3 0 23 0B 3K 3K 16418 mc - ~/devel/haskell/src/ghc/ghc/compiler/rename 1800000 2 5 3 0 23 0B 3K 3K 2500 mc - ~/devel/haskell/src/xmonad-lib/XMonadContrib 2e00000 2 5 3 0 6 0B 3K 3K 22313 ssh 2a00000 2 5 3 0 6 0B 3K 3K 5504 urxvt 2000000 2 5 3 0 6 0B 3K 3K 20716 arossato@haskell.org: /srv/code/XMonadContrib 1e00000 2 5 3 0 6 0B 3K 3K 2697 urxvt 0400000 0 2 3 0 2 0B 3K 3K ? 0800000 1 2 1 0 30 0B 1K 1K ? screensaver 0200000 0 1 1 0 0 0B 1K 1K ? 1400000 1 1 0 0 0 0B 48B 48B ? xrestop 2400000 1 0 0 0 0 0B 24B 24B ? top - 12:29:45 up 18 days, 4:35, 18 users, load average: 0.29, 0.19, 0.18 Tasks: 165 total, 1 running, 161 sleeping, 3 stopped, 0 zombie Cpu(s): 15.9%us, 1.3%sy, 0.0%ni, 82.7%id, 0.0%wa, 0.0%hi, 0.0%si, 0.0%st Mem: 515900k total, 363248k used, 152652k free, 21152k buffers Swap: 987988k total, 781384k used, 206604k free, 71600k cached PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND 21804 andrea 15 0 86884 79m 2412 S 14.6 15.8 249:20.64 emacs-21.4-no-x 2009 root 15 0 677m 53m 1820 S 1.0 10.6 211:54.85 X 1985 root 15 0 19004 16m 1388 S 0.0 3.2 17:14.77 tor 15071 andrea 16 0 15296 11m 1640 S 0.0 2.3 0:37.65 mutt 23166 andrea 15 0 42432 10m 5864 S 0.0 2.2 0:01.53 ghc-6.6.1 28932 apache 15 0 50604 5332 2732 S 0.0 1.0 0:05.53 httpd 1650 apache 15 0 49280 4600 2732 S 0.0 0.9 0:07.02 httpd 1652 apache 15 0 49284 4600 2732 S 0.0 0.9 0:08.19 httpd 1648 apache 15 0 49284 4592 2732 S 0.0 0.9 0:07.65 httpd 1651 apache 15 0 49280 4592 2732 S 0.0 0.9 0:06.96 httpd 1649 apache 15 0 49280 4536 2684 S 0.0 0.9 0:07.30 httpd 28935 apache 15 0 49280 4488 2668 S 0.0 0.9 0:04.68 httpd 31730 andrea 16 0 7332 4452 3752 S 0.0 0.9 0:00.32 aspell 1756 apache 15 0 49284 4348 2732 S 0.0 0.8 0:06.40 httpd 15056 mysql 16 0 101m 3536 1992 S 0.0 0.7 0:03.08 mysqld 19565 andrea 15 0 32356 3528 1640 S 0.7 0.7 129:24.95 xmobar 16418 andrea 15 0 10004 3152 1144 S 0.0 0.6 0:03.09 urxvt 19566 andrea 15 0 9564 2764 1676 S 0.0 0.5 3:07.69 xmonad From nlv at lab321.ru Tue Dec 4 06:11:16 2007 From: nlv at lab321.ru (Nikitin Lev) Date: Tue Dec 4 06:07:51 2007 Subject: [xmonad] Problem in Installing xmonad Message-ID: <1196766676.7270.11.camel@pc29.lab.com> Hello. I'm trying install xmonad (0.4.1). I use debian linux 4.0 r1 I've installed new version of ghc: 6.8.1, version of X11 is 1.3.0. When I configure xmonad (runhaskell Setup.lhs configure) I get error: ------------------- XMonad.hs:42:17: Could not find module `Data.Set': it is a member of package containers-0.1.0.0, which is hidden ------------------- Can anybody help me? P.S. With older version of ghc (from debian distr, I had problem to install old-time and old-locale packages...). P.S.S. I'm novice in haskell. Is there any tutorial how to install (update) new haskell packages (for ghc)? From astsmtl at gmail.com Tue Dec 4 09:05:35 2007 From: astsmtl at gmail.com (Alexander Tsamutali) Date: Tue Dec 4 09:01:54 2007 Subject: [xmonad] Problem in Installing xmonad In-Reply-To: <1196766676.7270.11.camel@pc29.lab.com> References: <1196766676.7270.11.camel@pc29.lab.com> Message-ID: <20071204190535.708e1018@gmail.com> ? Tue, 04 Dec 2007 17:11:16 +0600 Nikitin Lev ?????: > Hello. > > I'm trying install xmonad (0.4.1). > I use debian linux 4.0 r1 > I've installed new version of ghc: 6.8.1, version of X11 is 1.3.0. > When I configure xmonad (runhaskell Setup.lhs configure) I get error: > > ------------------- > XMonad.hs:42:17: > Could not find module `Data.Set': > it is a member of package containers-0.1.0.0, which is hidden > ------------------- I can confirm this problem on Source Mage. Recently i had updated ghc to 6.8.1 and xmonad to 0.4.1. On one box everything worked fine, but on another i've got the same problem. I tried to hide/expose containers with ghc-pkg, but it didn't helped. -- Alexander Tsamutali From valery.vv at gmail.com Tue Dec 4 09:31:43 2007 From: valery.vv at gmail.com (Valery V. Vorotyntsev) Date: Tue Dec 4 09:27:16 2007 Subject: [xmonad] Problem in Installing xmonad In-Reply-To: <20071204190535.708e1018@gmail.com> References: <1196766676.7270.11.camel@pc29.lab.com> <20071204190535.708e1018@gmail.com> Message-ID: On 12/4/07, Alexander Tsamutali wrote: > I can confirm this problem on Source Mage. Recently i had > updated ghc to 6.8.1 and xmonad to 0.4.1. On one box everything worked > fine, but on another i've got the same problem. I tried to hide/expose > containers with ghc-pkg, but it didn't helped. This resembles my problem, described at http://hpaste.org/4182 Until I know, what's wrong, I use this patented trick to install xmonad & XMonadContrib: $ for f in ghc{,-pkg}; do mv ~/bin/{,_}$f; done ... your normal configure/build/install procedure ... $ for f in ghc{,-pkg}; do mv ~/bin/{_,}$f; done -- vvv From dons at galois.com Tue Dec 4 12:05:10 2007 From: dons at galois.com (Don Stewart) Date: Tue Dec 4 12:00:56 2007 Subject: [xmonad] Problem in Installing xmonad In-Reply-To: <20071204190535.708e1018@gmail.com> References: <1196766676.7270.11.camel@pc29.lab.com> <20071204190535.708e1018@gmail.com> Message-ID: <20071204170510.GA27525@scytale.galois.com> astsmtl: > ? Tue, 04 Dec 2007 17:11:16 +0600 > Nikitin Lev ?????: > > > Hello. > > > > I'm trying install xmonad (0.4.1). > > I use debian linux 4.0 r1 > > I've installed new version of ghc: 6.8.1, version of X11 is 1.3.0. > > When I configure xmonad (runhaskell Setup.lhs configure) I get error: > > > > ------------------- > > XMonad.hs:42:17: > > Could not find module `Data.Set': > > it is a member of package containers-0.1.0.0, which is hidden > > ------------------- > > I can confirm this problem on Source Mage. Recently i had > updated ghc to 6.8.1 and xmonad to 0.4.1. On one box everything worked > fine, but on another i've got the same problem. I tried to hide/expose > containers with ghc-pkg, but it didn't helped. You'll need to update the .cabal file, or use the xmonad 0.5 (darcs) branch. Ghc 6.8, with the base package split up, happened just after 0.4.1 came out. See this faq, http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions#Building_xmonad_0.4.x_with_GHC_6.8 Cheers, Don From dons at galois.com Tue Dec 4 15:28:40 2007 From: dons at galois.com (Don Stewart) Date: Tue Dec 4 15:24:31 2007 Subject: [xmonad] xmonad news: now available via rss Message-ID: <20071204202840.GB28083@scytale.galois.com> You can now subscribe to an RSS feed of announcements for xmonad, http://xmonad.org/xmonad.xml So use this to avoid a release slipping by :) Also, we should have xmonad 0.5 out the door by the weekend, once the quality assurance pass completes. Yay! -- Don From dons at galois.com Wed Dec 5 01:16:01 2007 From: dons at galois.com (Don Stewart) Date: Wed Dec 5 01:11:42 2007 Subject: [xmonad] xmonad 0.5 release candidates Message-ID: <20071205061601.GA22103@scytale.galois.com> Release candidates for the upcoming 0.5 xmonad are available, for the beta testers: http://xmonad.org/xmonad-0.4.20071204.tar.gz http://xmonad.org/xmonad-contrib-0.4.20071204.tar.gz You'll need X11 1.4 from hackage.haskell.org. These should work fine with ghc 6.6 or ghc 6.8, and use the new ~/.xmonad/ configuration system. Documentation isn't up yet, so drop by the IRC channel if you get stuck, or anything goes wrong. The more testing, the better the release! -- Don From nlv at lab321.ru Wed Dec 5 00:08:45 2007 From: nlv at lab321.ru (Nikitin Lev) Date: Wed Dec 5 03:34:54 2007 Subject: [xmonad] Problem in Installing xmonad In-Reply-To: <20071204170510.GA27525@scytale.galois.com> References: <1196766676.7270.11.camel@pc29.lab.com> <20071204190535.708e1018@gmail.com> <20071204170510.GA27525@scytale.galois.com> Message-ID: <1196831325.8373.0.camel@pc29.lab.com> Very thanks. From lobzang at free.fr Thu Dec 6 10:01:11 2007 From: lobzang at free.fr (lobzang@free.fr) Date: Thu Dec 6 09:56:38 2007 Subject: [xmonad] (no subject) Message-ID: <1196953271.47580eb78bced@imp.free.fr> Hi guys, It seems that my ghc configuration is broken ( /usr/lib/ghc-6.8.1/package.conf ) . Is there a way to re-install properly cabal / ghc ? I would like to make a clean install of xmonad. thanks in advance, Lobzang. From codesite-noreply at google.com Thu Dec 6 10:55:34 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 10:51:01 2007 Subject: [xmonad] Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver Message-ID: <00c09ffb53810440a0290dc4c1d54dd@google.com> Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 New issue report by byorgey: What steps will reproduce the problem? I am not entirely sure how to reproduce it reliably -- it only seems to happen if the screensaver is running for a while. 1. lock the screen with xscreensaver/let computer sit idle for a while/close laptop lid. (?) 2. unlock screen. What is the expected output? What do you see instead? xmonad no longer responds to keyboard input. I can still switch to a virtual terminal with Ctrl-Alt-F1, though. xmonad is definitely still running, and the mouse still works. Focus still follows the mouse and applications seem to respond to keyboard input. It seems that opening a new window causes xmonad to start responding to keyboard input again. What version of the product are you using? On what operating system? latest darcs, on Ubuntu gutsy. Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From astsmtl at gmail.com Thu Dec 6 11:59:25 2007 From: astsmtl at gmail.com (Alexander Tsamutali) Date: Thu Dec 6 11:55:47 2007 Subject: [Xmonad] xmonad 0.4 now in debian In-Reply-To: <20071105104750.022fac04@gmail.com> References: <1194209406.4089.6.camel@otto.ehbuehl.net> <20071104205332.GC18890@scytale.galois.com> <20071105104750.022fac04@gmail.com> Message-ID: <20071206215925.56e4d1f6@gmail.com> ? Mon, 5 Nov 2007 10:47:50 +0500 Alexander Tsamutali ?????: > ? Sun, 4 Nov 2007 12:53:32 -0800 > Don Stewart ?????: > > > While we're here, do people know of any other package systems > > including xmonad, beyond: > > > > * OpenBSD > > * NetBSD > > * FreeBSD > > > > * Debian > > * Gentoo > > * Ubuntu > > * Gobo > > * Arch > > Source Mage GNU/Linux has spell: > http://codex.sourcemage.org/stable/windowmanagers/xmonad/ > > You can just "cast xmonad" to install it. Currently xmonad.org information is a bit wrong. Our distribution is called "Source Mage GNU/Linux" or "Source Mage". So "Source Mage Linux" is inaccurate. Also it's better to use URL which I posted above, it's shorter and will be available always, unlike the URL which points to the Ibiblio mirror. -- Alexander Tsamutali From lobzang at free.fr Thu Dec 6 12:23:06 2007 From: lobzang at free.fr (lobzang@free.fr) Date: Thu Dec 6 12:18:33 2007 Subject: [xmonad] how can I completely re-install ghc/cabal/xmonad ? Message-ID: <1196961786.47582ffae40b2@imp.free.fr> Hi guys, It seems that my ghc configuration is broken ( /usr/lib/ghc-6.8.1/package.conf ) . Is there a way to re-install properly cabal / ghc ? (or at least find a way to fix my conf) I would like to make a clean install of xmonad. thanks in advance, Lobzang. From mailing_list at istitutocolli.org Thu Dec 6 13:23:57 2007 From: mailing_list at istitutocolli.org (Andrea Rossato) Date: Thu Dec 6 13:20:27 2007 Subject: [xmonad] xmonad 0.5 release candidates In-Reply-To: <20071205061601.GA22103@scytale.galois.com> References: <20071205061601.GA22103@scytale.galois.com> Message-ID: <20071206182357.GB30904@laptop.nowhere.net> On Tue, Dec 04, 2007 at 10:16:01PM -0800, Don Stewart wrote: > Documentation isn't up yet, so drop by the IRC channel if you get > stuck, or anything goes wrong. It is great having this pre-release. I'm sorry but I've been dreadfully busy this week. There's is this MPEG guy, Chiariglione, very highly regarded by the Italian establishment, who proposed, just a couple of days ago, to introduce a mandatory Trusted Computing infrastructure in Italy, with a regulation that would basically make it impossible to develop any kind of free software, so I've been busying writing other kind of documentation and code...;) I hope to finish what's missing (which is not must stuff actually) by the end of the week. I didn't have the time to see if in the last 48 hours the monoid stuff has been pushed, but I'll resync myself with the outside world by tommorow...;) Cheers, Andrea From dons at galois.com Thu Dec 6 15:26:14 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 15:26:50 2007 Subject: [xmonad] how can I completely re-install ghc/cabal/xmonad ? In-Reply-To: <1196961786.47582ffae40b2@imp.free.fr> References: <1196961786.47582ffae40b2@imp.free.fr> Message-ID: <20071206202614.GE27446@scytale.galois.com> lobzang: > Hi guys, > > It seems that my ghc configuration is broken ( /usr/lib/ghc-6.8.1/package.conf ) > . Is there a way to re-install properly cabal / ghc ? (or at least find a way > to fix my conf) > I would like to make a clean install of xmonad. You can start by unregistering packages you installed. Then install cabal, then X11, xmonad et al. -- Don From max.rabkin at gmail.com Thu Dec 6 15:45:07 2007 From: max.rabkin at gmail.com (Max Rabkin) Date: Thu Dec 6 15:40:32 2007 Subject: [xmonad] Input Methods and Hangul Message-ID: I have just switched to XMonad from KDE, where I was using SKIM to input Hangul. I haven't been able to work out how to run SCIM in XMonad. Unfortunately, most of the google hits for "xmonad scim" are in Japanese, which I don't understand (I wouldn't know enough Korean to understand them, even if they were in Korean). Can somebody who has setup SCIM or another CJK input program please point me in the right direction? --Max From dons at galois.com Thu Dec 6 15:56:50 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 15:52:24 2007 Subject: [xmonad] [stettberger@dokucode.de: [dwm] dinput 0.2] Message-ID: <20071206205650.GA30271@scytale.galois.com> Might be useful to some xmonaders. ----- Forwarded message from Christian Dietrich ----- Date: Thu, 6 Dec 2007 21:31:01 +0100 From: Christian Dietrich To: dynamic window manager Subject: [dwm] dinput 0.2 Hi, I released a new version of dinput[1] today. dinput is a derivative of dmenu, but with a history and line editing. In this version i added support for binding actions to keystrokes. For example will -e '^a=popen(xclip -o)' define a keybinding for ctrl+a, which inserts the output of `xclip -o` command to the actual cursor position. Feel free to comment. cheers, didi [1] http://dokucode.de/cgi-bin/show.sh?path=/Projects/dinput -- No documentation is better than bad documentation ----- End forwarded message ----- From xj2106 at columbia.edu Thu Dec 6 16:23:25 2007 From: xj2106 at columbia.edu (Xiao-Yong Jin) Date: Thu Dec 6 16:20:49 2007 Subject: [xmonad] Input Methods and Hangul In-Reply-To: (Max Rabkin's message of "Thu, 6 Dec 2007 22:45:07 +0200") References: Message-ID: <87wsrrfrg2.fsf@columbia.edu> "Max Rabkin" writes: > I have just switched to XMonad from KDE, where I was using SKIM to > input Hangul. I haven't been able to work out how to run SCIM in > XMonad. Unfortunately, most of the google hits for "xmonad scim" are > in Japanese, which I don't understand (I wouldn't know enough Korean > to understand them, even if they were in Korean). > > Can somebody who has setup SCIM or another CJK input program please > point me in the right direction? Start it in your ~/.xinitrc or ~/.Xclients or ~/.Xsession or whatever X init files your system use. Be sure to setup some environment variables properly, such as GTK_IM_MODULE and XMODIFIERS. And also make sure that the locale is correct. Xiao-Yong -- c/* __o/* <\ * (__ */\ < From dons at galois.com Thu Dec 6 17:21:05 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 17:16:33 2007 Subject: [xmonad] Input Methods and Hangul In-Reply-To: <87wsrrfrg2.fsf@columbia.edu> References: <87wsrrfrg2.fsf@columbia.edu> Message-ID: <20071206222105.GD30271@scytale.galois.com> xj2106: > "Max Rabkin" writes: > > > I have just switched to XMonad from KDE, where I was using SKIM to > > input Hangul. I haven't been able to work out how to run SCIM in > > XMonad. Unfortunately, most of the google hits for "xmonad scim" are > > in Japanese, which I don't understand (I wouldn't know enough Korean > > to understand them, even if they were in Korean). > > > > Can somebody who has setup SCIM or another CJK input program please > > point me in the right direction? > > Start it in your ~/.xinitrc or ~/.Xclients or ~/.Xsession or > whatever X init files your system use. Be sure to setup > some environment variables properly, such as GTK_IM_MODULE > and XMODIFIERS. And also make sure that the locale is > correct. Is this something that should be in the FAQ? I'd love to see some more text on locale/encoding support details, Add any relevant questions and answers here: http://haskell.org/haskellwiki/Xmonad/Frequently_asked_questions Cheers, Don From mike at datagrok.org Thu Dec 6 18:34:17 2007 From: mike at datagrok.org (Michael F. Lamb) Date: Thu Dec 6 18:29:45 2007 Subject: [xmonad] Input Methods and Hangul In-Reply-To: <87wsrrfrg2.fsf@columbia.edu> References: <87wsrrfrg2.fsf@columbia.edu> Message-ID: <20071206233417.GA25610@strange.dreamhost.com> > > Can somebody who has setup SCIM or another CJK input > > program please point me in the right direction? > > Start it in your ~/.xinitrc or ~/.Xclients or ~/.Xsession > or whatever X init files your system use. Be sure to > setup some environment variables properly, such as > GTK_IM_MODULE and XMODIFIERS. And also make sure that > the locale is correct. If you're on a Debian box (or maybe derivatives like Ubuntu as well), you may 'sudo aptitude install im-switch'; this will somewhat automate and manage the setup in a wm-agnostic way. (I use this for Japanese text through SCIM.) From dominik at dbruhn.de Thu Dec 6 19:18:51 2007 From: dominik at dbruhn.de (Dominik Bruhn) Date: Thu Dec 6 19:14:26 2007 Subject: [xmonad] darcs patch: Sshprompt: Add explanation for the completion in sshprompt Message-ID: <20071207001851.GA13722@dbruhn.de> Skipped content of type multipart/mixed-------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071207/324e553b/attachment-0001.bin From dons at galois.com Thu Dec 6 19:51:03 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 19:46:32 2007 Subject: [xmonad] 0.5 and packages Message-ID: <20071207005103.GA31460@scytale.galois.com> Has anyone attempted to try out packing up the release candidates for xmonad, for their favourite package systems? http://xmonad.org/xmonad.xml (for details) The process of packaging should be a lot simpler now -- as xmonad the binary can be reconfigured without recompiling, making the package maintainers job simpler. However, it would still be good to get some feedback on packaging before the release. Particular from the high profile package systems -- debian, gentoo et al. Any thoughts? -- Don From dons at galois.com Thu Dec 6 20:57:55 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 20:54:03 2007 Subject: [xmonad] 0.5 and packages In-Reply-To: References: Message-ID: <20071207015755.GB31561@scytale.galois.com> xmonad-bounces: > The attached message has been automatically discarded. > Date: Fri, 07 Dec 2007 02:50:59 +0100 > From: Joachim Breitner > To: xmonad@haskell.org > Subject: Re: [xmonad] 0.5 and packages > > Hi, > > Am Donnerstag, den 06.12.2007, 16:51 -0800 schrieb Don Stewart: > > Has anyone attempted to try out packing up the release candidates for > > xmonad, for their favourite package systems? > > > > http://xmonad.org/xmonad.xml (for details) > > > > The process of packaging should be a lot simpler now -- as xmonad the > > binary can be reconfigured without recompiling, making the package > > maintainers job simpler. > > > > However, it would still be good to get some feedback on packaging before > > the release. Particular from the high profile package systems -- debian, > > gentoo et al. > > Well, I acted preparationally: > http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=454440 > (Bug against libghc6-x11-dev, maintained by Ian Lynagh, to packate the > new version of X11). Yep, we'll need X11 1.4 > > Once that is done, I?ll have a look at the new release, which probably > already obsoletes what I have done with xmonad-rebuild in the last > release :-) Yes, xmonad-rebuild and similar scripts won't be required now. There will still be a runtime dependency on GHC, as usual. Also, X11-extras no longer is used (instead, X11 1.4.0) -- Don From codesite-noreply at google.com Thu Dec 6 23:30:31 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 23:25:56 2007 Subject: [xmonad] Issue 94 in xmonad: Reduce required imports in xmonad.hs configuration files Message-ID: <001485095e200440aab4f9ffe7ed01@google.com> Issue 94: Reduce required imports in xmonad.hs configuration files http://code.google.com/p/xmonad/issues/detail?id=94 Comment #1 by dons00: (No comment was entered for this change.) Issue attribute updates: Labels: -Milestone-Release0.5 Milestone-Release0.6 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Thu Dec 6 23:34:32 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 23:29:56 2007 Subject: [xmonad] Issue 77 in xmonad: web page contrib.html should be generated from haddocks/src Message-ID: <00c09ff7928c0440aac3568dd813c5db@google.com> Issue 77: web page contrib.html should be generated from haddocks/src http://code.google.com/p/xmonad/issues/detail?id=77 Comment #1 by dons00: Done. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Thu Dec 6 23:38:33 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 23:33:56 2007 Subject: [xmonad] Issue 67 in xmonad: Request: 'ratpoison -c' alike Message-ID: <00163600d06e0440aad1b004c413cd48@google.com> Issue 67: Request: 'ratpoison -c' alike http://code.google.com/p/xmonad/issues/detail?id=67 Comment #2 by dons00: (No comment was entered for this change.) Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Thu Dec 6 23:42:34 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 23:37:58 2007 Subject: [xmonad] Issue 70 in xmonad: Extension request: Command to open a temporary window manager, or replace XMonad with a different one Message-ID: <000fea77e35b0440aae008fe76efa3@google.com> Issue 70: Extension request: Command to open a temporary window manager, or replace XMonad with a different one http://code.google.com/p/xmonad/issues/detail?id=70 Comment #2 by dons00: Someone can do this if they like. Only raised once though, so we won't take action. Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Thu Dec 6 23:46:37 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Thu Dec 6 23:42:01 2007 Subject: [xmonad] Issue 73 in xmonad: xmonad as a library Message-ID: <000fea7b80a70440aaee8fb866ef7e@google.com> Issue 73: xmonad as a library http://code.google.com/p/xmonad/issues/detail?id=73 Comment #5 by dons00: Documentation done. Only thing left is an example, commented-out xmonad.hs users can use as a template. Issue attribute updates: Labels: -Priority-Medium Priority-Critical -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From dons at galois.com Thu Dec 6 23:54:56 2007 From: dons at galois.com (Don Stewart) Date: Thu Dec 6 23:50:30 2007 Subject: [Xmonad] xmonad 0.4 now in debian In-Reply-To: <20071206215925.56e4d1f6@gmail.com> References: <1194209406.4089.6.camel@otto.ehbuehl.net> <20071104205332.GC18890@scytale.galois.com> <20071105104750.022fac04@gmail.com> <20071206215925.56e4d1f6@gmail.com> Message-ID: <20071207045456.GB31984@scytale.galois.com> astsmtl: > ? Mon, 5 Nov 2007 10:47:50 +0500 > Alexander Tsamutali ?????: > > > ? Sun, 4 Nov 2007 12:53:32 -0800 > > Don Stewart ?????: > > > > > While we're here, do people know of any other package systems > > > including xmonad, beyond: > > > > > > * OpenBSD > > > * NetBSD > > > * FreeBSD > > > > > > * Debian > > > * Gentoo > > > * Ubuntu > > > * Gobo > > > * Arch > > > > Source Mage GNU/Linux has spell: > > http://codex.sourcemage.org/stable/windowmanagers/xmonad/ > > > > You can just "cast xmonad" to install it. > > Currently xmonad.org information is a bit wrong. Our distribution is > called "Source Mage GNU/Linux" or "Source Mage". So "Source > Mage Linux" is inaccurate. Also it's better to use URL which I posted > above, it's shorter and will be available always, unlike the URL which > points to the Ibiblio mirror. > Thanks! I've updated both of these. (the website will resync shortly) -- don From dons at galois.com Fri Dec 7 00:23:19 2007 From: dons at galois.com (Don Stewart) Date: Fri Dec 7 00:18:43 2007 Subject: [xmonad] Component-Contrib: patch LayoutScreens.hs In-Reply-To: <475022f5.01b7660a.424a.4877@mx.google.com> References: <475022f5.01b7660a.424a.4877@mx.google.com> Message-ID: <20071207052319.GC31984@scytale.galois.com> jacula: > Hello haskellers, > > Configuring my first xmonad start, I ran into a little misspelling mistake > in the LayoutScreens.hs usage notes. The patch is, I think, self > explanatory. A patch for this was applied. Thanks! -- Don From max.rabkin at gmail.com Fri Dec 7 02:21:49 2007 From: max.rabkin at gmail.com (Max Rabkin) Date: Fri Dec 7 02:17:14 2007 Subject: [xmonad] Input Methods and Hangul In-Reply-To: <87wsrrfrg2.fsf@columbia.edu> References: <87wsrrfrg2.fsf@columbia.edu> Message-ID: On Dec 6, 2007 11:23 PM, Xiao-Yong Jin wrote: > And also make sure that the locale is > correct. Does that mean I must set my locale to KO to write Korean? Because I can't do that: I don't understand enough Korean for my programs to run in it. But I'm learning, so I like to be able to type in it sometimes. --Max > Xiao-Yong > -- > c/* __o/* > <\ * (__ > */\ < > From xj2106 at columbia.edu Fri Dec 7 13:41:47 2007 From: xj2106 at columbia.edu (Xiao-Yong Jin) Date: Fri Dec 7 13:39:14 2007 Subject: [xmonad] Input Methods and Hangul In-Reply-To: (Max Rabkin's message of "Fri, 7 Dec 2007 09:21:49 +0200") References: <87wsrrfrg2.fsf@columbia.edu> Message-ID: <87sl2efitw.fsf@columbia.edu> "Max Rabkin" writes: > On Dec 6, 2007 11:23 PM, Xiao-Yong Jin wrote: >> And also make sure that the locale is >> correct. > > Does that mean I must set my locale to KO to write Korean? Because I > can't do that: I don't understand enough Korean for my programs to run > in it. But I'm learning, so I like to be able to type in it sometimes. It depends on the input method. Usually it isn't necessary. Setting it to be what_EVER.UTF-8 may work. Otherwise, LANG=what_EVER.UTF-8 and only LC_CTYPE=ko_KR.UTF-8 should definitely do the trick. I use fcitx to input Chinese, and en_US.UTF-8 is enough for it to process all the characters, except some special symbols that depend on particular encoding. Xiao-Yong -- c/* __o/* <\ * (__ */\ < From codesite-noreply at google.com Fri Dec 7 17:13:14 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 17:08:35 2007 Subject: [xmonad] Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver Message-ID: <00c09ffb4bcf0440b98d88275a15219f@google.com> Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #1 by byorgey: Another data point: today, after unlocking the screen, neither the mouse nor the keyboard would respond. I was still able to switch to a virtual terminal and log in, so I could verify that xmonad was still running. I decided to kill xscreensaver, and it caused X to exit as well. At this point I have no idea whether this is an xmonad bug or an xscreensaver bug. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From thomas.adam22 at gmail.com Fri Dec 7 17:22:05 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Fri Dec 7 17:17:29 2007 Subject: [xmonad] Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver In-Reply-To: <00c09ffb4bcf0440b98d88275a15219f@google.com> References: <00c09ffb4bcf0440b98d88275a15219f@google.com> Message-ID: <18071eea0712071422x2430db2fg27e0b122492ad50c@mail.gmail.com> Hi -- On 07/12/2007, codesite-noreply@google.com wrote: > Issue 97: xmonad stops responding to keyboard input after running xscreensaver > http://code.google.com/p/xmonad/issues/detail?id=97 > > Comment #1 by byorgey: > Another data point: today, after unlocking the screen, neither the > mouse nor the > keyboard would respond. I was still able to switch to a virtual > terminal and log in, > so I could verify that xmonad was still running. I decided to kill > xscreensaver, and > it caused X to exit as well. At this point I have no idea whether this > is an xmonad > bug or an xscreensaver bug. I don't think this problem is xscreensaver specific, and I would argue is a red-herring. I too find for no apparent reason that after sometime, Firefox no longer responds to keyboard focus unless it is either moved to the floating layer and retiled or a new window is opened. This will be an issue with Firefox though, and not of XMonad itself. How best to fix it (whether XMonad can send a synthetic event to Firefox or not) is still something I am pondering. -- Thomas Adam From vogt.adam at gmail.com Fri Dec 7 17:32:17 2007 From: vogt.adam at gmail.com (Adam Vogt) Date: Fri Dec 7 17:27:42 2007 Subject: [xmonad] Issue 73 in xmonad: xmonad as a library In-Reply-To: <000fea7b80a70440aaee8fb866ef7e@google.com> References: <000fea7b80a70440aaee8fb866ef7e@google.com> Message-ID: <20071207223217.GA7648@dell> Add to that this effort to bring the manpage up to date: it still had stuff about non-greedy workspace switching and the compiling necessary for reconfiguration. It might be better to be a bit more verbose on configuration, and/or reference the other docs. * On Thursday, December 06 2007, codesite-noreply@google.com wrote: > Issue 73: xmonad as a library > http://code.google.com/p/xmonad/issues/detail?id=73 > > Comment #5 by dons00: > Documentation done. Only thing left is an example, commented-out xmonad.hs > users can > use as a template. -------------- next part -------------- New patches: [update manpage Adam Vogt **20071207221639] { hunk ./man/xmonad.1.in 3 -.TH xmonad 1 "18 April 07" xmonad\-1.0 "xmonad manual" +.TH xmonad 1 "7 December 07" xmonad\-0.5 "xmonad manual" hunk ./man/xmonad.1.in 19 -When running with multiple monitors (Xinerama), each screen has exactly 1 workspace visible. When \fBxmonad\fR starts, workspace 1 is on screen 1, workspace 2 is on screen 2, etc. If you switch to a workspace which is currently visible on another screen, \fBxmonad\fR simply switches focus to that screen. If you switch to a workspace which is *not* visible, \fBxmonad\fR replaces the workspace on the *current* screen with the workspace you selected. +When running with multiple monitors (Xinerama), each screen has exactly 1 workspace visible. mod-{w,e,r} switch the focus between screens, while shift-mod-{w,e,r} move the current window to that screen. When \fBxmonad\fR starts, workspace 1 is on screen 1, workspace 2 is on screen 2, etc. When switching workspaces to one that is already visible, the current and visible workspaces are swapped. hunk ./man/xmonad.1.in 21 -For example, if you have the following configuration: -.RS -.PP -Screen 1: Workspace 2 -.PP -Screen 2: Workspace 5 (current workspace) -.RE -.PP -and you wanted to view workspace 7 on screen 1, you would press: -.RS -.PP -mod-2 (to select workspace 2, and make screen 1 the current screen) -.PP -mod-7 (to select workspace 7) -.RE -.PP -Since switching to the workspace currently visible on a given screen is such a common operation, shortcuts are provided: mod-{w,e,r} switch to the workspace currently visible on screens 1, 2, and 3 respectively. Likewise, shift-mod-{w,e,r} moves the current window to the workspace on that screen. Using these keys, the above example would become mod-w mod-7. hunk ./man/xmonad.1.in 30 -\fBxmonad\fR is customized by creating a custom Config.hs and (re)compiling the source code. After recompiling, 'restart' is used to fork the new version, with changes reflected immediately. +\fBxmonad\fR is customized in ~/.xmonad/xmonad.hs } Context: [Depend on X11>=1.4.0 Spencer Janssen **20071205045945] [Update extra-source-files Spencer Janssen **20071205044421] [Update man location Spencer Janssen **20071205043913] [make Query a MonadIO Lukas Mai **20071128195126] [Add ManageHook to the XMonad metamodule Spencer Janssen **20071127002840] [update todos before release Don Stewart **20071125052720] [Depend on X11 1.4.0 Don Stewart **20071125034012] [add getXMonadDir (2nd try) Lukas Mai **20071121183018] [Add 'and' and 'or' functions to ManageHook. Spencer Janssen **20071121104613] [generalise type of `io' Don Stewart **20071121054407] [Add recompilation forcing, clean up recompile's documentation Spencer Janssen **20071120223614] [recompile does not raise any exceptions Spencer Janssen **20071120215835] [-no-recomp because we're doing our own recompilation checking Spencer Janssen **20071120215744] [pointfree Don Stewart **20071120184016] [clean up fmap overuse with applicatives. more opportunities remain Don Stewart **20071120181743] [ManageHook is a Monoid Spencer Janssen **20071119060820] [No more liftM Spencer Janssen **20071119033120] [Refactor recompile Spencer Janssen **20071119032255] [Trailing space Spencer Janssen **20071119030658] [Generalize recompile to MonadIO Spencer Janssen **20071119030436] [Factor out doubleFork logic Spencer Janssen **20071119030353] [handle case of xmonad binary not existing, when checking recompilation Don Stewart **20071119030057] [Use executeFile directly, rather than the shell, avoiding sh interepeting Don Stewart **20071119025015] [use 'spawn' rather than runProcess, to report errors asynchronously, avoiding zombies Don Stewart *-20071119023712] [use 'spawn' rather than runProcess, to report errors asynchronously, avoiding zombies Don Stewart **20071119023712] [Use xmessage to present a failure message to users when the config file cannot be loaded Don Stewart **20071119022429] [only check xmonad.hs against the xmonad binary, not the .o file (meaning you can remove it if you like) Don Stewart **20071119011528] [Do our own recompilation checking: only launch ghc if the xmonad.hs is newer than its .o file Don Stewart **20071119010759] [reformat export list to fit on the page Don Stewart **20071119003900] [add support for Mac users and their silly case-insensitive filesystems Devin Mullins **20071117024836] [some more tweaks Don Stewart **20071116184227] [more todos: docs Don Stewart **20071116182444] [we need examples for the managehook edsl Don Stewart **20071116182332] [more todos Don Stewart **20071116182033] [polish readme Don Stewart **20071116181931] [more polish for config doc Don Stewart **20071116181640] [tweak .cabal synopsis a little Don Stewart **20071116181245] [Config: small haddock fix Andrea Rossato **20071116113158] [Core: documented XConfig and ScreenDetail Andrea Rossato **20071116112826] [CONFIG, TODO: fix typos "Valery V. Vorotyntsev" **20071115144151 CONFIG: delete trailing whitespace ] [make default ratios in config nicer to look at Lukas Mai **20071112013551] [refactor main, add "recompile" to XMonad.Core Lukas Mai **20071108230933] [comments, reexport Data.Bits Don Stewart **20071114183759] [polish .cabal file. add xmonad@ as the default maintainer Don Stewart **20071114182716] [add lots more text on configuration Don Stewart **20071114182531] [refactor trace. Don Stewart **20071114034109] [clarify comment at top of Config.hs Devin Mullins **20071111191304 There appears to be some confusion -- several people have wanted to edit Config.hs as was done in the past. This comment probably won't stop that, but it's a start. ] [avoid Data.Ratio and % operator in XMonad.Config David Roundy **20071111183708 I think this'll make Config.hs more friendly as a template for folks to modify. ] [remove obviated (and confusing) comments Devin Mullins **20071111055047] [XMonad.Main uses FlexibleContexts Spencer Janssen **20071111214528] [hide existential Layout (mostly) from user API. David Roundy **20071111003055] [Depend on X11 1.3.0.20071111 Don Stewart **20071111200932] [update README some more Don Stewart **20071109181203] [we depend on Cabal 1.2.0 or newer Don Stewart **20071109155934] [Generalize several functions to MonadIO Spencer Janssen **20071109064214] [Docs for ManageHook Spencer Janssen **20071109031810] [New ManageHook system Spencer Janssen **20071109024722] [Generalize the type of whenJust Spencer Janssen **20071107062126] [maybe False (const True) -> isJust. spotted by shachaf Don Stewart **20071108003539] [typo Don Stewart **20071108000259] [imports not needed in example now Don Stewart **20071107032346] [Provide top level XMonad.hs export module Don Stewart **20071107030617] [point to where defns for config stuff can be found Don Stewart **20071107020801] [Fix haddock comment Spencer Janssen **20071107030510] [fall back to previous ~/.xmonad/xmonad if recompilation fails Lukas Mai **20071107015309] [recommend --user Don Stewart **20071106221004] [add CONFIG with details of how to configure Don Stewart **20071105040741] [Run only 50 tests per property, decreases test time by 10 seconds on my system Spencer Janssen **20071105064944] [Remove stale comment Spencer Janssen **20071105063731] [Use Cabal's optimization flags rather than -O Spencer Janssen **20071105061759] [Build the whole thing in the test hook Spencer Janssen **20071105061615] [-Werror Spencer Janssen **20071105060326] [Remove superfluous 'extensions:' field Spencer Janssen **20071105034515] [Use configurations in xmonad.cabal Spencer Janssen **20071105033428] [~/.xmonad/Main.hs is now ~/.xmonad/xmonad.hs ! Don Stewart **20071105032655] [makeMain -> xmonad Don Stewart **20071105031203] [-Wall police Don Stewart **20071105022202] [remember to compile the xmonad library also with the usual ghc-optoins Don Stewart **20071105022127] [EventLoop -> Core, DefaultConfig -> Config Don Stewart **20071105021705] [clean up DefaultConfig.hs Don Stewart **20071105021142] [clean up some weird formatting/overboard strictness annotations Don Stewart **20071105011400] [Update pragmas for GHC 6.8 compatibility Spencer Janssen **20071104215507] [Use the layout and workspaces values from the actual configuration used Spencer Janssen **20071104020320] [Float handler out of makeMain, make keys and mouseBindings dependent on XConfig for easy modMask switching Spencer Janssen **20071102025924] [We can't rely on the executable name, because it may be 'Main' Spencer Janssen **20071101205057] [Get defaultGaps from the current config, not the default one Spencer Janssen **20071101205025] [exposed-modules Spencer Janssen **20071101193331] [Hierarchify Spencer Janssen **20071101180846] [Main.hs -> DefaultConfig.hs, add new Main.hs with 'buildLaunch' Spencer Janssen **20071101175749] [Layouts.Choose: handle ReleaseResources Spencer Janssen **20071101152302] [Layouts.Choose: send Hide to non-selected layout Spencer Janssen **20071101151147] [Export mirrorRect Spencer Janssen **20071101085631] [Only export main from Main Spencer Janssen **20071101082326] [Add readsLayout, remove the existential from XConfig Spencer Janssen **20071101082155] [Delete Main.hs-boot! Spencer Janssen **20071101080045] [Remove manageHook from Main.hs-boot Spencer Janssen **20071101075308] [Remove workspaces from Main.hs-boot Spencer Janssen **20071101074556] [-Wall police Spencer Janssen **20071101074411] [Eliminate defaultTerminal Spencer Janssen **20071101073147] [Store user configuration in XConf Spencer Janssen **20071101072308] [This is a massive update, here's what has changed: Spencer Janssen **20071101064318 * Read is no longer a superclass of Layout * All of the core layouts have moved to the new Layouts.hs module * Select has been replaced by the new statically typed Choose combinator, which is heavily based on David Roundy's NewSelect proposal for XMonadContrib. Consequently: - Rather than a list of choosable layouts, we use the ||| combinator to combine several layouts into a single switchable layout - We've lost the capability to JumpToLayout and PrevLayout. Both can be added with some effort ] [cleaner version of main/config inversion. David Roundy **20071029184823] [make setLayout a bit more inclusive. David Roundy **20071024231250] [make xmonad work with inverted main/config. David Roundy **20071018170058] [sketch of config/main inversion. David Roundy **20071018164230] [more precise X11 version required Don Stewart **20071031203241] [tweaks to todo Don Stewart **20071031164618] [HEADS UP: remove X11-extras dependency, depend on X11 >= 1.3.0 Don Stewart **20071030220824 The X11-extras library has been merged into the larger X11 library, so we now drop the dependency on X11-extras, and instead build against the new X11 library. If you apply this patch you must build and install X11-1.3.0 or greater first, http://hackage.haskell.org/cgi-bin/hackage-scripts/package/X11-1.3.0 You can also go ahead and wipe X11-extras from GHC's memory, (for ghci to work out of the box with the testsuite) $ ghc-pkg unregister X11-extras $ ghc-pkg unregister --user X11-extras ] [New windows start in the iconic state Spencer Janssen **20071028063949] [add text on using xprop to find client names Don Stewart **20071027163031] [add text reminding people to run mod-shift-space Don Stewart **20071026225228] [StackSet.hs: (insertUp): remove comments about new window being made master window, since that clearly isn't true. Brent Yorgey **20071022210856] [Replace 'findIndex' with 'findTag', which more accurately describes what the function does. Brent Yorgey **20071022204105 I realize this is a big change, but the name 'findIndex' was confusing for me, since I expected it to return some sort of integer. What it actually does, of course, is return a workspace tag, which might be more general than an index. Of course, this change breaks several contrib modules; I'll submit a patch to make the change there as well. ] [StackSet.hs: (ensureTags): elaborate into a more descriptive comment. Brent Yorgey **20071022202212] [StackSet.hs: remove dead code. Brent Yorgey **20071022192636] [StackSet.hs: (differentiate): 'Texture' doesn't mean anything to me; replace with a more descriptive comment. Brent Yorgey **20071022191333] [StackSet.hs: (new): better comment; 'm' is not an integer, it is a list of screen descriptions. Brent Yorgey **20071022183411] [StackSet.hs: align some comments Brent Yorgey **20071022161601] [StackSet.hs: small grammar fix and better flow in comment Brent Yorgey **20071022160858] [StackSet.hs: better comments regarding hidden/visible workspace tracking for Xinerama Brent Yorgey **20071022160239 I'm not 100% sure that I understand what's going on here, but it seems as though the comment still described an older state of affairs. I don't see any Map Workspace Screen keeping track of visible workspaces. ] [Add Config.terminal Spencer Janssen **20071024105354] [explain that you need ghc as well Don Stewart **20071024030520] [xmonad, not XMonad Spencer Janssen **20071023234900] [STYLE: enlarge on existing principles gwern0@gmail.com**20071023225225 Comments: the -Wall thing was just trying to say -Wall -Werror should work. The license thing was too narrow - or are my public domain contributions unwelcome because they are not BSD-3? I think comments are most important for exported functions users will use; it isn't so important for helper functions (used only in the module) to be very well-documented, right? ] [start on style guide Don Stewart **20071023221422] [Operations.hs: flip maybe id is fromMaybe Eric Mertens **20071018231418] [Deobfuscate Tall layout Eric Mertens **20071018231329] [setInitialProperties after placing windows Spencer Janssen *-20071019201310] [setInitialProperties after placing windows Spencer Janssen **20071019201310] [Ignore borders in the stored RationalRects of floating windows. Spencer Janssen *-20071019063922 Also, add 'floatWindow' which computes the actual Rectangle for that window, including border. ] [Only assign workspace keys up to xK_9. Related to bug #63 Spencer Janssen **20071019083746] [Ignore borders in the stored RationalRects of floating windows. Spencer Janssen **20071019063922 Also, add 'floatWindow' which computes the actual Rectangle for that window, including border. ] [I prefer fmap over liftM Spencer Janssen **20071019063104] [change 0/1/3 to named states, per X11-extras darcs head Devin Mullins **20071018021651] [remove StackOrNot type synonymn. David Roundy **20071017201406] [Operations.hs: make use of notElem and notMember Eric Mertens **20071017174357] [TAG 0.4 Spencer Janssen **20071016215343] Patch bundle hash: 2b89ac00957d18a41ae0440f5cc05f8e82f43f70 From codesite-noreply at google.com Fri Dec 7 21:02:12 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 20:57:32 2007 Subject: [xmonad] Issue 47 in xmonad: Allow selection of the floating layout in Config.hs Message-ID: <00c09ffb4bcf0440bcc0640ecc157de8@google.com> Issue 47: Allow selection of the floating layout in Config.hs http://code.google.com/p/xmonad/issues/detail?id=47 Comment #1 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Labels: -Type-Defect Type-Enhancement -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:06:20 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:01:40 2007 Subject: [xmonad] Issue 51 in xmonad: amsn crashes when a contact tries to open a dialog Message-ID: <00163600cf970440bccf2e3bba157e38@google.com> Issue 51: amsn crashes when a contact tries to open a dialog http://code.google.com/p/xmonad/issues/detail?id=51 Comment #1 by SpencerJanssen: As far as we know, this problem remains. However, we can't do anything without more information. Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:10:21 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:05:42 2007 Subject: [xmonad] Issue 46 in xmonad: xmonad's output (logHook) needs to be separated from output from client programs Message-ID: <00163600cf970440bcdd8ca8e9157ee9@google.com> Issue 46: xmonad's output (logHook) needs to be separated from output from client programs http://code.google.com/p/xmonad/issues/detail?id=46 Comment #2 by SpencerJanssen: This is fixed for 0.5, see spawnPipe et al -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:14:23 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:09:44 2007 Subject: [xmonad] Issue 46 in xmonad: xmonad's output (logHook) needs to be separated from output from client programs Message-ID: <00c09ffb4bcf0440bcebf1e5a4157fed@google.com> Issue 46: xmonad's output (logHook) needs to be separated from output from client programs http://code.google.com/p/xmonad/issues/detail?id=46 Comment #3 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:18:26 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:13:46 2007 Subject: [xmonad] Issue 54 in xmonad: Composable manageHooks interface Message-ID: <00c09ffb53810440bcfa69c2f31586f0@google.com> Issue 54: Composable manageHooks interface http://code.google.com/p/xmonad/issues/detail?id=54 Comment #5 by SpencerJanssen: Done in 0.5, see XMonad.ManageHooks. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:22:28 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:17:47 2007 Subject: [xmonad] Issue 54 in xmonad: Composable manageHooks interface Message-ID: <00c09ff7928c0440bd08d95bad1581dc@google.com> Issue 54: Composable manageHooks interface http://code.google.com/p/xmonad/issues/detail?id=54 Comment #6 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:26:29 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:21:49 2007 Subject: [xmonad] Issue 74 in xmonad: cinellera does not launch (normally) Message-ID: <00c09ff7928c0440bd1736488e15825c@google.com> Issue 74: cinellera does not launch (normally) http://code.google.com/p/xmonad/issues/detail?id=74 Comment #1 by SpencerJanssen: I believe this is a cinelerra bug, WontFix until demonstrated otherwise. Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:30:31 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:25:51 2007 Subject: [xmonad] Issue 75 in xmonad: float mode and automatic workspace placement don't work together Message-ID: <00163600ca7f0440bd259f3de01581ad@google.com> Issue 75: float mode and automatic workspace placement don't work together http://code.google.com/p/xmonad/issues/detail?id=75 Comment #1 by SpencerJanssen: Fixed in 0.5 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:34:32 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:29:52 2007 Subject: [xmonad] Issue 75 in xmonad: float mode and automatic workspace placement don't work together Message-ID: <00c09ffb4bcf0440bd33fc614515832b@google.com> Issue 75: float mode and automatic workspace placement don't work together http://code.google.com/p/xmonad/issues/detail?id=75 Comment #2 by SpencerJanssen: (No comment was entered for this change.) Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Fri Dec 7 21:38:33 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Fri Dec 7 21:33:53 2007 Subject: [xmonad] Issue 71 in xmonad: Problems with initial size of floating windows Message-ID: <00c09ffb53810440bd425fc23f158a1a@google.com> Issue 71: Problems with initial size of floating windows http://code.google.com/p/xmonad/issues/detail?id=71 Comment #1 by SpencerJanssen: Fixed. Issue attribute updates: Status: Fixed -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From andrew at swclan.homelinux.org Fri Dec 7 22:27:36 2007 From: andrew at swclan.homelinux.org (Andrew Sackville-West) Date: Fri Dec 7 22:23:13 2007 Subject: [xmonad] emacs -nw and xmonad key bindings Message-ID: <20071208032735.GA7681@localhost.localdomain> Just posting this up in case anyone comes looking for it. I use emacs -nw and xmonad together. It took me some trial and error to figure this out. I don't know if it applies to the gui-fied emacs. I have an IBM Model M keyboard (clickey clickey clickey), at 101 keys (no win key, and whatnot). The following incantation will get you a Left_Alt key that is recognised by emacs and a Right_Alt key recognised by xmonad. in Config.hs modMask = mod3Mask to assign the mod3 key as the key to control xmonad. In pc101 and pc105 (others?) XkbModel, XkbLayout "us", both Alt keys are assigned to mod1. You can check this with xmodmap which will show the current mappings. execute the following xmodmap expressions add mod1 = Alt_L (* see below) remove mod1 = Alt_R add mod1 = Alt_R you can either do these as individual `xmodmap -e 'expression'` instances or put them in a file and run `xmodmap file` I do it in my .xinitrc and it gives me control of both xmonad using Alt_R and emacs using Alt_L. Hope this helps someone. A * if you look at the output from xmodmap, there is already an instance of Alt_L attached to mod1. But it you run this 'add', you'll get a second one with a different keycode. I don't know why this is, but it's required to get emacs to recognize the key. -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071207/e12ea5a7/attachment.bin From andrew at swclan.homelinux.org Fri Dec 7 22:35:09 2007 From: andrew at swclan.homelinux.org (Andrew Sackville-West) Date: Fri Dec 7 22:30:44 2007 Subject: [xmonad] emacs -nw and xmonad key bindings In-Reply-To: <20071208032735.GA7681@localhost.localdomain> References: <20071208032735.GA7681@localhost.localdomain> Message-ID: <20071208033509.GB7681@localhost.localdomain> On Fri, Dec 07, 2007 at 07:27:36PM -0800, Andrew Sackville-West wrote: > Just posting this up in case anyone comes looking for it. well crap. That didn't work. for some reason. now it seems I have to *remove* Alt_L altogether from mod1 with remove mod1 = Alt_L replacing the add mod1 = Alt_L and keeping the rest intact seems to have it. for now. A -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071207/3ae16c12/attachment.bin From xj2106 at columbia.edu Sat Dec 8 14:02:04 2007 From: xj2106 at columbia.edu (Xiao-Yong Jin) Date: Sat Dec 8 13:59:38 2007 Subject: [xmonad] Issue 51 in xmonad: amsn crashes when a contact tries to open a dialog In-Reply-To: <00163600cf970440bccf2e3bba157e38@google.com> (codesite-noreply@google.com's message of "Fri, 07 Dec 2007 18:06:20 -0800") References: <00163600cf970440bccf2e3bba157e38@google.com> Message-ID: <87fxydf1sj.fsf@columbia.edu> codesite-noreply@google.com writes: > Issue 51: amsn crashes when a contact tries to open a dialog > http://code.google.com/p/xmonad/issues/detail?id=51 > > Comment #1 by SpencerJanssen: > As far as we know, this problem remains. However, we can't do anything > without more > information. Amsn users should look through output from amsn. Most probably the crash is caused by something similar to the one described in the FAQ of amsn: http://www.amsn-project.net/wiki/FAQ#As_soon_as_I_try_to_log_on_or_change_aMSN.27s_language.2C_it_crashes_with_the_following_message:_X_Error_of_failed_request:__BadValue_.28integer_parameter_out_of_range_for_operation.29.2C_Major_opcode_of_failed_request:__45_.28X_OpenFont.29 I have encountered some different behaviours. But I would take it as a problem that lies within TCL or X11 libs. Xiao-Yong -- c/* __o/* <\ * (__ */\ < From dons at galois.com Sat Dec 8 18:00:58 2007 From: dons at galois.com (Don Stewart) Date: Sat Dec 8 17:56:23 2007 Subject: [xmonad] xmonad, and trends in the tiling wm market Message-ID: <20071208230058.GH4913@scytale.galois.com> We've not much information on what's happening with tiling wms. One source of info is the debian package system's popularity contest: if a package is in debian, we get to see a snapshot of trends. Here's a little analysis of what's been happening with the tiling wms in 2007: http://galois.com/~dons/images/tiling-window-managers.png Summary: * ion continues long term decline * ratpoison was in a place to take advantage of ion controversy * wmii and dwm continue long term growth * in late 07, the two new tiling window managers, xmonad and awesome, begin eating away at ion, ratpoison and dwm users * larswm and stumpwm are static For xmonad my hope is that improved packaging, and the ease of adding extensions, to appear in this weekend's release of xmonad 0.5 will lead to further growth. Along with xmonad's technical features over the competition, I hope to see continued growth in the coming year. We're working hard at ensuring this is the best tiling wm! Our challenge is to make the cost of installing a Haskell toolchain easier, though, so its cheaper to experiment with xmonad. This comes down to improved ghc packaging on each distro. -- Don From thomas.adam22 at gmail.com Sat Dec 8 18:15:39 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Sat Dec 8 18:10:58 2007 Subject: [xmonad] xmonad, and trends in the tiling wm market In-Reply-To: <20071208230058.GH4913@scytale.galois.com> References: <20071208230058.GH4913@scytale.galois.com> Message-ID: <18071eea0712081515r48944614o9840e4b66966e244@mail.gmail.com> Hello -- On 08/12/2007, Don Stewart wrote: > We've not much information on what's happening with tiling wms. One > source of info is the debian package system's popularity contest: if a > package is in debian, we get to see a snapshot of trends. Be careful with that -- the popularity contest is slightly hit-and-miss and might not accurately reflect xmonad's use. What is it you're after though? A comparison of how many users are *potentially* (that's the operative word here) are using xmonad? How xmonad compares in development to other tiling WMs? Whether or not people use it if the moon is waxing as opposed to it being a Tuesday and the local store run out of meatloaf again? In my mind, tracking something's use is best determined through feedback and nothing else. I've watched xmonad grow for a long time, and it's quite impressive; much quicker than a lot of other WMs that have sprung up. But it's rather late to the party in many respects; what sets it apart from other WMs is not only the language it's written in (something of a triumph I'm sure, but not something I care about frankly), but also its operation of working; it's still fundamentally different from dwm for instance. > Here's a little analysis of what's been happening with the tiling wms > in 2007: > > http://galois.com/~dons/images/tiling-window-managers.png > > Summary: > * ion continues long term decline Yes, understandable. > * ratpoison was in a place to take advantage of ion controversy Maybe, but then ratpoison's primary goal was to augment GNU screen's way of working to more than just a terminal, and it's done that successfully. It was certainly one of the first WMs AFAIAC to set the trend for the way other tiling window managers operate. > Our challenge is to make the cost of installing a Haskell toolchain > easier, though, so its cheaper to experiment with xmonad. This comes > down to improved ghc packaging on each distro. Yes -- there needs to be a more streamlined way of ensuring this, but like the way Ruby has been packaged in Debian for instance, it can end up a mess if not handled correctly. Certainly having Cabal 1.2 in distros for the upcoming 0.5 release is my main concern. -- Thomas Adam From dons at galois.com Sat Dec 8 18:22:20 2007 From: dons at galois.com (Don Stewart) Date: Sat Dec 8 18:17:41 2007 Subject: [xmonad] xmonad, and trends in the tiling wm market In-Reply-To: <18071eea0712081515r48944614o9840e4b66966e244@mail.gmail.com> References: <20071208230058.GH4913@scytale.galois.com> <18071eea0712081515r48944614o9840e4b66966e244@mail.gmail.com> Message-ID: <20071208232220.GI4913@scytale.galois.com> thomas.adam22: > Hello -- > > On 08/12/2007, Don Stewart wrote: > > We've not much information on what's happening with tiling wms. One > > source of info is the debian package system's popularity contest: if a > > package is in debian, we get to see a snapshot of trends. > > Be careful with that -- the popularity contest is slightly > hit-and-miss and might not accurately reflect xmonad's use. What is > it you're after though? A comparison of how many users are > *potentially* (that's the operative word here) are using xmonad? How > xmonad compares in development to other tiling WMs? Whether or not > people use it if the moon is waxing as opposed to it being a Tuesday > and the local store run out of meatloaf again? Right. It's hard to read too much global information into the debian case, since it depends so much on package details on that system. > In my mind, tracking something's use is best determined through > feedback and nothing else. I've watched xmonad grow for a long time, Quite so. The mailing list and irc channel have continued to grow, for example, which might be better indicators. > and it's quite impressive; much quicker than a lot of other WMs that > have sprung up. But it's rather late to the party in many respects; > what sets it apart from other WMs is not only the language it's > written in (something of a triumph I'm sure, but not something I care Indeed, we want to ensure that's not an issue. The language should only matter in that we expect long term benefits in speed of development, and safety, that should be the main result for language choice. > about frankly), but also its operation of working; it's still > fundamentally different from dwm for instance. Oh, how so? I guess it has come a long way -- particular wrt. extensibility. -- Don From tim.thelion at gmail.com Sat Dec 8 18:28:15 2007 From: tim.thelion at gmail.com (Tim hobbs) Date: Sat Dec 8 18:23:34 2007 Subject: [xmonad] Patch: Magnifier custom zoom ratios Message-ID: <650efde80712081528t1611d598ydc4f11f3c78eb822@mail.gmail.com> This just adds a function to magnifier that takes a custom zoom ratio. It is to be applied after the release as it's just a feature. -- - Tim tim.thelion@gmail.com -------------- next part -------------- A non-text attachment was scrubbed... Name: magnifier.patch Type: text/x-diff Size: 54823 bytes Desc: not available Url : http://www.haskell.org/pipermail/xmonad/attachments/20071208/9d027975/magnifier-0001.bin From thomas.adam22 at gmail.com Sat Dec 8 18:30:31 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Sat Dec 8 18:25:49 2007 Subject: [xmonad] xmonad, and trends in the tiling wm market In-Reply-To: <20071208232220.GI4913@scytale.galois.com> References: <20071208230058.GH4913@scytale.galois.com> <18071eea0712081515r48944614o9840e4b66966e244@mail.gmail.com> <20071208232220.GI4913@scytale.galois.com> Message-ID: <18071eea0712081530w7d5caadfy512fbf5328d5d933@mail.gmail.com> Hello -- On 08/12/2007, Don Stewart wrote: > Oh, how so? I guess it has come a long way -- particular wrt. > extensibility. Yes, that's all I meant. :) xmonad is the only WM I know where almost all of its functionality relies on contrib libraries. That's a very impressive design decision and has allowed for great extensibility. -- Thomas Adam From codesite-noreply at google.com Sat Dec 8 21:16:20 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sat Dec 8 21:11:37 2007 Subject: [xmonad] Issue 96 in xmonad: certain dialogs get dropped in gnucash Message-ID: <00c09f90f58f0440d110bd43b976664a@google.com> Issue 96: certain dialogs get dropped in gnucash http://code.google.com/p/xmonad/issues/detail?id=96 Comment #1 by jcreigh: This is definitely an xmonad bug, as the problem does not occur if Gnucash windows are ignored (with, eg, className =? "Gnucash" --> doIgnore) Issue attribute updates: Status: Started -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From thomas.adam22 at gmail.com Sun Dec 9 05:07:34 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Sun Dec 9 05:02:51 2007 Subject: [xmonad] Issue 96 in xmonad: certain dialogs get dropped in gnucash In-Reply-To: <00c09f90f58f0440d110bd43b976664a@google.com> References: <00c09f90f58f0440d110bd43b976664a@google.com> Message-ID: <18071eea0712090207y7568bfa4s4a7c8528127d7635@mail.gmail.com> Hi -- On 09/12/2007, codesite-noreply@google.com wrote: > Issue 96: certain dialogs get dropped in gnucash > http://code.google.com/p/xmonad/issues/detail?id=96 > > Comment #1 by jcreigh: > This is definitely an xmonad bug, as the problem does not occur if > Gnucash windows > are ignored (with, eg, className =? "Gnucash" --> doIgnore) I bet I know what this bug is (I;m assuming transient windows here): The window is being mapped and unmapped. If you were to use something like xscope then you might see that: a) Application sends a mapRequest. a1) Before xmonad has a chance to do that, the application asks to be put in the WithDrawn state (via a synthetic UnmapNotify event). b) The window is mapped. c) GNUCash sends a MapRequest. d) Another UnmapNotify request is sent and the window is UnMapped. e) The MapRequest from (c) is handled and a real UnMapNotify request is issued causing the window it close, never being mapped again. I'm guessing this is what's happening, but I don't run GnuCash. -- Thomas Adam From codesite-noreply at google.com Sun Dec 9 05:11:27 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 05:06:44 2007 Subject: [xmonad] Issue 96 in xmonad: certain dialogs get dropped in gnucash Message-ID: <00163600d06e0440d7b3f2230e180429@google.com> Issue 96: certain dialogs get dropped in gnucash http://code.google.com/p/xmonad/issues/detail?id=96 Comment #2 by thomas.adam22: I bet I know what this bug is (I'm assuming transient windows here): The window is being mapped and unmapped. If you were to use something like xscope then you might see that: a) Application sends a mapRequest. a1) Before xmonad has a chance to do that, the application asks to be put in the WithDrawn state (via a synthetic UnmapNotify event). b) The window is mapped. c) GNUCash sends a MapRequest. d) Another UnmapNotify request is sent and the window is UnMapped. e) The MapRequest from (c) is handled and a real UnMapNotify request is issued causing the window it close, never being mapped again. I'm guessing this is what's happening, but I don't run GnuCash. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 06:30:04 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 06:25:21 2007 Subject: [xmonad] Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver Message-ID: <00c09ffb53810440d8cd19d1df182cf7@google.com> Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #2 by thomas.adam22: I don't think this problem is xscreensaver specific, and I would argue is a red-herring. I too find for no apparent reason that after sometime, Firefox no longer responds to keyboard focus unless it is either moved to the floating layer and retiled or a new window is opened. This will be an issue with Firefox though, and not of XMonad itself. How best to fix it (whether XMonad can send a synthetic event to Firefox or not) is still something I am pondering. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From mailing_list at istitutocolli.org Sun Dec 9 11:19:00 2007 From: mailing_list at istitutocolli.org (Andrea Rossato) Date: Sun Dec 9 11:14:53 2007 Subject: [xmonad] darcs patch: StackSet: some haddock tuning Message-ID: <200712091619.lB9GJ09m018081@laptop.nowhere.net> Sun Dec 9 17:15:25 CET 2007 Andrea Rossato * StackSet: some haddock tuning -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 18075 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20071209/98d324f5/attachment-0001.bin From codesite-noreply at google.com Sun Dec 9 14:31:52 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 14:27:07 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies Message-ID: <00163600d8730440df8822194018e114@google.com> Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 New issue report by dons00: Now we have reconfigure without recompilation, we can consider non-Haskell mechanisms for configuration (such as a simple text format, or Xresources, or environment variables). A good choice here should ease adoption -- as users can get good results without needing haskell. Issue attributes: Status: Accepted Owner: dons00 Labels: Type-Enhancement Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 15:19:24 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 15:14:39 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies Message-ID: <00163600c9890440e0321bb87418f0f6@google.com> Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #1 by dons00: An example from Thomas. 1 -- Sample idea of what a non-xmonad/haskell config file might look like. 2 3 -- Set the modkey. 4 modkey = mod4 5 6 myConfig = { 7 borderWidth = 3 8 terminal = "urxvt +sb ...." 9 workspaces = "A", "B", "C", "D" 10 gaps = 15 0 0 0 11 modMask = modkey 12 .... 13 } 14 15 -- Layouts 16 layouts = tiled, mirror tiled, full (noBorders) 17 18 -- Keys 19 key a (shift) Kill 20 key right (control) rotview true 21 22 -- Mouse 23 mouse 1 focusNextWindow 24 25 -- Styles 26 Style (classname=Skype | resource=skype) StartWS A, Float 27 Style (classname=XClock) Float -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 15:28:36 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 15:23:51 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies Message-ID: <001485f9a4ae0440e053015304fab18@google.com> Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #2 by thomas.adam22: Thanks Don for that... My intention behind this proposed syntax is that is is sufficiently removed from haskell for it to be generic (i.e., does not enforce Haskell's syntax on the user), but close enough for it to be haskell so that some parser can be written. If that makes sense. Someone on IRC asked what they would do to make a ""global"" key-binding without the modifier -- if one looks at line 19, then that might be represented as: key (nomod) a kill (Potentially stupid in this example, but you get the point.) Again, line 26 (which is an abstract representation of what ManageHook might become, says that: "If a window has a class of 'skype' OR (|) a resource of 'skype' then move it to the WorkSpace of 'A' and put it in the floating layer". Hopefully that helps to clarify things a little. Kindly, Thomas Adam -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From xj2106 at columbia.edu Sun Dec 9 16:35:43 2007 From: xj2106 at columbia.edu (Xiao-Yong Jin) Date: Sun Dec 9 16:33:22 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies In-Reply-To: <00163600c9890440e0321bb87418f0f6@google.com> (codesite-noreply@google.com's message of "Sun, 09 Dec 2007 12:19:24 -0800") References: <00163600c9890440e0321bb87418f0f6@google.com> Message-ID: <877ijnft5c.fsf@columbia.edu> codesite-noreply@google.com writes: > Issue 98: Conventional configuration strategies > http://code.google.com/p/xmonad/issues/detail?id=98 > > Comment #1 by dons00: > An example from Thomas. > > > 1 -- Sample idea of what a non-xmonad/haskell config file might look like. > 2 > 3 -- Set the modkey. > 4 modkey = mod4 > 5 > 6 myConfig = { > 7 borderWidth = 3 > 8 terminal = "urxvt +sb ...." > 9 workspaces = "A", "B", "C", "D" > 10 gaps = 15 0 0 0 > 11 modMask = modkey > 12 .... > 13 } > 14 > 15 -- Layouts > 16 layouts = tiled, mirror tiled, full (noBorders) > 17 > 18 -- Keys > 19 key a (shift) Kill > 20 key right (control) rotview true > 21 > 22 -- Mouse > 23 mouse 1 focusNextWindow > 24 > 25 -- Styles > 26 Style (classname=Skype | resource=skype) StartWS A, Float > 27 Style (classname=XClock) Float I am not sure what you mean by the word `conventional'. It sounds awkward to give up a well formed syntax with a yet-to-be-designed configuration scheme. And at the mean time, full screen mplayer still needs me to move it up and left one pixel respectively to achieve _full screen_. I think it largely depends on what you developers think which way xmonad is going to follow. Just look at those nearly full powered window managers out there. You have to admit that they all have very complicated configuration file syntax. Let's take an example of FVWM, which is still my favourite non-tiled window manager. Its man page has 9048 lines to educate people how the configuration file could be written, and that still not includes all other separate modules. Do you want users of xmonad to learn another strange configuration syntax? On the contrary, please look at Sawfish. I am glad some people finally continued the work, which had been halted for a couple of years. Think of it, what kind of configuration syntax could you imagine to achieve the flexibility, readability and usability given by a Lisp-based scripting language it uses? `Haskell' is my answer. What is yours? How /conventional/ the configuration strategy is really restricts how powerful and configurable xmonad is. Please think twice before you stepping upon the endless journey of implementing a new language that could be used to configure a powerful-WM-to-be. My two cents, Xiao-Yong -- c/* __o/* <\ * (__ */\ < From thomas.adam22 at gmail.com Sun Dec 9 16:46:08 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Sun Dec 9 16:41:25 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies In-Reply-To: <877ijnft5c.fsf@columbia.edu> References: <00163600c9890440e0321bb87418f0f6@google.com> <877ijnft5c.fsf@columbia.edu> Message-ID: <18071eea0712091346y2ee874c6k8debd010d680df15@mail.gmail.com> Hi -- On 09/12/2007, Xiao-Yong Jin wrote: > yet-to-be-designed configuration scheme. And at the mean > time, full screen mplayer still needs me to move it up and > left one pixel respectively to achieve _full screen_. OK, that's not even tangential as it is off-topic. > I think it largely depends on what you developers think > which way xmonad is going to follow. Just look at those > nearly full powered window managers out there. You have to > admit that they all have very complicated configuration file > syntax. Let's take an example of FVWM, which is still my > favourite non-tiled window manager. Its man page has 9048 > lines to educate people how the configuration file could be > written, and that still not includes all other separate > modules. Given I'm an expert at FVWM, I can tell you it's power is not about config files as it is more about the sheer number options it has. The two aren't even comparable here. > Do you want users of xmonad to learn another > strange configuration syntax? On the contrary, please look Strange? No? Enforced? No. There would be nothing stopping you from writing out the best haskell you could muster as an xmonad config file; it's just in many people's eyes enforcing a -language- onto people is a tall order, and yes, there is a huge difference between a config file and a language. -- Thomas Adam From codesite-noreply at google.com Sun Dec 9 17:56:43 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 17:51:57 2007 Subject: [xmonad] Issue 73 in xmonad: xmonad as a library Message-ID: <00163600ca7f0440e264ba50c7191c0d@google.com> Issue 73: xmonad as a library http://code.google.com/p/xmonad/issues/detail?id=73 Comment #6 by dons00: Done! Find template xmonad.hs file here: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_Config.hs Issue attribute updates: Status: Verified -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 19:20:36 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 19:15:50 2007 Subject: [xmonad] Issue 82 in xmonad: Gap should be on by default Message-ID: <00163600ca7f0440e390b98bfb193b41@google.com> Issue 82: Gap should be on by default http://code.google.com/p/xmonad/issues/detail?id=82 Comment #2 by dons00: Bumped. Small issue. Issue attribute updates: Labels: -Milestone-Release0.5 Milestone-Release0.6 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 19:24:37 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 19:19:52 2007 Subject: [xmonad] Issue 68 in xmonad: Extension request: banish mouse pointer Message-ID: <00163600c9890440e39f1bda6a1941be@google.com> Issue 68: Extension request: banish mouse pointer http://code.google.com/p/xmonad/issues/detail?id=68 Comment #5 by dons00: If someone is interested, write a mouse banishing extension. Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Sun Dec 9 19:28:39 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Sun Dec 9 19:23:53 2007 Subject: [xmonad] Issue 98 in xmonad: Conventional configuration strategies Message-ID: <00163600d06e0440e3ad7a0202194b22@google.com> Issue 98: Conventional configuration strategies http://code.google.com/p/xmonad/issues/detail?id=98 Comment #3 by dons00: We now have a config template: http://haskell.org/haskellwiki/Xmonad/Config_archive/Template_Config.hs That is farrly non-Haskell. And we will continue to improve EDSL support for configuration. It is not a priority though to develop a Haskell-lite syntax in front of xmonad. Issue attribute updates: Status: WontFix -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From dons at galois.com Sun Dec 9 19:32:24 2007 From: dons at galois.com (Don Stewart) Date: Sun Dec 9 23:02:46 2007 Subject: [xmonad] ANNOUNCE: xmonad 0.5: a tiling window manager Message-ID: <20071210003224.GA23988@scytale.galois.com> The xmonad dev team is pleased to announce the 0.5 release of xmonad! http://xmonad.org xmonad is a tiling window manager for X. Windows are arranged automatically to tile the screen without gaps or overlap, maximising screen use. Window manager features are accessible from the keyboard: a mouse is optional. xmonad is extensible in Haskell, allowing for powerful customisation. Custom layout algorithms, key bindings and other extensions may be written by the user in config files. Layouts are applied dynamically, and different layouts may be used on each workspace. Xinerama is fully supported, allowing windows to be tiled on several physical screens. Features: * Very stable, fast, small and simple. * Automatic window tiling and management * First class keyboard support: a mouse is unnecessary * Full support for tiling windows on multi-head displays * Full support for floating windows * XRandR support to rotate, add or remove monitors * Per-workspace layout algorithms * Per-screens custom status bars * Easy, powerful customisation and reconfiguration in Haskell * Large extension library * Extensive documentation and support for hacking Get it! More information, screenshots, documentation, tutorials and community resources are available from the xmonad home page: http://xmonad.org The 0.5 release, and its dependencies, are available from hackage.haskell.org, here: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/xmonad **The headlines** xmonad 0.5 is a major new release of xmonad, allowing, for the first time, dynamic extension in Haskell without requiring recompilation. Extension and configuration of xmonad is now faster, simpler, and more flexible. All configuration is done via the ~/.xmonad/xmonad.hs file. Example config files and screenshots are available on the wiki: http://haskell.org/haskellwiki/Xmonad/Config_archive This marks the final break from its dwm origins. As a result, xmonad is now also much easier to package, distribute and extend, as recompilation of xmonad is not required to extend it. New features: * xmonad is now a library, as is the collection of xmonad extensions * xmonad is configured by editing ~/.xmonad/xmonad.hs * simpler layout hooks type and interface * small EDSL for writing window management rules * support for ghc 6.8.x * xmonad now requires Cabal 1.2 or newer * small bug fixes Extensions: xmonad comes with a huge library of extensions (now more than 5 times the size of xmonad), contributed by viewers like you. Extensions enable pretty much arbitrary window manager behaviour to be implemented by users, in Haskell, in the config files. Examples include: * ion-like window tabs * status bar support * X property and hints support * altnerative layout algorithms For more information on using and writing extensions see the webpage. The library of extensions is available from hackage: http://hackage.haskell.org/cgi-bin/hackage-scripts/package/xmonad-contrib Brought to you by the xmonad team: Spencer Janssen Don Stewart Jason Creighton Andrea Rossato David Roundy Brent Yorgey with code contributions from: Brandon Allbery Chris Mears Shachaf Ben-Kiki Eric Mertens Alec Berryman Neil Mitchell Gwern Branwen Devin Mullins Joachim Breitner Daniel Neri Alexandre Buisse Stefan O'Rear Nick Burlett Simon Peyton Jones Peter De Wachter Hans Philipp Annen Aaron Denney Karsten Schoelzel Nelson Elhage Michael Sloan Shae Erisson Ivan Tarasov Joachim Fasting Alex Tarkovsky Michael Fellinger Christian Thiemann David Glasser Joe Thornber Kai Grossjohann Matsuyama Tomohiro Dave Harrison Daniel Wagner Juraj Hercek Ferenc Wagner Sam Hughes Jamie Webb Miikka Koskinen Klaus Weidner David Lazar nornagon Lucas Mai timthelion Robert Marlow Valery V. Vorotyntsev Dougal Stanton Joel Suovaniemi Mats Jansborg Dmitry Kurochkin Clemens Fruhwirth As well as the support of many others on the #xmonad and #haskell IRC channels, and the wider Haskell and window manager communities. Thanks to everyone for their support! From codesite-noreply at google.com Mon Dec 10 00:41:34 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Dec 10 00:36:48 2007 Subject: [xmonad] Issue 99 in xmonad: common command line flags (version, replace, display) Message-ID: <00163600ca7f0440e80c95f895199f28@google.com> Issue 99: common command line flags (version, replace, display) http://code.google.com/p/xmonad/issues/detail?id=99 New issue report by jus...@justinbogner.com: The following command line flags would be nice: 1. --version should output the version of xmonad and quit 2. --display should set the X display, overriding the environment variable $DISPLAY 3. --replace should replace the running window manager (kill the current WM and start XMonad) Issue attributes: Status: New Owner: ---- Labels: Type-Defect Priority-Medium -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From dave at nullcube.com Mon Dec 10 01:13:02 2007 From: dave at nullcube.com (Dave Harrison) Date: Mon Dec 10 01:08:17 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp Message-ID: <475CD8EE.1070808@nullcube.com> Hey all, First up, love the new configuration method, my xmonad.hs file is now nice and tiny :-) Quick "maybe glitch" though, I'm using ComboLayout with Tabbed, and I find that when I first add lots of windows to the layout the alt-tab order is correct (also when adding windows into the middle of the stack it's correct). When I swapDown or swapUp _in_ the stack, the order is correct. But if I swapDown or swapUp at either end of the stack the ordering goes rather pearshaped (the ordering is no longer correct "visually" if you see what I mean). Is this a known thing ? My xmonad.hs is below. Cheers, Dave ---- import XMonad hiding (Tall(..)) import qualified XMonad.StackSet as W import XMonad.Layout.Tabbed import XMonad.Layout.Combo import XMonad.Layout.TwoPane import XMonad.Layout.NoBorders import XMonad.Layout.HintedTile import XMonad.Config (defaultConfig) import XMonad.Hooks.DynamicLog import XMonad.Util.Dmenu import qualified Data.Map as M import System.IO (hPutStrLn) daveConfig = defaultConfig { defaultGaps = [(0,15,0,0)] , logHook = dynamicLog , terminal = "xterm -fa Mono -fs 12" , layoutHook = smartBorders ( combineTwo (TwoPane 0.03 0.5) (tabbed shrinkText defaultTConf) (tabbed shrinkText defaultTConf) ||| mytab ||| tiled Tall ||| tiled Wide ||| Full ) , keys = \c -> mykeys c `M.union` keys defaultConfig c } where -- layouts tiled = HintedTile 1 0.03 0.5 mytab = tabbed shrinkText defaultTConf -- key mapping overrides mykeys (XConfig {modMask = modm, workspaces = ws}) = M.fromList $ [((modm, xK_Left ), sendMessage Shrink) -- %! Shrink the master area ,((modm, xK_Right ), sendMessage Expand) -- %! Expand the master area ,((modm, xK_p ), spawn "exe=`cat /home/dave/.dmenulist | dmenu -b -p \"$\"` && eval \"exec $exe\"") -- @@ Launch dmenu ] main = xmonad $ daveConfig From codesite-noreply at google.com Mon Dec 10 02:15:02 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Dec 10 02:10:15 2007 Subject: [xmonad] Issue 99 in xmonad: common command line flags (version, replace, display) Message-ID: <00c09ffb53810440e95ad378e819b86e@google.com> Issue 99: common command line flags (version, replace, display) http://code.google.com/p/xmonad/issues/detail?id=99 Comment #1 by thomas.adam22: --display and --version are trivial. Would be nice also to have a --screen flag for xinerama, too. The point of this reply is to discuss how --replace might work, since it's not as trivial as people might think. When xmonad loads it should "register" itself as the running window manager. How it would do this is by interning a series of XAtoms which setup meta information about itself, such as: _IC_WM_MANAGER _IC_WM_VERSION _IC_WM_TIMESTAMP Then, using the XClientMessageEvent structure, fill it in. The XAtoms defined above would need changing via XChangeProperty(). Then just send the event of StructureNotifyMask along with the XClientMessageEvent structure. There's more to it than that, but that's the basic outline. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From codesite-noreply at google.com Mon Dec 10 02:22:03 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Dec 10 02:17:17 2007 Subject: [xmonad] Issue 99 in xmonad: common command line flags (version, replace, display) Message-ID: <00163600cf970440e973f22ad519bc7e@google.com> Issue 99: common command line flags (version, replace, display) http://code.google.com/p/xmonad/issues/detail?id=99 Comment #2 by SpencerJanssen: --version should certainly go in. --display isn't required in my opinion, since there is the standard $DISPLAY variable. --replace seems more complicated than it is worth. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From l.mai at web.de Mon Dec 10 03:55:01 2007 From: l.mai at web.de (Lukas Mai) Date: Mon Dec 10 03:51:31 2007 Subject: [xmonad] darcs patch: normalize Module headers Message-ID: Mon Dec 10 09:53:27 CET 2007 Lukas Mai * normalize Module headers -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: text/x-darcs-patch Size: 2378 bytes Desc: A darcs patch for your repository! Url : http://www.haskell.org/pipermail/xmonad/attachments/20071210/0ad7e95f/attachment.bin From xmonad at lonely-star.org Mon Dec 10 05:36:54 2007 From: xmonad at lonely-star.org (Nathan Huesken) Date: Mon Dec 10 05:32:09 2007 Subject: [xmonad] xmonad on MacBook Message-ID: <20071210113654.t4h6xcnrxcgkcgcg@87.230.22.124> Hello together, has somebody expirience with installing xmonad on a MacBook? Is it possible? ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From droundy at darcs.net Mon Dec 10 06:58:49 2007 From: droundy at darcs.net (David Roundy) Date: Mon Dec 10 06:54:04 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <475CD8EE.1070808@nullcube.com> References: <475CD8EE.1070808@nullcube.com> Message-ID: <20071210115317.GA23574@darcs.net> On Mon, Dec 10, 2007 at 05:13:02PM +1100, Dave Harrison wrote: > Quick "maybe glitch" though, I'm using ComboLayout with Tabbed, and I > find that when I first add lots of windows to the layout the alt-tab > order is correct (also when adding windows into the middle of the > stack it's correct). When I swapDown or swapUp _in_ the stack, the > order is correct. But if I swapDown or swapUp at either end of the > stack the ordering goes rather pearshaped (the ordering is no longer > correct "visually" if you see what I mean). Is this a known thing ? ... > , layoutHook = smartBorders ( combineTwo (TwoPane 0.03 > 0.5) (tabbed shrinkText defaultTConf) (tabbed shrinkText defaultTConf) > ||| mytab ||| tiled Tall ||| tiled Wide ||| Full ) First, let me note that you could create the same layout more elegantly as layoutHook = smartBorders ( mytab *|* mytab ||| mytab ||| tiled Tall ||| tiled Wide ||| Full ) Secondly, with regard to focus order, Combo separates the focus order from the visual representation, because the focus order is handled by core xmonad, which has no knowledge of the hierarchical grouping, and isn't friendly to layouts reordering windows. A proper fix would be to implement hierarchical Stacks in the core, but that seems unlikely, so we are left with ugly hacks, and ugly hacks are likely to remain ugly (although, we *can* give them beautiful syntax). -- David Roundy Department of Physics Oregon State University From xmonad at lonely-star.org Mon Dec 10 10:59:01 2007 From: xmonad at lonely-star.org (Nathan Huesken) Date: Mon Dec 10 10:54:14 2007 Subject: [xmonad] xmonad on MacBook In-Reply-To: <14d615330712100524s59923476j35d95043ab055365@mail.gmail.com> References: <20071210113654.t4h6xcnrxcgkcgcg@87.230.22.124> <14d615330712100524s59923476j35d95043ab055365@mail.gmail.com> Message-ID: <20071210165901.vgehlbamo800sg88@87.230.22.124> Sorry for not being clear. I meant under OS X. Greetings, Nathan Quoting Jeremy Apthorp : > On 10/12/2007, Nathan Huesken wrote: >> Hello together, >> >> has somebody expirience with installing xmonad on a MacBook? Is it possible? > > Do you mean under Mac OS X or under Linux? I am running xmonad on a > MacBook Pro as I write this. (Running Linux.) > > -- > - Jeremy Apthorp > ---------------------------------------------------------------- This message was sent using IMP, the Internet Messaging Program. From dons at galois.com Mon Dec 10 11:21:06 2007 From: dons at galois.com (Don Stewart) Date: Mon Dec 10 11:16:19 2007 Subject: [xmonad] xmonad on MacBook In-Reply-To: <20071210165901.vgehlbamo800sg88@87.230.22.124> References: <20071210113654.t4h6xcnrxcgkcgcg@87.230.22.124> <14d615330712100524s59923476j35d95043ab055365@mail.gmail.com> <20071210165901.vgehlbamo800sg88@87.230.22.124> Message-ID: <20071210162106.GB26309@scytale.galois.com> It is certainly possible, http://haskell.org/haskellwiki/Xmonad/Using_xmonad_on_Apple_OSX if you can add more info to that page, that would be most welcome! -- Don xmonad: > Sorry for not being clear. > I meant under OS X. > > Greetings, > Nathan > > Quoting Jeremy Apthorp : > > >On 10/12/2007, Nathan Huesken wrote: > >>Hello together, > >> > >>has somebody expirience with installing xmonad on a MacBook? Is it > >>possible? > > > >Do you mean under Mac OS X or under Linux? I am running xmonad on a > >MacBook Pro as I write this. (Running Linux.) > > > >-- > >- Jeremy Apthorp > > > > > > ---------------------------------------------------------------- > This message was sent using IMP, the Internet Messaging Program. > > > _______________________________________________ > xmonad mailing list > xmonad@haskell.org > http://www.haskell.org/mailman/listinfo/xmonad From andrew at swclan.homelinux.org Mon Dec 10 12:13:34 2007 From: andrew at swclan.homelinux.org (Andrew Sackville-West) Date: Mon Dec 10 12:09:02 2007 Subject: [xmonad] Issue 96 in xmonad: certain dialogs get dropped in gnucash In-Reply-To: <18071eea0712090207y7568bfa4s4a7c8528127d7635@mail.gmail.com> References: <00c09f90f58f0440d110bd43b976664a@google.com> <18071eea0712090207y7568bfa4s4a7c8528127d7635@mail.gmail.com> Message-ID: <20071210171334.GP7681@localhost.localdomain> On Sun, Dec 09, 2007 at 10:07:34AM +0000, Thomas Adam wrote: > Hi -- > > On 09/12/2007, codesite-noreply@google.com wrote: > > Issue 96: certain dialogs get dropped in gnucash > > http://code.google.com/p/xmonad/issues/detail?id=96 > > > > Comment #1 by jcreigh: > > This is definitely an xmonad bug, as the problem does not occur if > > Gnucash windows > > are ignored (with, eg, className =? "Gnucash" --> doIgnore) > > I bet I know what this bug is (I;m assuming transient windows here): > > The window is being mapped and unmapped. If you were to use something > like xscope then you might see that: > > a) Application sends a mapRequest. > a1) Before xmonad has a chance to do that, the application asks to be > put in the WithDrawn state (via a synthetic UnmapNotify event). > b) The window is mapped. > c) GNUCash sends a MapRequest. > d) Another UnmapNotify request is sent and the window is UnMapped. > e) The MapRequest from (c) is handled and a real UnMapNotify request > is issued causing the window it close, never being mapped again. > Anyone feel like clueing me in on what this really means? It sounds to me, from my minimal understanding of the above list, like GnuCash may be at fault (or at least one it's libs -- gtk?) and xmonad is just listening to what it says instead of gracefully ignoring conflicting requests. But I'm no gui nor WM programmer, so I'd love a little education :) A -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071210/e046e3b1/attachment-0001.bin From byorgey at gmail.com Mon Dec 10 12:37:31 2007 From: byorgey at gmail.com (Brent Yorgey) Date: Mon Dec 10 12:32:43 2007 Subject: [xmonad] darcs patch: man/xmonad.hs: add some documentation explaining that 'title' can be used in the manageHook Message-ID: <22fcbd520712100937g683ace4bp1f6e64dbdc76a6f6@mail.gmail.com> Skipped content of type multipart/alternative-------------- next part -------------- A non-text attachment was scrubbed... Name: man-xmonad-manageHook-title.dpatch Type: application/octet-stream Size: 704 bytes Desc: not available Url : http://www.haskell.org/pipermail/xmonad/attachments/20071210/72fef24a/man-xmonad-manageHook-title.obj From codesite-noreply at google.com Mon Dec 10 12:38:58 2007 From: codesite-noreply at google.com (codesite-noreply@google.com) Date: Mon Dec 10 12:34:15 2007 Subject: [xmonad] Issue 51 in xmonad: amsn crashes when a contact tries to open a dialog Message-ID: <00c09ffb4bcf0440f212357a481b1f5b@google.com> Issue 51: amsn crashes when a contact tries to open a dialog http://code.google.com/p/xmonad/issues/detail?id=51 Comment #2 by nomorecolors: http://sourceforge.net/tracker/index.php?func=detail&aid=1807664&group_id=54091&atid=472655 -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings From byorgey at gmail.com Mon Dec 10 13:42:59 2007 From: byorgey at gmail.com (Brent Yorgey) Date: Mon Dec 10 13:38:12 2007 Subject: [xmonad] Patch: Magnifier custom zoom ratios In-Reply-To: <650efde80712081528t1611d598ydc4f11f3c78eb822@mail.gmail.com> References: <650efde80712081528t1611d598ydc4f11f3c78eb822@mail.gmail.com> Message-ID: <22fcbd520712101042p23f7c174ybd80e3c7fcd0a1f2@mail.gmail.com> On Dec 8, 2007 6:28 PM, Tim hobbs wrote: > This just adds a function to magnifier that takes a custom zoom ratio. > It is to be applied after the release as it's just a feature. > Thanks for the patch! However, the haddock documentation is broken. You need a full blank line on either side of any birdtrack-style quoting > like this not > like this. Can you please fix and resubmit the patch? Note that you can generate the haddock documentation by doing runhaskell Setup haddock and then pointing your browser at file:///path/to/XMonadContrib/dist/doc/html/xmonad-contrib/index.html. Thanks! -Brent -------------- next part -------------- An HTML attachment was scrubbed... URL: http://www.haskell.org/pipermail/xmonad/attachments/20071210/51c04d12/attachment.htm From thomas.adam22 at gmail.com Mon Dec 10 14:44:05 2007 From: thomas.adam22 at gmail.com (Thomas Adam) Date: Mon Dec 10 14:39:18 2007 Subject: [xmonad] Issue 96 in xmonad: certain dialogs get dropped in gnucash In-Reply-To: <20071210171334.GP7681@localhost.localdomain> References: <00c09f90f58f0440d110bd43b976664a@google.com> <18071eea0712090207y7568bfa4s4a7c8528127d7635@mail.gmail.com> <20071210171334.GP7681@localhost.localdomain> Message-ID: <18071eea0712101144g2e205ec2g22f0daa5ac5fefb2@mail.gmail.com> Hi -- On 10/12/2007, Andrew Sackville-West wrote: > On Sun, Dec 09, 2007 at 10:07:34AM +0000, Thomas Adam wrote: > > a) Application sends a mapRequest. > > a1) Before xmonad has a chance to do that, the application asks to be > > put in the WithDrawn state (via a synthetic UnmapNotify event). > > b) The window is mapped. > > c) GNUCash sends a MapRequest. > > d) Another UnmapNotify request is sent and the window is UnMapped. > > e) The MapRequest from (c) is handled and a real UnMapNotify request > > is issued causing the window it close, never being mapped again. > > > > Anyone feel like clueing me in on what this really means? It sounds to > me, from my minimal understanding of the above list, like GnuCash may > be at fault (or at least one it's libs -- gtk?) and xmonad is just > listening to what it says instead of gracefully ignoring conflicting > requests. No -- the window manager is doing what it has been told to do, the problem is with what the ICCCM says about how to handle such cases. I should point out I have no idea if the issue reported is what I have outlined or not, I'm simply guessing. A window can be mapped and in the WithDrawn state (i.e., not displayed) on screen. The long and short of what I've detailed there is that should a MapRequest is followed by a synthetic (fake) UnmapNotify request it should simply ignore the MapRequest, since it will map it properly when the real MapRequest is issued. -- Thomas Adam From andrew at swclan.homelinux.org Mon Dec 10 16:12:23 2007 From: andrew at swclan.homelinux.org (Andrew Sackville-West) Date: Mon Dec 10 16:07:50 2007 Subject: [xmonad] emacs -nw and xmonad key bindings In-Reply-To: <20071208033509.GB7681@localhost.localdomain> References: <20071208032735.GA7681@localhost.localdomain> <20071208033509.GB7681@localhost.localdomain> Message-ID: <20071210211223.GC7681@localhost.localdomain> On Fri, Dec 07, 2007 at 07:35:09PM -0800, Andrew Sackville-West wrote: > On Fri, Dec 07, 2007 at 07:27:36PM -0800, Andrew Sackville-West wrote: > > Just posting this up in case anyone comes looking for it. > > well crap. That didn't work. > > for some reason. > > now it seems I have to *remove* Alt_L altogether from mod1 with > > remove mod1 = Alt_L > > replacing the > > add mod1 = Alt_L > > and keeping the rest intact seems to have it. > > for now. In the interest of full disclosure... this doesn't seem to work either. blah. the current, really does work solution: map Caps Lock to mod3 with: clear lock add mod3 = Caps_Lock and leaving the rest default works quite nicely... And eliminates that horrible caps lock key too! sorry for the noise. A -------------- next part -------------- A non-text attachment was scrubbed... Name: not available Type: application/pgp-signature Size: 189 bytes Desc: Digital signature Url : http://www.haskell.org/pipermail/xmonad/attachments/20071210/5b151cfc/attachment.bin From dave at nullcube.com Mon Dec 10 16:20:04 2007 From: dave at nullcube.com (Dave Harrison) Date: Mon Dec 10 16:15:18 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <20071210115317.GA23574@darcs.net> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> Message-ID: <475DAD84.4080504@nullcube.com> David Roundy wrote: > On Mon, Dec 10, 2007 at 05:13:02PM +1100, Dave Harrison wrote: >> Quick "maybe glitch" though, I'm using ComboLayout with Tabbed, and I >> find that when I first add lots of windows to the layout the alt-tab >> order is correct (also when adding windows into the middle of the >> stack it's correct). When I swapDown or swapUp _in_ the stack, the >> order is correct. But if I swapDown or swapUp at either end of the >> stack the ordering goes rather pearshaped (the ordering is no longer >> correct "visually" if you see what I mean). Is this a known thing ? > ... >> , layoutHook = smartBorders ( combineTwo (TwoPane 0.03 >> 0.5) (tabbed shrinkText defaultTConf) (tabbed shrinkText defaultTConf) >> ||| mytab ||| tiled Tall ||| tiled Wide ||| Full ) > > First, let me note that you could create the same layout more elegantly as > > layoutHook = smartBorders ( mytab *|* mytab ||| mytab ||| tiled Tall ||| > tiled Wide ||| Full ) Cheers David, I'll use that one ! :-) > Secondly, with regard to focus order, Combo separates the focus order from > the visual representation, because the focus order is handled by core > xmonad, which has no knowledge of the hierarchical grouping, and isn't > friendly to layouts reordering windows. A proper fix would be to implement > hierarchical Stacks in the core, but that seems unlikely, so we are left > with ugly hacks, and ugly hacks are likely to remain ugly (although, we > *can* give them beautiful syntax). So just to clarify, does this mean that there IS an ugly hack in place but there is a bug in it, or the solution would be an ugly hack that has not been implemented ? Cheers D From droundy at darcs.net Mon Dec 10 16:34:13 2007 From: droundy at darcs.net (David Roundy) Date: Mon Dec 10 16:29:26 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <475DAD84.4080504@nullcube.com> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> <475DAD84.4080504@nullcube.com> Message-ID: <20071210213408.GD23574@darcs.net> On Tue, Dec 11, 2007 at 08:20:04AM +1100, Dave Harrison wrote: > David Roundy wrote: > > Secondly, with regard to focus order, Combo separates the focus order from > > the visual representation, because the focus order is handled by core > > xmonad, which has no knowledge of the hierarchical grouping, and isn't > > friendly to layouts reordering windows. A proper fix would be to implement > > hierarchical Stacks in the core, but that seems unlikely, so we are left > > with ugly hacks, and ugly hacks are likely to remain ugly (although, we > > *can* give them beautiful syntax). > > So just to clarify, does this mean that there IS an ugly hack in place > but there is a bug in it, or the solution would be an ugly hack that > has not been implemented ? It means there IS an ugly hack in place, and it's got a bug because reimplementing most of xmonad core in an extension seems to me like the wrong way to go... besides the fact that it would require you to use custom shiftUp/Down etc. Xmonad is just not designed to be extensible in the way that Combo extends it, and this shows. -- David Roundy Department of Physics Oregon State University From dave at nullcube.com Mon Dec 10 18:37:38 2007 From: dave at nullcube.com (Dave Harrison) Date: Mon Dec 10 18:32:51 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <20071210213408.GD23574@darcs.net> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> <475DAD84.4080504@nullcube.com> <20071210213408.GD23574@darcs.net> Message-ID: <475DCDC2.6020109@nullcube.com> David Roundy wrote: > On Tue, Dec 11, 2007 at 08:20:04AM +1100, Dave Harrison wrote: >> David Roundy wrote: >>> Secondly, with regard to focus order, Combo separates the focus order from >>> the visual representation, because the focus order is handled by core >>> xmonad, which has no knowledge of the hierarchical grouping, and isn't >>> friendly to layouts reordering windows. A proper fix would be to implement >>> hierarchical Stacks in the core, but that seems unlikely, so we are left >>> with ugly hacks, and ugly hacks are likely to remain ugly (although, we >>> *can* give them beautiful syntax). >> So just to clarify, does this mean that there IS an ugly hack in place >> but there is a bug in it, or the solution would be an ugly hack that >> has not been implemented ? > > It means there IS an ugly hack in place, and it's got a bug because > reimplementing most of xmonad core in an extension seems to me like the > wrong way to go... besides the fact that it would require you to use custom > shiftUp/Down etc. Xmonad is just not designed to be extensible in the way > that Combo extends it, and this shows. Yow, that's a bit of a showstopper for me since I'm a heavy user of ComboLayout at the office (dev on a big monitor calls for a Full to the left and tabs to the right I find) - I'm suddenly considering a downgrade :-( What's the way forward here ? From j at jwebb.sygneca.com Mon Dec 10 18:43:00 2007 From: j at jwebb.sygneca.com (Jamie Webb) Date: Mon Dec 10 18:37:35 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <475DCDC2.6020109@nullcube.com> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> <475DAD84.4080504@nullcube.com> <20071210213408.GD23574@darcs.net> <475DCDC2.6020109@nullcube.com> Message-ID: <20071210234300.6854dad0@carbon.sygneca.com> On 2007-12-11 10:37:38 Dave Harrison wrote: > David Roundy wrote: > > On Tue, Dec 11, 2007 at 08:20:04AM +1100, Dave Harrison wrote: > >> David Roundy wrote: > >>> Secondly, with regard to focus order, Combo separates the focus > >>> order from the visual representation, because the focus order is > >>> handled by core xmonad, which has no knowledge of the > >>> hierarchical grouping, and isn't friendly to layouts reordering > >>> windows. A proper fix would be to implement hierarchical Stacks > >>> in the core, but that seems unlikely, so we are left with ugly > >>> hacks, and ugly hacks are likely to remain ugly (although, we > >>> *can* give them beautiful syntax). > >> So just to clarify, does this mean that there IS an ugly hack in > >> place but there is a bug in it, or the solution would be an ugly > >> hack that has not been implemented ? > > > > It means there IS an ugly hack in place, and it's got a bug because > > reimplementing most of xmonad core in an extension seems to me like > > the wrong way to go... besides the fact that it would require you > > to use custom shiftUp/Down etc. Xmonad is just not designed to be > > extensible in the way that Combo extends it, and this shows. > > Yow, that's a bit of a showstopper for me since I'm a heavy user of > ComboLayout at the office (dev on a big monitor calls for a Full to > the left and tabs to the right I find) - I'm suddenly considering a > downgrade :-( What's the way forward here ? Try the WindowNavigation plugin? /J From xmonad at s001.hethrael.com Mon Dec 10 19:08:40 2007 From: xmonad at s001.hethrael.com (lithis) Date: Mon Dec 10 19:03:58 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <475DCDC2.6020109@nullcube.com> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> <475DAD84.4080504@nullcube.com> <20071210213408.GD23574@darcs.net> <475DCDC2.6020109@nullcube.com> Message-ID: <20071211000840.GA22938@darksigil.darksigil.com> On Tue, 2007/12/11 10:37:38 +1100, Dave Harrison wrote: > > Yow, that's a bit of a showstopper for me since I'm a heavy user of > ComboLayout at the office (dev on a big monitor calls for a Full to > the left and tabs to the right I find) - I'm suddenly considering a > downgrade :-( What's the way forward here ? What about LayoutScreens? http://www.xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Layout-LayoutScreens.html I haven?t used it, but it sounds like it might suffice. From dave at nullcube.com Mon Dec 10 19:27:46 2007 From: dave at nullcube.com (Dave Harrison) Date: Mon Dec 10 19:22:59 2007 Subject: [xmonad] XMonad 0.5, combo layouts, swapDown and swapUp In-Reply-To: <20071211000840.GA22938@darksigil.darksigil.com> References: <475CD8EE.1070808@nullcube.com> <20071210115317.GA23574@darcs.net> <475DAD84.