November 2008 - xmonad

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

15 Nov '08

Issue 237: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority] http://code.google.com/p/xmonad/issues/detail?id=237 Comment #1 by thomas.szczarkowski: It occured to me - if your terminal background color is light, you should probably change the highlight color from "yellow" to something darker. -- 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 15 Nov '08

15 Nov '08

Issue 237: focusedBorderColor sometimes fails to follow focus after a window shuffle [low priority] http://code.google.com/p/xmonad/issues/detail?id=237 New issue report by thomas.szczarkowski: What steps will reproduce the problem? 1. Install the trivial xmonad.hs that is attached 2. Open an empty workspace: alt+[num] 3. Open two terminals: ctrl+shift+Enter twice (NB - no more than two windows, otherwise the bug may not appear!) 4. Shuffle with mod-shift-J. What is the expected output? What do you see instead? The focused window's border should be 'focusedWindowBorder'; instead it is 'normalWindowBorder'. The shuffle operation does not correctly update the window border colors. What version of the product are you using? On what operating system? 0.8, on Ubuntu 8.04/amd64 Attachments: xmonad.hs 120 bytes Issue attributes: Status: New Owner: ---- -- 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 212 in xmonad: xmonad and xkb features
by codesite-noreply＠google.com 14 Nov '08

14 Nov '08

Issue 212: xmonad and xkb features http://code.google.com/p/xmonad/issues/detail?id=212 Comment #6 by mauricio.antunes: Interesting! As I said, I only have this problem with xmonad, never with other window managers. However, it seems I never left the mouse for 120 seconds outside xmonad. After 'xkbset exp =m' everything works as expected. Thanks! Problem solved. -- 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 212 in xmonad: xmonad and xkb features
by codesite-noreply＠google.com 13 Nov '08

13 Nov '08

Issue 212: xmonad and xkb features http://code.google.com/p/xmonad/issues/detail?id=212 Comment #5 by hpnpwd: This problem seems no to be a bug of xmonad, but the feature of XKB. In default, the MouseKeys of XKB expires in 120 second (try "xkbset q exp"). You can change this expire time by executing "xkbset exp [TIME_IN_SECONDS]" Also, you can set MouseKeys not to expire by executing "xkbset exp m". But however, xkbset seems not to work in Ubuntu 8.04. So I updated to Ubuntu 8.10, then now xkbset works. -- 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

using xosd to indicate screen focus
by Don Stewart 13 Nov '08

13 Nov '08

I've been experimenting with using the xosd lib for visual clues as to which screen has focus on xinerma set ups (something that brings grief and confusion to new users!) An example, http://galois.com/~dons/images/screen-xosd.png The idea would be for an xmc extension with hooks into xosd, so you could write text and other fun things this way, with the first application being a view hook. Thoughts? Seems worth pursuing? -- Don

5 6

Issue 233 in xmonad: broken link on website
by codesite-noreply＠google.com 13 Nov '08

13 Nov '08

Issue 233: broken link on website http://code.google.com/p/xmonad/issues/detail?id=233 Comment #1 by vogt.adam: I think that this is the same haddock bug as in issue 201 -- 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 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 13 Nov '08

13 Nov '08

Issue 226: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 Comment #2 by vogt.adam: Similar results with 6.10.1, also with gridSelect See those similar, but not exactly the same x11 errors attached: Attachments: error 3.4 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 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 12 Nov '08

12 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #16 by kralph: I also had this (like Comment 15) happen once while working. I think I was also in Firefox at the time. I'm back to using xscreensaver, and so far I haven't had this problem again though. I still have no idea what causes it. It seems random so far. -- 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: GridSelect
by Clemens Fruhwirth 12 Nov '08

12 Nov '08

Hi everyone, Here is my little GridSelect toy. I don't think it's polished enough to go into contrib, but as I was asked about it when I posted a screenshot on IRC, I thought that I don't want to hold it back until I found time to polish it. http://clemens.endorphin.org/gridselect.png GridSelect brings up a 2D grid of windows in the center of the screen, and I can select a window with cursors keys. The window is delivered back to the caller of GridSelect, and for the moment the most useful thing it does for me is to raise and focus the selected window. The advantage over the presentation of Tabbed is that there is much more space for window titles, that are now not forced into a single row at the top of the screen, but can occupy multiple rows. Also navigating a 2D grid is also much faster than navigating a linear 1D structure. GridSelect colorizes the cells according to the window class of displayed window. So, all windows with the same class get the same color, and after a while I start to remember which window class has which color. E.g., when I want my xchat window, I just have to search for light green, or if I want an emacs windows, I have to focus on dark violet. There are a few ideas that I haven't found time to toy with. First I like the window arrangement to be more static. At the moment, the windows are sorted (by XMonad) according to its last use and GridSelect arranges them spiraling outwards in a diamond like pattern. Mentally, I can only keep track of the usage history to the depth of 2-3 for blindly selecting window. For everything else, I have to read titles. It would be more helpful to give fixed spots to windows. Of course, windows get deleted and new windows pop up all the time. Probably it would be good to defragment/sort by display time upon a key press. Substring search on window titles is another idea. As GridSelect uses cursor keys for the moment, the rest of the keyboard could be used to enter the string used in searching. GridSelect should then gray out the windows that do not contain the search term. Thanks to the community for XMonad, Fruhwirth Clemens - http://clemens.endorphin.org

5 4

Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 12 Nov '08

12 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #15 by greg.burri: I have a similar behavior here. Sometimes after 2-3 hours using xmonad, it doesn't respond anymore. It's like the MOD key is broken, I can't change to an another Desktop (MOD-1/2..), I can't switch between application (MOD-Tab) and I can't launch new application (MOD-p). The mouse and the keyboard works, I can use it in the current application. I can also switch to a virtual terminal with (CTRL-ALT-1/2..). The latest time I used it I was in Firefox but I don't remember the details :( I Use the Win key for MOD. Here is my configuration : - xmonad 0.8 - xorg 7.3+18 - Debian sid with GNU/Linux 2.6.26-1 #1 SMP - DELL XPS 1330 (core2duo) -- 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