- xmonad - Haskell.org

Issue 172 in xmonad: When managing new windows at startup, hide those that should not be visible
by codesite-noreply＠google.com 07 Apr '08

07 Apr '08

Issue 172: When managing new windows at startup, hide those that should not be visible http://code.google.com/p/xmonad/issues/detail?id=172 New issue report by SpencerJanssen: xmonad assumes that windows accepted by 'manage' are unmapped. This is the case with windows created while xmonad is running, but is not the case with windows that were created before xmonad has started. How to reproduce: - add a manageHook that sends a window to a workspace that isn't the first - start one of these windows while xmonad is not running - start xmonad - notice that the window appears on the screen while it should be non-visible Thanks to hmich on #xmonad for reporting the problem. Issue attributes: Status: Accepted Owner: SpencerJanssen 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

screenshots
by Don Stewart 07 Apr '08

07 Apr '08

i've updated some of the screenshots on the wiki, http://haskell.org/haskellwiki/Xmonad/Screenshots If people have other nice setups -- and I know there's some serious graphic designers out there -- please feel free to upload your screenshots and configs :) Transparency, compositing etc all welcome -- Don

2 2

Issue 171 in xmonad: focus switching problems with xxkb
by codesite-noreply＠google.com 07 Apr '08

07 Apr '08

Issue 171: focus switching problems with xxkb http://code.google.com/p/xmonad/issues/detail?id=171 New issue report by dons00: 'ExplicitCall' on #haskell reports that: just start the xxkb in xmonad, change the xxkb group, switch to other window and the group is preserved. that isn't a supposed behaviour and that doesn't happen on several other WMs I used (wmii and fwvm) Possibly an EWMH issue? Issue attributes: Status: New Owner: dons00 Labels: Type-Defect Priority-Medium Usability -- 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 158 in xmonad: _NET_WORKAREA support
by codesite-noreply＠google.com 07 Apr '08

07 Apr '08

Issue 158: _NET_WORKAREA support http://code.google.com/p/xmonad/issues/detail?id=158 Comment #4 by nomeata: I think its used by, for example, natuilus to find out where to put the icons. If it's just the screen minus struts (i.e. docks), it should be pretty doable. I guess I'll assign it to me and I'll try to put it in EWMH. I'd still like to have a test case so I can verify I did it properly. How does enso behave now, and how should it, Nathan? Issue attribute updates: Owner: nomeata Labels: Component-Contrib -- 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 170 in xmonad: Feature Request: Remember layout for each workspace
by codesite-noreply＠google.com 06 Apr '08

06 Apr '08

Issue 170: Feature Request: Remember layout for each workspace http://code.google.com/p/xmonad/issues/detail?id=170 Comment #1 by r...(a)ro-che.info: Sorry, I misunderstood and misguided you in IRC. You should be satisfied by PerWorkspace extension. What you asked in IRC was remembering layouts on exit and restoring them on startup, which is not implemented yet. Issue attribute updates: Status: Invalid -- 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 170 in xmonad: Feature Request: Remember layout for each workspace
by codesite-noreply＠google.com 06 Apr '08

06 Apr '08

Issue 170: Feature Request: Remember layout for each workspace http://code.google.com/p/xmonad/issues/detail?id=170 New issue report by carsten.otto: Hi! I'd like to have (e.g.) "Workspace 5" always use the layout "Circle", where all others should have the "Fullscreen" layout. With the current configuration I have to manually set the layout for "Workspace 5" after every reboot. Some optional default layout for every workspace in the config file would be nice. Thanks, Carsten 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 44 in xmonad: Support for i18n in window titles
by codesite-noreply＠google.com 06 Apr '08

06 Apr '08

Issue 44: Support for i18n in window titles http://code.google.com/p/xmonad/issues/detail?id=44 Comment #3 by dons00: matching on i18n window titles works in ManageHooks now. 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

3 2

Issue 43 in xmonad: Call setlocale at startup
by codesite-noreply＠google.com 06 Apr '08

06 Apr '08

Issue 43: Call setlocale at startup http://code.google.com/p/xmonad/issues/detail?id=43 Comment #8 by dons00: mauke has commited a tiny binding to setlocale, which is now called on startup. 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

1 0

darcs patch: XMonad.Main: call setlocale on startup (and 2 more)
by Lukas Mai 06 Apr '08

06 Apr '08

Sun Apr 6 03:12:34 CEST 2008 Lukas Mai <l.mai(a)web.de> * XMonad.Main: call setlocale on startup Sun Apr 6 03:13:38 CEST 2008 Lukas Mai <l.mai(a)web.de> * XMonad.ManageHook: make 'title' locale-aware; haddock cleanup The code for 'title' was stolen from getname.patch (bug #44). Sun Apr 6 03:20:06 CEST 2008 Lukas Mai <l.mai(a)web.de> * XMonad.ManageHook: add 'appName', another name for 'resource'

2 1

Floats always go to the current screen (Patch)
by Robert 05 Apr '08

05 Apr '08

When opening new floating windows on a multihead display, they will often unpredictably appear on a different screen to the one that currently has focus. Example: Bind a key to run 'gmrun'. Run gmrun from one screen and take note of which screen it appears on. Switch to another screen and do the same thing. gmrun will generally appear on the same screen each time. This seems unpredictable to me. I think new windows should always appear on the current workspace (unless it's transient perhaps). This allows me to, for example, choose which screen a new window appears on by switching to it first. In the current situation, I have to somehow remember where X prefers to launch an application and try to arrange my workspaces and screens such that the application will appear in the right location. This patch makes new float windows appear on the current screen as I think they should. The contrib patch makes contrib compatible with this change. I've undone some of the floating layer work in this patch. It seems the floating layer stuff was written explicitly to support the current way of placing floating windows. If there were good reasons for this functionality, please convince me my patch does the wrong thing. Otherwise, I think this patch has the benefit of being more predictable and simpler in code.

4 18