December 2008 - xmonad

Issue 253 in xmonad: Dual head without xinerama doesn't work
by codesite-noreply＠google.com 28 Dec '08

28 Dec '08

Status: New Owner: ---- New issue 253 by korgulec: Dual head without xinerama doesn't work http://code.google.com/p/xmonad/issues/detail?id=253 If a dualhead setup without xinerama is used then xmonad fails to see the other screen. Running DISPLAY=":0.1" xterm opens a new xterm window on secondary screen, but it can't be focused. Seems that xmonad is using only default screen, and is not querying for all possible screens. xmonad version - 0.8 -- 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 28 Dec '08

28 Dec '08

Comment #26 on issue 97 by allbery.b: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 The preceding is because the pipe to xmobar is filling up and blocking, because xmonad is generating output faster than xmobar is consuming it. It might be worth setting stdout to nonblocking; otherwise, fork a thread to handle the log output (and compile with -threaded). -- 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 28 Dec '08

28 Dec '08

Comment #25 on issue 97 by greg.burri: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I can reproduce it like that : 1. After logon pop two terminals (xterm for me) with two MOD-SHIFT-ENTER 2. Continuously switch between both by pressing MOD-TAB After ~50 sec the issue will appear and xmonad will stop to respond. If I comment theses lines from my config it seems the issue won't appear anymore : -- logHook = dynamicLogWithPP $ xmobarPP {ppOutput = hPutStrLn xmproc -- ,ppTitle = xmobarColor "green" "" . shorten 50 -- } My config is the same that the Step-by-step tutorial : http://haskell.org/haskellwiki/Xmonad/Config_archive/John_Goerzen%27s_Confi… -- 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] Configuring XMonad.Layout.Monitor
by Roman Cheplyaka 27 Dec '08

27 Dec '08

* Richard Riley <rileyrgdev(a)googlemail.com> [2008-12-27 22:20:02+0100] > > Roman Cheplyaka <roma(a)ro-che.info> writes: > > > In order to simplify understanding and configuration of Monitor > > extension, I made these (backwards-incompatible) changes: > > - remove a bunch of add*Monitor functions > > - added some new, so now monitor can be configured using three steps: > > > > 1. Define Monitor record. 'monitor' can be used as a template, so if you > > don't need some features (opacity, named monitors) or you're ok with > > default values you may not define corresponding fields (or even know > > about them). > > > > clock = monitor > > { prop = ClassName "Cairo-clock" `And` Title "MacSlow's Cairo-Clock" > > , rect = (Rectangle (1280-150) (800-150) 150 150) > > , persistent = True > > , opacity = 0xAAAAAAAA > > } > > > > 2. Add ManageHook to de-manage monitor windows and apply opacity settings. > > > > manageHook = myManageHook <+> manageMonitor clock > > > > 3. Apply layout modifier. > > > > myLayouts = ModifiedLayout clock $ ... > > > > Please see updated documentation for details. > > > > To users who have already configured their monitors: all you need to > > change is layout (define monitor and use ModifiedLayout instead of > > addMonitor). You may leave manageHook as it is and it will work. > > So conversion should be pretty easy. Sorry for the inconvenience. > > This might be a silly question (not familiar with Haskell too well), but > why not simply "register" Monitor objects in the monitor creation and > then add a single hook and layout? > > e.g something along the lines of (not real haskell!) > > monitor( prop = Title "xclock" > , rect = (Rectangle (1280-150) (800-150) 150 150) > , persistent = True > , opacity = 0xAAAAAAAA > ) > > monitor( prop = ClassName "procman" > , rect = (Rectangle (1280-150) (800-150) 150 150) > , persistent = True > , opacity = 0xAAAAAAAA > ) > > myLayouts = monitors $ ... > > and > > manageHook = monitorsHook <+> > > > or is there a good reason to add each monitor to hooks and layouts > separately? Registering Monitor objects in the monitor creation is not possible because Haskell is declarative pure language. Actually these statements do not _create_ anything, they just _define_ monitors which you may (or may not) use later. We prefer to be explicit about any possible effects. This is the general reason. Another reason is that you may apply different monitors to different layouts. However, you can gather all defined monitors into a list (call it 'monitors') and define something like monitorsLayoutModifier = foldr (.) id $ map ModifiedLayout $ monitors monitorsManageHook = composeAll monitors and then have what you wanted: myLayouts = monitorsLayoutModifier $ ... manageHook = monitorsManageHook <+> If this way is more convenient for you, I can add these functions monitorsLayoutModifier and monitorsManageHook into the module. -- Roman I. Cheplyaka :: http://ro-che.info/ "Don't let school get in the way of your education." - Mark Twain

