May 2010 - xmonad - Haskell.org

darcs patch: get rid of zombies in a more portable way
by Tomas Janousek 12 Dec '10

12 Dec '10

Sun Apr 11 20:55:10 CEST 2010 Tomas Janousek <tomi(a)nomi.cz> * get rid of zombies in a more portable way FreeBSD and OpenBSD don't support the signal(SIGCHLD, SIG_IGN) way of dealing with them. Wikipedia quote on the issue: "POSIX.1-2001 allows a parent process to elect for the kernel to automatically reap child processes that terminate by setting the disposition of SIGCHLD to SIG_IGN or by setting the SA_NOCLDWAIT flag for the SIGCHLD signal; Linux 2.6 kernels adhere to this behavior while FreeBSD supports only the latter of these methods. Because of historical differences between System V and BSD behaviors with regard to ignoring SIGCHLD, calling wait remains the most portable paradigm for cleaning up after forked child processes." -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

5 4

Re: Issue 69 in xmonad: Key binding improvements
by codesite-noreply＠google.com 11 Dec '10

11 Dec '10

Comment #9 on issue 69 by mark.stosberg: Key binding improvements http://code.google.com/p/xmonad/issues/detail?id=69 I'm struggling to try Xmonad because I don't have a windows key and the "loving caress" of xmodmap (as the original poster puts it) is not so gentle. As someone new to Xmonad and Haskell, the "sufficient" workaround is not simple at all: - delete all of the default keybindings - add a single keybinding for your desired prefix key that activates a submap - add all the desired keybindings to your submap I wouldn't know how to start with implementing that. I even tried the "extra user-friendly" BlueTile alternative. It also assumed I had a Windows key... -- 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

1 4

Re: Issue 291 in xmonad: Layout.Tabbed has drawing problems when used with Layout.MultiToggle
by codesite-noreply＠google.com 04 Nov '10

04 Nov '10

Updates: Labels: Type-Defect Component-Contrib Comment #1 on issue 291 by vogt.adam: Layout.Tabbed has drawing problems when used with Layout.MultiToggle http://code.google.com/p/xmonad/issues/detail?id=291 Can you still reproduce this if you include this patch: Sat Dec 19 19:47:33 EST 2009 Tomas Janousek <tomi(a)nomi.cz> * Fix MultiToggle crashes with decorated layouts The problem was that certain layouts keep their "world" state in their value, which was thrown away and forgotten after ReleaseResources during toggle. In particular, decorated layouts store some X11 handles in them and allocate/deallocate it as appropriate. If any modification to their state is ignored, they may try to deallocate already deallocated memory, which results in a crash somewhere inside Xlib. This patch makes Transformers reversible so that nothing is ever ignored. As a side effect, layout transformers now do receive messages and messages for the base layout do not need the undo/reapply cycle -- we just pass messages to the current transformed layout and unapply the transformer when needed. (This, however, doesn't mean that the base layout is not asked to release resources on a transformer change -- we still need the transformer to release its resources and there's no way to do this without asking the base layout as well.) -- 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

1 5

Re: Issue 197 in xmonad: Blocking on nextEvent stops other threads from running
by codesite-noreply＠google.com 04 Nov '10

04 Nov '10

Comment #4 on issue 197 by byorgey: Blocking on nextEvent stops other threads from running http://code.google.com/p/xmonad/issues/detail?id=197 What's the status of this ticket? Is this a WontFix? Or is there something that could be improved here? -- 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

1 4

Re: Issue 4 in xmonad: Separate focus for tiled and floating layers
by codesite-noreply＠google.com 16 Oct '10

16 Oct '10

Comment #16 on issue 4 by scuz.there: Separate focus for tiled and floating layers http://code.google.com/p/xmonad/issues/detail?id=4 It might be more useful to have transients for a window hidden when that window is not focused. Similar to Photoshop on Mac. -- 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

1 8

Issue 366 in xmonad: XMonad.Layout.NoFrillsDecoration depends on SimpleDecoration
by codesite-noreply＠google.com 30 Sep '10

30 Sep '10

