- xmonad - Haskell.org

Re: Issue 168 in xmonad: gnome-panel with autohide enabled appears behind main windows
by codesite-noreply＠google.com 07 Aug '14

07 Aug '14

Comment #5 on issue 168 by govnototalitarizm: gnome-panel with autohide enabled appears behind main windows http://code.google.com/p/xmonad/issues/detail?id=168 gwern0 do not work with latest xmonad. This issue is a major stopover for me to migrate to xmonad.

1 5

xmonad hides xfce4-panel
by Damian Philipp 07 Aug '14

07 Aug '14

Hello xmonad experts, I am trying to set up xmonad (0.11 from Ubuntu repository) as a WM for xfce on a fresh install of Lubuntu 14.04. I configured xmonad.hs as instructed on the Wiki page (The file is so short, I included it inline at the end of this mail). When I start xfce using xfwm4 and then run "xmonad --replace" from a terminal, I practically arrive at my dream desktop. However, when I configure xfce to autostart xmonad, I can briefly see the xfce4 panel flash up and then immediately disappear. xmonad just leaves an empty space where the panel is supposed to be. mod-b toggles the empty space but does not show the panel. The default configuraiton of Lubuntu is to have a single panel at the top of the screen. I can revive the panel by briefly running xfwm4: $ killall xmonad-x86_64-linux $ xfwm4 $ xmonad --replace But that is not really a permanent solution. I looked through the archives, but all I cloud find was posts relating to the interaction of the panel workspace indicator and xmonad workspaces, nothing about the panel going AWOL. What do I have to do to make both the panel show up and run xmonad as my default WM to xfce? Regards, Damian Philipp My xmonad.hs: > import XMonad > import XMonad.Config.Xfce > > main = xmonad xfceConfig > { modMask = mod4Mask > , terminal = "xfce4-terminal" }

4 4

Issue 348 in xmonad: Encoding task force
by codesite-noreply＠google.com 05 Aug '14

05 Aug '14

Status: New Owner: ---- Labels: Type-Enhancement New issue 348 by SpencerJanssen: Encoding task force http://code.google.com/p/xmonad/issues/detail?id=348 xmonad is sloppy about strings and encoding. We should go through all of xmonad and make sure all code follows these guidelines: * All String ([Char]) values should be lists of Unicode code points, and should NOT be in UTF-8 or any other encoded form. * All input that creates String values should decoded from bytes in whatever encoding to a lists of code points (this means System.IO and proper locale settings in GHC 6.12, System.IO.UTF8 in older) * All output that takes String values should encode the code points to bytes in whatever encoding (again System.IO in 6.12, utf8-string otherwise) * All non-string data (lists of bytes, encoded strings, etc.) should be stored at types other than [Char] If anybody wants to spearhead this, feel free to come forward. Alternatively we could have maintainers self-certify their modules? -- 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 11

Issue 575 in xmonad: Typo on web page
by codesite-noreply＠google.com 05 Aug '14

05 Aug '14

Status: New Owner: ---- New issue 575 by rrt(a)sc3d.org: Typo on web page http://code.google.com/p/xmonad/issues/detail?id=575 xmonad.org/tour.html "ito" → "into" -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

darcs patch: config-mate
by allbery.b＠gmail.com 03 Aug '14

03 Aug '14

** tested version ** 1 patch for repository http://code.haskell.org/XMonadContrib: Sat Aug 2 22:06:59 EDT 2014 allbery.b(a)gmail.com * config-mate Initial support for the Mate desktop environment (http://mate-desktop.org) Based on existing Gnome 2 support, since Mate is a maintained fork of Gnome 2.

1 0

darcs patch: debug-managehook
by allbery.b＠gmail.com 03 Aug '14

03 Aug '14

** tested version ** 1 patch for repository http://code.haskell.org/XMonadContrib: Sat Aug 2 22:06:01 EDT 2014 allbery.b(a)gmail.com * debug-managehook A set of hooks, and convenience combinators, to help with ManageHook debugging. Ordinary users may well want to use debugManageHookOn in normal configs, specifying a key sequence which can be pressed before running a command in order to capture debug information just for that command's main window. This is especially useful when trying to diagnose issues such as programs that do not play well with SpawnOn, or ManageHook matching on 'title' when the program does not set the window title until after it is mapped.

