December 2008 - xmonad

Issue 205 in xmonad: I would like wiggling mouse to select window its over.
by codesite-noreply＠google.com 17 Dec '08

17 Dec '08

Comment #6 on issue 205 by mbsullivan: I would like wiggling mouse to select window its over. http://code.google.com/p/xmonad/issues/detail?id=205 Is there a fix for this issue? It seems like something that is reasonable, and I recall running into it while using a mouse before. A focus-follows-mouse where the window underneath the mouse pointer is ALWAYS focused would be the most logical for a mouse user, it seems to me. Mike -- 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 199 in xmonad: Prompt.AppendFile crashes when file is not writable
by codesite-noreply＠google.com 17 Dec '08

17 Dec '08

Comment #7 on issue 199 by domi...(a)dbruhn.de: Prompt.AppendFile crashes when file is not writable http://code.google.com/p/xmonad/issues/detail?id=199 I checked the following: sshPrompt and a non-existing or a non-readable .known_hosts appendFiled and a non-writable file both work fine, (sshPrompt doesnt appear and appendFile fails silently), so no crash at all. Can anybody please check this for his config, so we can perhaps close the bug? -- 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 244 in xmonad: .xmonad/history permissions may allow information leakage
by codesite-noreply＠google.com 17 Dec '08

17 Dec '08

Comment #1 on issue 244 by domi...(a)dbruhn.de: .xmonad/history permissions may allow information leakage http://code.google.com/p/xmonad/issues/detail?id=244 I submited a patch fixing this error seconds ago. Check it out and then mark this bug as done. -- 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 210 in xmonad: xmonad.hs not accepted, xmonad.errors empty
by codesite-noreply＠google.com 17 Dec '08

17 Dec '08

Comment #6 on issue 210 by drew666: xmonad.hs not accepted, xmonad.errors empty http://code.google.com/p/xmonad/issues/detail?id=210 The same empty xmonad.errors bug exists when xmonad 0.8 compiled from source tarball on OSX 10.5.5. Sorry for bumping this, but could someone mention what the missing dependency is here? I am still new to all this Haskell stuff. Is this as simple as finding a libghc6-xmonad-dev.tar.gz? PS. I see the same "error detect while loading xmonad configuration file: /Users/me/.xmonad/xmonad.hs Please check the file for errors. /Users/me/.xmonad/xmonad-i386-darwin: executeFile: does not exist (No such file or directory) -- 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 247 in xmonad: SmartBorders fails for fullscreen mplayer when there are no other windows present
by codesite-noreply＠google.com 17 Dec '08

17 Dec '08

Comment #3 on issue 247 by domi...(a)dbruhn.de: SmartBorders fails for fullscreen mplayer when there are no other windows present http://code.google.com/p/xmonad/issues/detail?id=247 Duplicate of 223, fixed by Sun Oct 5 20:44:26 CEST 2008 Joachim Breitner <mail(a)joachim-breitner.de> * SmartBorders even for empty layouts Fixes: http://code.google.com/p/xmonad/issues/detail?id=223 darcs patch, which isnt included in 0.8 release. You got two options: - Wait for the 0.9 release - Update to darcs version and compile yourself. Admins: Please tag as dup. -- 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

Fedora 10, Gnome and Xmonad
by Jan Müller 17 Dec '08

17 Dec '08