Status: New Owner: ---- New issue 366 by j...(a)kitenet.net: XMonad.Layout.NoFrillsDecoration depends on SimpleDecoration http://code.google.com/p/xmonad/issues/detail?id=366 What steps will reproduce the problem? 1.import XMonad.Layout.NoFrillsDecoration 2.do not import XMonad.Layout.SimpleDecoration 3. What is the expected output? What do you see instead? xmonad.hs:41:10: Not in scope: `defaultTheme' xmonad.hs:42:4: Not in scope: `activeColor' xmonad.hs:43:4: Not in scope: `inactiveColor' xmonad.hs:44:4: Not in scope: `activeBorderColor' xmonad.hs:45:4: Not in scope: `inactiveBorderColor' Etc. This goes away if SimpleDecoration is also imported. What version of the product are you using? On what operating system? 0.9 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. -- 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

1 3

Issue 395 in xmonad: Support for multiple master windows for X.L.Master
by codesite-noreply＠google.com 25 Sep '10

25 Sep '10

Status: New Owner: ---- New issue 395 by quesel: Support for multiple master windows for X.L.Master http://code.google.com/p/xmonad/issues/detail?id=395 Find attached a patch that enables the contrib module X.L.Master to handle multiple master windows. Best Regards, Jan Attachments: master.patch 42.6 KB

1 4

Re: Issue 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 12 Sep '10

12 Sep '10

Updates: Status: Accepted Labels: Type-Defect Component-Contrib Comment #5 on issue 311 by byorgey: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 (No comment was entered for this change.) -- 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

1 2

Re: [xmonad] Upgrading repo formats
by Gwern Branwen 10 Sep '10

10 Sep '10

On Fri, Apr 23, 2010 at 3:40 PM, adam vogt <vogt.adam(a)gmail.com> wrote: > On Sat, Apr 10, 2010 at 1:16 PM, Gwern Branwen <gwern0(a)gmail.com> wrote: >> While waiting on a slow connection today to darcs get XMC, I had time >> to ponder. The patches are (or would be) in my global cache, so it >> could go much faster. Why doesn't it? Because xmonad-contrib and >> xmonad-core are both still using darcs-1 fomatted repositories. >> >> Is there any particular reason to not upgrade? Even Debian Stable has >> Darcs 2.x (http://packages.debian.org/lenny/darcs) so it's not as if >> there are many people who would be unable to do a darcs get. >> >> -- >> gwern > > I support this. > > Since this isn't something we can easily rollback, (without the messy > situation of keeping the unupgraded repository updated in parallel), it > is important to have some consensus before updating repo formats. What now? Nobody has objected here, and it's been several days, so I would guess not many will object in the future. I would point out that besides the mere 12 pulls using darcs 1.x this month - which could all be due to just 1 user - Xmonad has broken ghc 6.6 support, and I wouldn't be surprised if ghc 6.8 support was now broken. So anyone actually *using* darcs xmonad-core/xmonad-contrib must be using a recent GHC, and there are Darcs 2.xs which support 6.8 and probably 6.6 as well. Which implies that anyone using darcs xmonad is capable of upgrading to Darcs 2. We don't to worry about anyone locked down to Darcs 1.x. The question is whether we have the will to actually upgrade the repos and make people re-'darcs get' the repos. I think we do, and that the long-term benefits of cached patches and fewer conflicts and active Darcs support and whatnot justify the short-term pain. But ultimately, while I could unilaterally upgrade xmonad-contrib, dons and sjanssen are the only ones who can upgrade xmonad-core, and I'd feel pretty silly doing only half the job. -- gwern

5 7

Issue 336 in xmonad: xmonad won't start: Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_)
by codesite-noreply＠google.com 26 Aug '10

26 Aug '10

Status: New Owner: ---- New issue 336 by flazzarino: xmonad won't start: Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_) http://code.google.com/p/xmonad/issues/detail?id=336 What steps will reproduce the problem? 1. last line of ~/.xinitrc: exec /Users/franco/.cabal/bin/xmonad What is the expected output? What do you see instead? I expect to have xmonad launch but i get this error in console 11/13/09 2:36:51 PM org.x.startx[7572] xmonad-i386-darwin: XMonad/Main.hsc:(82,14)-(84,41): Irrefutable pattern failed for pattern (Data.Maybe.Just nbc_) What version of the product are you using? On what operating system? xmonad 0.9 (installed via cabal) ghc-version (6.10.4) installed via the package OSX 10.6.2 (Snow Leopard) Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". import XMonad main = xmonad defaultConfig #no output Please provide any additional information below. on a mailing list i've seen hints that X cannot support the colors gray and red but i'm using a very stock snow leopard X11, only fullscreen is turned on -- 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

1 10