- xmonad - Haskell.org

Issue 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 12 May '09

12 May '09

Comment #1 on issue 294 by asgaro...(a)gmx.de: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 This should already be fixed in contrib-darcs(including something similar to your suggestion). -- 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: X.L.LayoutBuilder doc fix and cleaning
by Anders Engstrom 10 May '09

10 May '09

Sat May 9 21:52:54 CEST 2009 Anders Engstrom <ankaan(a)gmail.com> * X.L.LayoutBuilder doc fix and cleaning

2 1

darcs patch: X.L.LayoutBuilder custom layouts
by Anders Engstrom 09 May '09

09 May '09

Sat May 9 19:46:27 CEST 2009 Anders Engstrom <ankaan(a)gmail.com> * X.L.LayoutBuilder custom layouts A layout combinator that sends a specified number of windows to one rectangle and the rest to another.

3 3

Problem with manage hook
by Maurício 07 May '09

07 May '09

Hi, I use this manageHook: mh = ( ask >>= doF . sink ) It works well except for a single application ('netgen', which uses a widget set that I can't identify). When it opens a dialog window, everything starts to flash (like if black and white lights were alternating fast). My wild guess is that when my manageHook changes a widget parameter (size?) the widget reacts changing it back, and I get an infinite loop. Do you think I could improve my manageHook to solve that? Thanks for your comments, Maurício

2 1

ANN: XMonad in Fedora 11
by loupgaroublond＠gmail.com 07 May '09

07 May '09

Hey All, I'm happy to announce the little fib that is the subject of this message. My XMonad packages have been accepted by the Fedora review process. It is now possible for us to get the package in Fedora proper. Currently, there is a working build for rawhide, the unstable development branch of Fedora. There will be a build for the Fedora 11 release shortly. The only caveat is that we missed the deadline for the Fedora 11 Release, and therefore XMonad will not be in the "Everything" package set until Fedora 12. It will be available by default in the updates repository, any user can install it simply with yum. The F12 build can be found here. http://koji.fedoraproject.org/koji/buildinfo?buildID=101104 (Until these packages hit repositories, the recommended way to install XMonad on Fedora is to use cabal-install.) -Yaakov

1 0

Issue 292 in xmonad: Border pixels not rendered on screens rotated with xrandr
by codesite-noreply＠google.com 07 May '09

07 May '09

Updates: Status: Invalid Comment #1 on issue 292 by SpencerJanssen: Border pixels not rendered on screens rotated with xrandr http://code.google.com/p/xmonad/issues/detail?id=292 It's an X or video driver bug, those are the components responsible for actually drawing the borders. Window borders aren't an often used feature, so it is not uncommon for problems in border support to go unnoticed. -- 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 290 in xmonad: Windows are no longer visible but are still there
by codesite-noreply＠google.com 07 May '09

07 May '09

Updates: Status: Invalid Comment #6 on issue 290 by SpencerJanssen: Windows are no longer visible but are still there http://code.google.com/p/xmonad/issues/detail?id=290 Again, most likely an xcompmgr issue. If you want to confirm that there is an issue with FadeInactive, check whether the output of xprop | grep _NET_WM_WINDOW_OPACITY on the invisible windows is sane. Marking as invalid until then. -- 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 230 in xmonad: Modular config support
by codesite-noreply＠google.com 07 May '09

07 May '09

Comment #14 on issue 230 by SpencerJanssen: Modular config support http://code.google.com/p/xmonad/issues/detail?id=230 Issue 293 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 0

Issue 293 in xmonad: ~/.xmonad/ not in include path
by codesite-noreply＠google.com 07 May '09

07 May '09

Updates: Status: Duplicate Mergedinto: 230 Comment #1 on issue 293 by SpencerJanssen: ~/.xmonad/ not in include path http://code.google.com/p/xmonad/issues/detail?id=293 (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 0

Issue 294 in xmonad: fadeInactiveLogHook behaviour messed up on xinerama
by codesite-noreply＠google.com 07 May '09

07 May '09

Status: New Owner: ---- New issue 294 by kernseife: fadeInactiveLogHook behaviour messed up on xinerama http://code.google.com/p/xmonad/issues/detail?id=294 0.8 fadeInactiveLogHook keeps one window per screen opaque, not only the focused window of the active screen. Related: There are some apps that some user might not want to have faded, like mplayer. Suggestion: http://hpaste.org/fastcgi/hpaste.fcgi/view?id=4670 ...or, rather, fadeInactiveLogHook :: Ratio -> [Query Bool] -> X () -- 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