1 0

darcs patch: debug-debug
by allbery.b＠gmail.com 03 Aug '14

03 Aug '14

** tested version ** 1 patch for repository http://code.haskell.org/XMonadContrib: Sat Aug 2 22:05:30 EDT 2014 allbery.b(a)gmail.com * debug-debug Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug requires these fixes, but some of them are significant even if not using ManageDebug.

1 0

darcs patch: debug-managehook
by allbery.b＠gmail.com 03 Aug '14

03 Aug '14

1 patch for repository http://code.haskell.org/XMonadContrib: Sat Aug 2 21:51:24 EDT 2014 allbery.b(a)gmail.com * debug-managehook A set of hooks, and convenience combinators, to help with ManageHook debugging. Ordinary users may well want to use debugManageHookOn in normal configs, specifying a key sequence which can be pressed before running a command in order to capture debug information just for that command's main window. This is especially useful when trying to diagnose issues such as programs that do not play well with SpawnOn, or ManageHook matching on 'title' when the program does not set the window title until after it is mapped.

2 1

darcs patch: debug-debug
by allbery.b＠gmail.com 03 Aug '14

03 Aug '14

1 patch for repository http://code.haskell.org/XMonadContrib: Sat Aug 2 21:49:01 EDT 2014 allbery.b(a)gmail.com * debug-debug Various fixes and enhancements to DebugWindow and DebugStack. ManageDebug requires these fixes, but some of them are significant even if not using ManageDebug.

1 0

Issue 531 in xmonad: Multiple workspaces with the same name confuses XMonad
by codesite-noreply＠google.com 14 Jul '14

14 Jul '14

Status: New Owner: ---- New issue 531 by erdnussb...(a)gmail.com: Multiple workspaces with the same name confuses XMonad http://code.google.com/p/xmonad/issues/detail?id=531 What is the expected output? What do you see instead? I expect that xmonad differs between workspaces even if they have the same name. The following describes the scenarios you run into when naming multiple workspaces identically. ------------------- Scenario 1: ------------------- How to produce: 1. Give some workspaces the same name. 2. Restart and recompile XMonad. What happens: The renamed workspaces are added uselessly to the beginng of the list. (see picture 1.png) ------------------- Scenario 2: ------------------- How to produce: 1. Start from scenario 1. 2. Restart X. What happens: XMonad shows all the workspaces separately but addresses them as one (see picture 2.png). Additional information: If you switch between two workspaces with the same name, xmonad loads the content again (you see it flicker) but the content is the same. ------------------- Scenario 3a: ------------------- How to produce: 1. Start from scenario 2. 2. Change one of the former identical workspace names to something unique. 3. Recompile and restart XMonad. What happens: XMonad displays mutliple times the unique name?! (see picture 3a.png) Additional information: From this point on, recompiling and restarting doesn't fix the corruption of the running XMonad session. ------------------- Scenario 3b: ------------------- How to produce: 1. Start from Scenario 3a 2. Restart X What happens: The multiple workspaces are shown again, still addresses as one, but the uniquely named workspace is displayed and addressed correctly. (see picture 3b.png) ------------------- Scenario 3c: ------------------- How to produce: 1. Start from Scenario 3b. 2. Change all workspace names to something unique again. 3. Recompile and Restart Xmonad. What happens: The doesn't have the intended effect, instead some workspace keys stop working and a random one is shown mutliple times. (see picture 3c.png) Restarting X fixes this issue. 4. Start with Scenario 1 again, it's fun (: ------------------- What version of the product are you using? On what operating system? Linux ******* 3.2.0-4-amd64 #1 SMP Debian 3.2.35-2 x86_64 GNU/Linux (wheezy) xmonad 0.10 ------------------- Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Yes I'm using it, there are no compilation errors. ------------------- Please provide any additional information below. Dzen2 and Xmobar showed the same effects. Attachments: 1.png 116 KB 2.png 122 KB 3a.png 137 KB 3b.png 115 KB 3c.png 116 KB xmonad.hs 10.8 KB

1 4