1 0

Configuring XMonad.Layout.Monitor
by Roman Cheplyaka 26 Dec '08

26 Dec '08

In order to simplify understanding and configuration of Monitor extension, I made these (backwards-incompatible) changes: - remove a bunch of add*Monitor functions - added some new, so now monitor can be configured using three steps: 1. Define Monitor record. 'monitor' can be used as a template, so if you don't need some features (opacity, named monitors) or you're ok with default values you may not define corresponding fields (or even know about them). clock = monitor { prop = ClassName "Cairo-clock" `And` Title "MacSlow's Cairo-Clock" , rect = (Rectangle (1280-150) (800-150) 150 150) , persistent = True , opacity = 0xAAAAAAAA } 2. Add ManageHook to de-manage monitor windows and apply opacity settings. manageHook = myManageHook <+> manageMonitor clock 3. Apply layout modifier. myLayouts = ModifiedLayout clock $ ... Please see updated documentation for details. To users who have already configured their monitors: all you need to change is layout (define monitor and use ModifiedLayout instead of addMonitor). You may leave manageHook as it is and it will work. So conversion should be pretty easy. Sorry for the inconvenience. -- Roman I. Cheplyaka (aka Feuerbach @ IRC)

1 0

Issue 226 in xmonad: XMonad.Prompt lockups with ghc 6.10
by codesite-noreply＠google.com 25 Dec '08

25 Dec '08

Comment #11 on issue 226 by wirtwolff: XMonad.Prompt lockups with ghc 6.10 http://code.google.com/p/xmonad/issues/detail?id=226 xmobar-0.9 and xmobar-darcs also trigger similar error when xmobar is run from cli or spawned in xmonad.hs. These were xmobars compiled with ghc-6.10.1 on two different 64-bit gentoo systems. Reverting to ghc-6.8.3 and rebuilding haskell bits makes prompt/showWS/decorations/xmobar work again. -- 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

Do I need a Desktop Environment?
by Leon 25 Dec '08

25 Dec '08

Hi, I know you need X to install XMonad, but can you run it without a desktop environment (like Gome or KDE etc...)?

2 1

Issue 168 in xmonad: gnome-panel with autohide enabled appears behind main windows
by codesite-noreply＠google.com 24 Dec '08

24 Dec '08

Comment #3 on issue 168 by gwern0: gnome-panel with autohide enabled appears behind main windows http://code.google.com/p/xmonad/issues/detail?id=168 bogner suggested in #xmonad that the (relatively) new module Layout.Monitor might offer a way to hack around this issue. I can finally confirm that yes, it actually does. My modifications to my xmonad.hs looked like: hunk ./.xmonad/xmonad.hs 14 +import XMonad.Layout.Monitor (addMonitor, Property(ClassName)) hunk ./.xmonad/xmonad.hs 28 - , layoutHook = avoidStruts $ smartBorders (Full || | Mirror tiled ||| tiled ) + , layoutHook = hideGnome $ avoidStruts $ smartBorders $ (Full ||| Mirror tiled ||| tiled ) hunk ./.xmonad/xmonad.hs 37 + hideGnome = addMonitor (ClassName "gnome-panel") (Rectangle 0 0 0 0) hunk ./.xmonad/xmonad.hs 48 - className =? "Darwinia" --> unfloat ] + className =? "Darwinia" --> unfloat, + className =? "gnome-panel" --> doIgnore ] Follow that by a restart of gnome-panel, and one gets a nicely autohidden gnome-panel which slides up over one's tiled windows on request. I have no comments on bogner's patches, though. They may still be warranted even if one can hack around in this specific instance. -- 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 251 in xmonad: mono applications not working under xmonad
by codesite-noreply＠google.com 23 Dec '08

23 Dec '08

Comment #5 on issue 251 by SpencerJanssen: mono applications not working under xmonad http://code.google.com/p/xmonad/issues/detail?id=251 > what exactly is "the default xmonad config"? The default configuration is used when there is no ".xmonad" directory -- ie. the configuration without any user customizations. -- 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 252 in xmonad: xmonad-contrib fails to compile with ghc-6.10.1
by codesite-noreply＠google.com 23 Dec '08

23 Dec '08

Comment #1 on issue 252 by gwern0: xmonad-contrib fails to compile with ghc-6.10.1 http://code.google.com/p/xmonad/issues/detail?id=252 This is a known 6.10 issue, fixed in darcs xmonad and xmc. -- 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