August 2010 - xmonad - Haskell.org

Re: Issue 313 in xmonad: Merge contrib's isFullscreen and doFullFloat to core
by codesite-noreply＠google.com 07 May '11

07 May '11

Comment #6 on issue 313 by gwern0: Merge contrib's isFullscreen and doFullFloat to core http://code.google.com/p/xmonad/issues/detail?id=313 The next release from darcs will be 1.0; is there any particular reason the change hasn't been made & pushed, or this bug closed? -- 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

Issue 378 in xmonad: Clean up WindowBringer interface
by codesite-noreply＠google.com 12 Apr '11

12 Apr '11

Status: New Owner: ---- New issue 378 by MathStuf: Clean up WindowBringer interface http://code.google.com/p/xmonad/issues/detail?id=378 The attached patch adds a bringMenu' function so that the user may specify a command for it as well. In addition, the other functions are cleaned up to use cascade with the default "dmenu" command. I tried doing "darcs record", but I do not have packages that satisfy the testing version dependencies and the xmonad update from cabal has dependency solving issues with the system version. Attachments: xmonad-contrib-windowbringer-cleanup.patch 2.2 KB -- 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 368 in xmonad: Action to send subkey to a window
by codesite-noreply＠google.com 12 Apr '11

12 Apr '11

Status: New Owner: ---- New issue 368 by MathStuf: Action to send subkey to a window http://code.google.com/p/xmonad/issues/detail?id=368 What steps will reproduce the problem? 1. When using subkey for keybindings, it grabs any use of the subkey. 2. I tried using xdotool to send the key, but xmnad grabs this as well. What is the expected output? Send keypress to focused window. What do you see instead? xmonad grabs the simulated keypress. What version of the product are you using? On what operating system? 0.9 Fedora 12 x86_64 and i686 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output from xmonad --recompile. Attachments: xmonad.hs 10.0 KB -- 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 1

Re: Issue 317 in xmonad: Implement a working X.U.putSelection
by codesite-noreply＠google.com 11 Mar '11

11 Mar '11

Comment #22 on issue 317 by wirtwo...(a)gmail.com: Implement a working X.U.putSelection http://code.google.com/p/xmonad/issues/detail?id=317 Issue 365 has been merged into this issue. -- 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 7

updating.... in xmobar
by Jacob Alexandersson 04 Feb '11

04 Feb '11

Hey all, I just started trying xmonad out, and I really ilke it. I've used ratpoison in the past but eventually gave it up. xmonad seems to work better for me so far. I realize this is a xmobar question, but I am guessing there are people on this list that uses xmobar also. I have a .xmobarrc which looks like follows: <snip> Config { font = "-*-Fixed-Bold-R-Normal-*-13-*-*-*-*-*-*-*" , bgColor = "black" , fgColor = "grey" , position = TopW L 100 , lowerOnStart = True , commands = [ Run Cpu ["-L","3","-H","50","--normal","green","--high","red"] 10 , Run Memory ["-t","Mem: <usedratio>%"] 10 , Run Swap [] 10 , Run Date "%a %b %_d %l:%M" "date" 10 , Run Com "uname" ["-s","-r"] "blaj" 36000 , Run StdinReader ] , sepChar = "%" , alignSep = "}{" , template = "%StdinReader% }{ %blaj% %cpu% | %memory% * %swap% <fc=#ee9a00>%date%</fc>" } </snip> ...and in ~/.xmonad/xmonad.hs I have: <snip> ... xmproc <- spawnPipe "/usr/bin/xmobar /home/jcx/.xmobarrc" ... </snip> All I get is "updating..." where %StdinReader% is placed. Is this correct?? Am I missing something? cheers, Jacob.

3 3

darcs patch: Note things to update each release. (and 2 more)
by Adam Vogt 31 Dec '10

31 Dec '10

3 patches for repository aavogt@code.haskell.org:/srv/code/xmonad: Mon Mar 22 11:06:22 EDT 2010 Adam Vogt <vogt.adam(a)gmail.com> * Note things to update each release. Sat Apr 3 14:11:15 EDT 2010 Adam Vogt <vogt.adam(a)gmail.com> * Update comments describing `recompile' Sat Apr 3 14:13:54 EDT 2010 Adam Vogt <vogt.adam(a)gmail.com> * Update util/GenerateManpage to be pandoc-1.4 compatible

2 1

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