December 2008 - xmonad

Issue 210 in xmonad: xmonad.hs not accepted, xmonad.errors empty
by codesite-noreply＠google.com 03 Dec '08

03 Dec '08

Comment #5 on issue 210 by grapescan: xmonad.hs not accepted, xmonad.errors empty http://code.google.com/p/xmonad/issues/detail?id=210 The same bug exists on Debian4.0r5 -- 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

XMonadContrib -Werror build currently broken with GHC 6.10
by Gwern Branwen 03 Dec '08

03 Dec '08

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 .... [101 of 140] Compiling XMonad.Config.PlainConfig ( XMonad/Config/PlainConfig.hs, dist/build/XMonad/Config/PlainConfig.o ) XMonad/Config/PlainConfig.hs:235:9: Warning: orphan instance: instance Error [(Integer, String)] Oops. I ran into this on the record-test. So do we suggest 6.10 developers just use --no-test or what? - -- gwern -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.9 (GNU/Linux) iEYEAREKAAYFAkk14y4ACgkQvpDo5Pfl1oJkmgCaA6+l2M/drKPag3B6zL171vhk uKMAn0TGac5UduGxGTJCEiwWcRDfYcRZ =8lgW -----END PGP SIGNATURE-----

4 3

darcs patch: XMonad.Prompt: swap up and down per bug #243
by gwern0＠gmail.com 03 Dec '08

03 Dec '08

Tue Dec 2 20:33:23 EST 2008 gwern0(a)gmail.com * XMonad.Prompt: swap up and down per bug #243

2 1

Issue 243 in xmonad: shellPrompt history keybinding problems
by codesite-noreply＠google.com 02 Dec '08

02 Dec '08

Comment #1 on issue 243 by gwern0: shellPrompt history keybinding problems http://code.google.com/p/xmonad/issues/detail?id=243 This seems to be generic to the various Prompts, not just shellPrompt. I agree that this is a error; Prompt has no reason to reverse the usual bindings. Up should give one the most recent. I have sent in a patch doing just this. -- 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 02 Dec '08

02 Dec '08

Comment #21 on issue 97 by sharma.animesh: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 My laptop is Dell Latitute D630 running Ubuntu 8.10, ghc 6.8.2, xmonad 0.8 (compiled from source), i686 I really want to stick to xmonad, but restarting is a bit frustrating. -- 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 02 Dec '08

02 Dec '08

Comment #20 on issue 97 by sharma.animesh: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I get the similar problem. This generally happens when I am watching a video inside firefox using adobe-flash-player or video in general using vlc/mplayer. The Mod key (mapped to Windows keys Mod4) stops working but the keyboard is fully functional in the present focus window. I have to restart x using ctrl-alt-backspace to get out. Sometimes it happens just like that, with no pattern what so ever. -- 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 02 Dec '08

02 Dec '08

Comment #19 on issue 97 by sharma.animesh: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 import XMonad import XMonad.Hooks.DynamicLog import XMonad.Hooks.ManageDocks import XMonad.Util.Run(spawnPipe) import XMonad.Util.EZConfig(additionalKeys) --import XMonad.Actions.Warp import System.IO import Data.Ratio --myManageHook = composeAll [ -- className =? "Gimp" --> doFloat, -- className =? "Vncviewer" --> doFloat -- ] main = do xmproc <- spawnPipe "/usr/local/bin/xmobar /home/ash022/.xmonad/xmobar" xmonad $ defaultConfig { manageHook = manageDocks <+> -- myManageHook <+> manageHook defaultConfig, layoutHook = avoidStruts $ layoutHook defaultConfig, logHook = dynamicLogWithPP $ xmobarPP { ppOutput = hPutStrLn xmproc , ppTitle = xmobarColor "orange" "" . shorten 50 } , modMask = mod4Mask -- Rebind Mod to the Windows key } `additionalKeys` [ ((mod4Mask .|. shiftMask, xK_z), spawn "xscreensaver-command -lock"), ((controlMask, xK_Print), spawn "scrot -s"), ((0, xK_Print), spawn "scrot") -- , ((mod4Mask .|. shiftMask, xK_q ), warpToWindow (1%2) (1%2)) ] -- 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 243 in xmonad: shellPrompt history keybinding problems
by codesite-noreply＠google.com 02 Dec '08

02 Dec '08

Status: New Owner: ---- New issue 243 by A...(a)informationoverflow.net: shellPrompt history keybinding problems http://code.google.com/p/xmonad/issues/detail?id=243 What steps will reproduce the problem? 1. open your shellPrompt 2. click arrow key up What is the expected output? What do you see instead? Normally you should see the last entered command... instead you'll get the command you entered on the very beginning. It seems arrow key up and down are switched. What version of the product are you using? On what operating system? I'm using xmonad darcs on debian etch. My architecture is i386. If this error is due to a module from XMonadContrib, please tag this issue with 'Component-Contrib' below. 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

darcs patch: Fix boolean operator precedence in GridSelect keybindings
by Aleksandar Dimitrov 01 Dec '08

01 Dec '08

Mon Dec 1 13:09:28 CET 2008 Aleksandar Dimitrov <aleks.dimitrov(a)googlemail.com> * Fix boolean operator precedence in GridSelect keybindings The vim-like hjkl keys were ORed to the key event AND arrow keys.

2 1

xmonad doesn't seem to produce any errors if .xmonad/xmonad.hs has no 'main'
by Ian Kilgore 01 Dec '08

01 Dec '08

I can't haskell my way out of a paper bag, but the config file is obvious enough that I've been able to make the tweaks I wanted without trouble.. Installing 0.8 on this box after having not used xmonad for a while, I was an ignorant user and assumed I could copy XMonad/Config.hs to .xmonad/xmonad.hs and edit it (last time I used xmonad, configuration was editing Config.hs in place before building, so this wasn't much of a stretch..) No main in the Config.hs, so xmonad-i386-linux was never built, only xmonad.o. While this was obviously user error, it seems unhelpful that the only error message produced at all was the one telling me that executeFile couldn't run xmonad-i386-linux. xmonad --recompile produced no output, and while it created xmonad.errors, the file was empty. It'd be swell if xmonad reported errors when it fails to produce an executable; hardly a bug, but it couldn't hurt.. -- Ian Kilgore print/42; # n/,"Just another Perl hacker,\n"

1 0