November 2008 - xmonad

Issue 236 in xmonad: XMonad.Prompt does not work in GHC 6.10
by codesite-noreply＠google.com 10 Nov '08

10 Nov '08

Issue 236: XMonad.Prompt does not work in GHC 6.10 http://code.google.com/p/xmonad/issues/detail?id=236 New issue report by SpencerJanssen: There have been a few reports of problems with XMonad.Prompt and GHC 6.10, but with no real details. We'll need a GHC 6.10 user to investigate this issue. Issue attributes: Status: Accepted Owner: ---- Labels: Milestone-Release0.9 Component-Contrib Priority-Critical -- 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 10 Nov '08

10 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #14 by sean.escriva: slock is nice lightweight screen locker, which may do what you need as well -- 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

[xmonad-contrib] darcs patch: SshShell Part 2
by Matt Brown 10 Nov '08

10 Nov '08

Moved escape function from Shell.hs to Prompt.hs, so SshShell.hs can use it. Also added comments regarding ControlMaster and passwordless requirement. This patch includes my last patch as well. Couldn't figure out how to make darcs NOT include it. -matt

1 0

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

10 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #13 by kralph: This happened again upon xscreensaver resume, but this time Firefox wasn't even running. I made some changes to my .xsession and xmonad.hs. If it happens again I'm going to try xlockmore instead of xscreensaver. -- 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 10 Nov '08

10 Nov '08

Issue 212: xmonad and xkb features http://code.google.com/p/xmonad/issues/detail?id=212 Comment #4 by mauricio.antunes: I'm now using xmonad 0.8 in Ubuntu 8.10. The problem is still there, in two different computers with different hardware. Maybe the priority of this should be raised. Not because of the problem itself, since very few people use a computer without a mouse, but because keyboard is probably the major issue in xmonad, and solving this bug may help solving others. -- 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 10 Nov '08

10 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #12 by mauricio.antunes: Adding my experience: I just had a keyboard freeze when using dmenu interrupted by a new late firefox window. (I believe I read somewhere this was a problem with earlier versions, now fixed.) It's interesting that, although after the usual Alt-SysRq-r trick, I was able to run 'xclock -display :0' as recomended in the FAQ. 'xclock' did start, but that didn't solve the problem. xmonad 0.8, Ubuntu 8.10. -- 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

Re: [xmonad] darcs patch: GridSelect
by Clemens Fruhwirth 10 Nov '08

10 Nov '08

At Mon, 10 Nov 2008 12:17:59 +0100, Dominik Bruhn wrote: > > [1 <text/plain; us-ascii (quoted-printable)>] > Hy Clemens, > can you perhaps drop some lines on the mailinglist how to use (or try out) the > gridselect-module for xmonad? Im not that familiar with the xmonad-code so a > small hint would help. I tried to add a keybinding ("((modm, xK_g), > gridselect defaultGSConfig)") but thats not the way I is supposed to work, is > it? Sorry, I have put my xmonad.hs line into the original mail that was swallowed by gmane, and I forget about it in the second. Try: , ((modMask', xK_f ), (gridselect defaultGSConfig) >>= (\w -> case w of Just w -> windows (bringWindow w) >> focus w >> windows W.shiftMaster Nothing -> return () as keybinding. That will forcefully raise/focus the window you selected with mod+F. -- Fruhwirth Clemens - http://clemens.endorphin.org

2 2

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

10 Nov '08

Issue 97: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 Comment #11 by kralph: I just had this problem also after resuming from an xscreensaver locked and dpms powersaved screen. Firefox happened to have the xmonad focus upon resume also. Firefox responded to keys, and I was able to exit Firefox. But upon exiting, the remaining windows on the desktop weren't retiled by xmonad. A Pidgin window was also on the desktop, and that responded to keys, but I couldn't mouse click anything. I couldn't figure out how to get xmonad to start responding normally again, so I had to Ctrl-Alt-Backspace out of X. Using xmonad 0.8 on Gentoo. -- 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

[kowey@darcs.net: Re: [darcs-users] darcs patch: Handle EOF exceptions from hReady, in accordance with ...]
by Don Stewart 09 Nov '08

09 Nov '08

I'm suspicious this also affects XMonad.Prompt with ghc 6.10 -- which behaves very oddly under that compiler. ----- Forwarded message from Eric Kow <kowey(a)darcs.net> ----- Date: Sun, 9 Nov 2008 21:35:43 +0000 From: Eric Kow <kowey(a)darcs.net> To: Petr Rockai <me(a)mornfall.net> Cc: darcs-users(a)darcs.net Subject: Re: [darcs-users] darcs patch: Handle EOF exceptions from hReady, in accordance with ... On Sun, Nov 09, 2008 at 22:08:45 +0100, Petr Rockai wrote: > could you please check whether this fixes the prompt issue with GHC 6.10.1? > It's completely untested wrt. actual 6.10, but it does typecheck and it seems > to pass the suite on 6.8. This passes tests indeed! Looks like we're ready for darcs 2.1.1rc1 after all :-D For the interested, the version of the base package that ships with GHC 6.10.1 fixes a bug http://hackage.haskell.org/trac/ghc/ticket/1063 which in turn confused our darcs code because it threw an exception we didn't know what to do with. Thanks! -- Eric Kow <http://www.nltg.brighton.ac.uk/home/Eric.Kow> PGP Key ID: 08AC04F9 _______________________________________________ darcs-users mailing list darcs-users(a)darcs.net http://lists.osuosl.org/mailman/listinfo/darcs-users ----- End forwarded message -----

1 0

Issue 228 in xmonad: OpenOffice fullscreen presentation is tiled
by codesite-noreply＠google.com 08 Nov '08

08 Nov '08

Issue 228: OpenOffice fullscreen presentation is tiled http://code.google.com/p/xmonad/issues/detail?id=228 Comment #3 by sean.escriva: fullscreen flash video is fixable using ManageHelpers from contrib: import XMonad.Hooks.ManageHelpers then add: composeOne [ isFullscreen -?> doFullFLoat ] to your ManageHook, probably worth trying with ooimpress -- 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