(Warning: As pointed out below my knowledge of Haskell, Xmonad and Linux is very limited, so please bear with me) Short version: ------ Getting xmonad up and running under Fedora 10 in combination with Gnome is not straightforward. After several hours I found a solution which is posted below. It would be nice if someone would update the Wiki page accordingly. Longer version: ------ Hi, I hope it's ok to post stuff like this on the mailing list: During the last two days I had severe problems getting xmonad up and running under a freshly installed Fedora 10. A few minutes ago I was able to solve the problem and now I want to share experiences in the hope that it will be useful for people having the same problem. Additionally, it would be really nice if someone would take the following information, put them into a nicer form and then update [1] (I could do this myself but since I'm more a less a complete Linux-, Haskell-, and Xmonad-noob, I think a more experienced person could do a much better job) So, what went wrong? First I was looking for precompiled packages for 64bit Fedora 10 but in the end I had to compile everything by myself. After an hour or so I got a file called xmonad in /usr/local/bin/. In order to test it I did a killall metacity; xmonad & with the old xmonad.hs from my previous Ubuntu installation. Besides some cryptic warnings (in the console window where I startedxmonad) everything worked fine. (I could not find any occurence of these warnings anywhere, so if someone is interested I can have a second look and post them on the list) After this the real trouble begun: Essentially all available tips on how to replace metacity with xmonad (or any other window manager) do _not_ work under Fedora 10! Some things I tried: - .gnomerc - .xinit / .xsession - the stuff described under "2.2 gnome-session" on [1] - some stuff mentioned in [2] While reading [2] I got the impression that this problem is not restricted to xmonad. After searching some more I stumbled onto the first three paragraphs on [3]. Unfortunately the tips given there are not complete, but after finding [4] I was able to combine both approaches and make it work (at least for me) :) First step: ------ create a file called Xmonad.desktop in /usr/share/applications which contains the following: [Desktop Entry] Type=Application Encoding=UTF-8 Name=Xmonad # change this path according to your xmonad binary Exec=/usr/local/bin/xmonad NoDisplay=true X-GNOME-WMName=Xmonad X-GNOME-Bugzilla-Bugzilla=XMonad X-GNOME-Bugzilla-Product=xmonad X-GNOME-Bugzilla-Component=general X-GNOME-Autostart-Phase=WindowManager X-GNOME-Provides=windowmanager X-GNOME-Autostart-Notify=true I copied Metacity.desktop and replaced some lines. I'm sure some of these lines can be removed but since this works for me without any problems I'm not going to put more time in this. Second step: ------ Use gconf2 or gconf-edit to set /desktop/gnome/applications/window_manager to "xmonad" It seems that this key is deprecated (see [3]) but (at least for me) it's the only way to get it work. Final steps: ------ Log out, log in, and (hopefully) enjoy xmonad If someone has an easier/better solution to this problem, please tell me :) Thanks for all your work on xmonad, Jan [1] http://www.haskell.org/haskellwiki/Xmonad/Using_xmonad_in_Gnome [2] http://newsgroups.derkeiler.com/Archive/Uk/uk.comp.os.linux/2008-10/threads… [3] http://www.haskell.org/haskellwiki/Talk:Xmonad/Using_xmonad_in_Gnome [4] http://n2.nabble.com/Is-Gnome-windown-manager-switching-broken-again--td139…

3 2

Issue 237 in xmonad: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority]
by codesite-noreply＠google.com 16 Dec '08

16 Dec '08

Comment #3 on issue 237 by lit...(a)hethrael.org: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority] http://code.google.com/p/xmonad/issues/detail?id=237 I recently started noticing this--perhaps beginning a week ago. I haven't upgraded xmonad in a while, so it might be a side effect of upgrading something else (I know I recently upgraded Xorg). I am running xmonad 0.8 in Arch Linux on amd64. I can reproduce this with two or more windows. Of the programs I run, urxvt seems to trigger it the most. I reproduced it with multiple xlogos in a workspace as well, so it's not just an urxvt issue. I also sometimes see horizontal and vertical lines in my urxvt windows when windows change size (by opening or closing a terminal or pressing Mod+H). These lines are normalWindowBorder color. I am attaching a screenshot after I opened fourteen terminal windows and then closed seven of them. Steps to Reproduce 1. Open at least two urxvt windows in a Tall workspace. 2. Focus the last window in the workspace (it seems to affect the last window the worst). 3. Press Mod+Shift+K. Result The last window and the next to last window are both drawn with the focusedWindowBorder border color. More Steps to Reproduce 4. The next-to-last window is currently focused. 5. Press Mod+Shift+J. Result No window is currently drawn with the focusedWindowBorder border color. However, the last window does have focus. Attachments: urxvt-lines.png 44.3 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

Issue 237 in xmonad: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority]
by codesite-noreply＠google.com 16 Dec '08

16 Dec '08

Updates: Status: Invalid Comment #2 on issue 237 by SpencerJanssen: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority] http://code.google.com/p/xmonad/issues/detail?id=237 Sorry, I can't reproduce this. We'll need more detailed steps to reproduce to act on 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 247 in xmonad: SmartBorders fails for fullscreen mplayer when there are no other windows present
by codesite-noreply＠google.com 15 Dec '08

15 Dec '08

Comment #2 on issue 247 by j...(a)kitenet.net: SmartBorders fails for fullscreen mplayer when there are no other windows present http://code.google.com/p/xmonad/issues/detail?id=247 Here is my xmonad.hs, with which I see the problem. Attachments: xmonad.hs 5.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 0

announce: XMonad.Layout.Monitor
by Roman Cheplyaka 15 Dec '08

15 Dec '08

XMonad.Layout.Monitor is module for managing 'monitor' windows. Monitor windows are like dock windows, but they are placed above other windows. For example, see screenshot[1]. 'Monitor' is layout modifier which shows monitor window above the tiled windows of current layout. Its features are: - works with unmanaged windows ( => it's trivial to get monitor on all workspaces, plus monitor never gets focus) - toggling visibility with a keybinding - it's possible to have several monitors and toggle them independently (using nested modifiers) Due to stacking algorithm of xmonad, it isn't currently possible to show monitor above floating windows. For details, please see the docs. Comments are welcome. 1. http://www.haskell.org/haskellwiki/Image:Xmonad-clock.png -- Roman I. Cheplyaka (aka Feuerbach @ IRC)

4 4