April 2008 - xmonad - Haskell.org

darcs patch: Allow tabbar to always be shown.
by ivan.miljenovic＠gmail.com 18 Apr '08

18 Apr '08

Tue Apr 15 14:37:28 EST 2008 Ivan.Miljenovic(a)gmail.com * Allow tabbar to always be shown. Patch take 4, hopefully the final version. Includes droundy's suggestions.

4 3

XMoBar: Waking up the kernel too often
by Dominik Bruhn 18 Apr '08

18 Apr '08

Hy, I hope this is the right place to report an issue concerning XMoBar: Even if you update the parts of the bar very seldom (say every minute), the program itself wakes up every 0.1 second. This makes XMobar the "Top cause for wakeups" in powertop and this keeps my cpu in C3-State and so it uses more power and my batery last shorter. It would be fine if xmobar would calculate the minimum needed delay for the mainloop and use this instead of the fix value. Please tell me what you think: Is it a bug and worth fixing? Thanks -- Dominik Bruhn mailto: dominik(a)dbruhn.de

3 2

Issue 181 in xmonad: xmonad should make use of POSIX signals
by codesite-noreply＠google.com 18 Apr '08

18 Apr '08

Issue 181: xmonad should make use of POSIX signals http://code.google.com/p/xmonad/issues/detail?id=181 New issue report by ppergame: It would be useful to have a signal that restarts xmonad. SIGHUP is bad idea -- here's some random discussion thread about it: http://ml.42.org/wmx/msg00319.html SIGUSR1/2 might be more appropriate. 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

1 0

Issue 178 in xmonad: UpdatePointer behavior not usable with Tabbed layout
by codesite-noreply＠google.com 18 Apr '08

18 Apr '08

Issue 178: UpdatePointer behavior not usable with Tabbed layout http://code.google.com/p/xmonad/issues/detail?id=178 Comment #6 by laylward: Klaus, that seems to have fixed my problem much more reliably. Thanks! -- 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 0

Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 17 Apr '08

17 Apr '08

Issue 177: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 Comment #3 by awesomelyawesome: Potentially the same thing using claws-mail auto complete, and workspace switching. 1. Compose new mail, and attempt to auto complete an email address 2. Once the completion list pops up, use mod-<n> to switch to a different work space 3. The completion dialog stays raised, and only disappears when clicked 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 0

Announcing DarcsWatch (with link)
by Joachim Breitner 17 Apr '08

17 Apr '08

Hi, sorry for the spam, but what I forgot in the first mail: You can find DarcsWatch at: http://darcswatch.nomeata.de/ A lot of haskell-related projects use the darcs version control system. Darcs has the nice feature that you can easily submit a patch by e-mail, usually sent to the project maintainer or a mailing list. What has bothered me in the past was that I had to manually check whether my patch was applied yet. So this week, I wrote DarcsWatch. DarcsWatch receives submitted patches and compares them to the repositories it knows about, whether the patch is missing there or not. You either send your patches to DarcsWeb directly when submitting them, using CC, or DarcsWatch is subscribed to the project mailing list itself, which is the case for the darcs-devel and xmonad lists. Other than that, not much is to do, and you’ll find a nice overview of your patches with diffs and download links. For an example, see: http://darcswatch.nomeata.de/user_mail@joachim-breitner.de.html If you want to use DarcsWatch for your contributions to other projects, or for your own projects, have a look the documentation at http://darcs.nomeata.de/darcswatch/documentation.html There are probably still bugs around, and the problem of marking patches as obsolete is not really solved yet, so if you have ideas about it, mail me or come to #darcs on freenode. Patches are always welcome, you can get the source from DarcsWatch’s repository, found at http://darcs.nomeata.de/darcswatch/ Enjoy, Joachim -- Joachim Breitner e-Mail: mail(a)joachim-breitner.de Homepage: http://www.joachim-breitner.de ICQ#: 74513189 Jabber-ID: nomeata(a)joachim-breitner.de

1 0

Announcing DarcsWatch
by Joachim Breitner 17 Apr '08

17 Apr '08

Hi, (Hi again to those on haskell-cafe, but things have changed since the other announcement) A lot of haskell-related projects use the darcs version control system. Darcs has the nice feature that you can easily submit a patch by e-mail, usually sent to the project maintainer or a mailing list. What has bothered me in the past was that I had to manually check whether my patch was applied yet. So this week, I wrote DarcsWatch. DarcsWatch receives submitted patches and compares them to the repositories it knows about, whether the patch is missing there or not. You either send your patches to DarcsWeb directly when submitting them, using CC, or DarcsWatch is subscribed to the project mailing list itself, which is the case for the darcs-devel and xmonad lists. Other than that, not much is to do, and you’ll find a nice overview of your patches with diffs and download links. For an example, see: http://darcswatch.nomeata.de/user_mail@joachim-breitner.de.html If you want to use DarcsWatch for your contributions to other projects, or for your own projects, have a look the documentation at http://darcs.nomeata.de/darcswatch/documentation.html There are probably still bugs around, and the problem of marking patches as obsolete is not really solved yet, so if you have ideas about it, mail me or come to #darcs on freenode. Patches are always welcome, you can get the source from DarcsWatch’s repository, found at http://darcs.nomeata.de/darcswatch/ Enjoy, Joachim -- Joachim Breitner e-Mail: mail(a)joachim-breitner.de Homepage: http://www.joachim-breitner.de ICQ#: 74513189 Jabber-ID: nomeata(a)joachim-breitner.de

1 0

Issue 180 in xmonad: In focus-follows-mouse mode, the wrong window gets focused
by codesite-noreply＠google.com 17 Apr '08

17 Apr '08

Issue 180: In focus-follows-mouse mode, the wrong window gets focused http://code.google.com/p/xmonad/issues/detail?id=180 Comment #5 by Klaus.Weidner: I've changed the patch to move the mouseFocused flag to XConf and using "local" to scope it, it works for me. I think I'm starting to get a better grasp how this works - effectively like dynamic/special variable bindings in Perl/Common Lisp, but with much more impressive terminology ;-) On my system this also resolves the UpdatePointer problems reported in issue #178, the tabbed mode works as expected. Attachments: xmonad-core-mouse-focused.dpatch 3.3 KB xmonad-contrib-mouse-focused.dpatch 7.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 0

darcs patch: Script callbacks for hooks
by Trevor Elliott 16 Apr '08

16 Apr '08

Hi Everyone, I've added the ability to call a script with an argument to direct execution. For example, if you'd like to run a hook on startup that does something like manage your dzen2 instance, all you would need to do is make sure that: > execScriptHook "startup" was somewhere in your startup hook definition, and the script ~/.xmonad/hooks would be called with a single argument of "startup". --trevor

2 1

Issue 180 in xmonad: In focus-follows-mouse mode, the wrong window gets focused
by codesite-noreply＠google.com 16 Apr '08

16 Apr '08

Issue 180: In focus-follows-mouse mode, the wrong window gets focused http://code.google.com/p/xmonad/issues/detail?id=180 Comment #4 by SpencerJanssen: Regarding the changes to the core, I think there is still a nicer solution waiting to be found. What if we added another field to the 'XConf' structure that indicates whether the current action was initiated by a click or mouse motion? We can use MonadReader's 'local' function to nicely scope this across those actions only. Klaus, does this help with the updatepointer issues too? -- 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 0