- xmonad - Haskell.org

Re: Issue 193 in xmonad: conky uses 100% cpu after starting it and moving the mouse (XMonadContrib)
by codesite-noreply＠google.com 09 Aug '10

09 Aug '10

Comment #4 on issue 193 by stevenc49: conky uses 100% cpu after starting it and moving the mouse (XMonadContrib) http://code.google.com/p/xmonad/issues/detail?id=193 I'm not too sure about #2 resizing but with xmonad and a focused workspace on conky, the CPU spike up. I went into my ~/.conkyrc and found out that commenting out "own_window yes" will solve the problem.

1 0

Re: WindowNavigation and Spacing Issue
by Tomáš Janoušek 03 Aug '10

03 Aug '10

Hi David, On Mon, Aug 02, 2010 at 08:05:54PM +0200, David Hrachovy wrote: > now I understand the problem. If I had two floating windows like this > ----------- > | | > ----------- > > ------------ > | | > ------------ > the focus changing wouldn't work, right? Not so bad:) With X.L.WN, if I understand it correctly, it wouldn't. With X.A.WN, it might. > I forgot to mention the XMonad.Actions.WindowNavigation. Well with this > > myLayout = windowNavigation $ spacing 2 $ tiled > > it didn't work for me. I didn't get if it worked for you or not. If > yes, let me know. The usage of X.A.WN is different, see the documentation. Regards, -- Tomáš Janoušek, a.k.a. Liskni_si, http://work.lisk.in/

1 0

Inconsistencies in `instance Monoid ManageHook'
by Adam Vogt 03 Aug '10

03 Aug '10

Hi, The behavior of instance Monoid ManageHook is unnecessarily complicated. Perhaps the following example can convince you If a and b are defined with some arbitrary a', b' manipulations of the WindowSet like > a :: ManageHook > a = do > liftIO (putStrLn "a") > doF a' Then > a <+> b can be written as > do > liftIO (putStrLn "a") > liftIO (putStrLn "b") > doF (a' . b') Side effects take place from left-to-right. The WindowSet is threaded from right-to-left through the functions (which could be produced as a result of those side effects). Possible correction: 1. Change ManageHook > type ManageHook = Query (Dual (Endo WindowSet)) For: All Monoid instances involved with XMonad would be left-to-right (Data.Map.Map prefering values on the left for duplicate keys doesn't fitting any direction in my opinion) Against: Will break quite a few configurations 2. Change instance Monoid (Query a) > instance (Monoid a) => Monoid (Query a) where > mappend = flip (liftM2 (flip mappend)) For: Less code is likely to be broken by flipping the order that IO is run, since much fewer ManageHooks seem to involve liftX or liftIO for changing things that could be read later Against: Left-to-right remains a special case for ManageHook How much would you value consistency when using (<+>) = mappend with nearly all fields in XConfig? Are any current or reasonable uses of ManageHook be impossible if one of the composition orders were changed for consistency? -- Adam

2 2

WindowNavigation and Spacing Issue
by David Hrachovy 02 Aug '10

02 Aug '10

Hello everyone! when using WindowNavigation and Spacing together, the window navigation doesn't work. If the 'spacing 2' is removed the navigation works. I like both the features. Can you please help me set up window spacing and easy window navigation? Try out this minimal example to see the issue - NOTE: you have to spawn at least three terminals to be able to see it): import XMonad import Data.Monoid import System.Exit import qualified XMonad.StackSet as W import qualified Data.Map as M import XMonad.Layout.WindowNavigation import XMonad.Layout.Spacing myKeys conf@(XConfig {XMonad.modMask = modm}) = M.fromList $ [ ((modm .|. shiftMask, xK_Return), spawn $ XMonad.terminal conf) -- Quit xmonad , ((modm .|. shiftMask, xK_q ), io (exitWith ExitSuccess)) -- Restart xmonad , ((modm , xK_q ), spawn "xmonad --recompile; xmonad --restart") -- WindowNavigation , ((modm, xK_l), sendMessage $ Go R) , ((modm, xK_h ), sendMessage $ Go L) , ((modm, xK_k ), sendMessage $ Go U) , ((modm, xK_j ), sendMessage $ Go D) ] myLayout = windowNavigation $ spacing 2 tiled where tiled = Tall nmaster delta ratio nmaster = 1 ratio = 1/2 delta = 3/100 main = xmonad defaultConfig { terminal = "xterm", keys = myKeys, layoutHook = myLayout } I am running xmonad 0.9.1. Thank you David H.

2 1

Issue 349 in xmonad: Chromium gives BadWindow (invalid Window parameter)
by codesite-noreply＠google.com 02 Aug '10

02 Aug '10

Status: New Owner: ---- New issue 349 by ninternity: Chromium gives BadWindow (invalid Window parameter) http://code.google.com/p/xmonad/issues/detail?id=349 What steps will reproduce the problem? 1. Using the Chromium package, "chromium-browser" What is the expected output? A running chromium instance. What do you see instead? The program 'chromium-browser' received an X Window System error. This probably reflects a bug in the program. The error was 'BadWindow (invalid Window parameter)'. (Details: serial 116 error_code 3 request_code 20 minor_code 0) (Note to programmers: normally, X errors are reported asynchronously; that is, you will receive the error a while after causing it. To debug your program, run it with the --sync command line option to change this behavior. You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error() function.) What version of the product are you using? On what operating system? xmonad 0.9, installed from Hackage Xubuntu 9.10 Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. Error does not happen when using xfce + Xubuntu 9.10, nor in xmonad 0.9 + Xubuntu 9.04. Chromium version: 4.0.267.0~svn20091208r34059-0ubuntu1~ucd1~karmic Attachments: xmonad.hs 1.6 KB xmonad_recompile_out 238 bytes -- 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 1

Issue 333 in xmonad: mplayer doesn't go fullscreen
by codesite-noreply＠google.com 28 Jul '10

28 Jul '10

Status: New Owner: ---- New issue 333 by polux2001: mplayer doesn't go fullscreen http://code.google.com/p/xmonad/issues/detail?id=333 What steps will reproduce the problem? 1. install ubuntu 9.10 2. cabal install xmonad 3. mplayer somevideo 4. press F What is the expected output? What do you see instead? Nothing happens. This doesn't occur with other WM (metacity). Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". I'm using a customized xmonad.hs but the problem occurs with Config.hs found in he distribution. -- 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 13

darcs patch: A hook to handle minimize/restore window manager hints.
by Justin Bogner 26 Jul '10

26 Jul '10

Tue Jun 15 23:11:24 MDT 2010 Justin Bogner <mail(a)justinbogner.com> * A hook to handle minimize/restore window manager hints. XMonad.Hooks.Minimize handles both minimize and restore messages. Handling restore messages was already done in RestoreMinimized, which this module intends to replace.

3 2

Re: [xmonad] Re: knowing what is on each workspace and/or knowing which workspace I am looking at
by Lara Michaels 21 Jul '10

21 Jul '10

Hi Justin, Many thanks, I will apply it and recompile xmonad. In the mean-time, I wanted to share a short script that, combined with the Gnome Window Selector, works almost perfectly for me. You will find it attached. It uses xdotool to let you pop up the Gnome Window Selector from the keyboard. Perhaps someone will find it useful. Pros (compared to the different "pager/pager-like" solutions I have been trying out): + works with multiple screens + shows you the title of each window, not just an icon + works with a vertical panel Cons: - information is not right in front of you [you have to "pop up" the menu to see which window is where] - Gnome Window Switcher groups together all windows currently visible into the first section of the menu, and then omits the currently visible workspaces on which they sit from the ordered list of workspaces. I would have preferred an ordered list of *all* workspaces (together with some indication of which workspaces are currently visible), but I am finding it easy to get used to the way GWS works and this is just a minor inconvenience for me. All the best ~l --- On Wed, 7/21/10, Justin Bogner <mail(a)justinbogner.com> wrote: > From: Justin Bogner <mail(a)justinbogner.com> > Subject: [xmonad] Re: knowing what is on each workspace and/or knowing which workspace I am looking at > To: xmonad(a)haskell.org > Date: Wednesday, July 21, 2010, 12:09 AM > Lara Michaels <laramichaels1978(a)yahoo.com> > writes: > > In case others (now or in the future) are interested > in getting this > > working, I just want to note that unfortunately this > very cool > > switcher that Justin pointed out is not usable with > multiple > > monitors. All the apps currently visible (on both > workspaces) get > > grouped together as being in either workspace A or B, > depending on > > which currently has focus. > > This is due to how EwmhDesktops works. The gnome window > selector behaves > the same way, in fact. I wrote a patch [1] that fixes this > issue last > year, but apparently nobody was interested enough to apply > it. > > An updated patch for the current head is attached. > > [1]: http://article.gmane.org/gmane.comp.lang.haskell.xmonad/8542 > > > -----Inline Attachment Follows----- > > > -----Inline Attachment Follows----- > > _______________________________________________ > xmonad mailing list > xmonad(a)haskell.org > http://www.haskell.org/mailman/listinfo/xmonad >

1 0

Re: [xmonad] Re: knowing what is on each workspace and/or knowing which workspace I am looking at
by Lara Michaels 21 Jul '10

21 Jul '10

Hi Justin and Max, Thank you for your terrific help. I just played around for a bit with the Gnome Window selector and it is by far the best option until now for my purposes. I will try to use xdotool to avoid having to click on the panel to show/hide the list. The only thing I would like to change about this is that I would like it to always show the complete, sorted list of workspaces -- "ws 1", "ws2" ,etc -- independently if there is something on them and/or if they are currently visible. The spatial layout of the ordered list (with no skipping of empty workspaces) would be perfect. But I guess this is asking too much. :) As usual all ideas are more than welcome. This is a terrific list. :) best ~l

2 4

knowing what is on each workspace and/or knowing which workspace I am looking at
by Lara Michaels 18 Jul '10

18 Jul '10

Dear all, I never managed to have a way of knowing either 1- on which workspace a particular program is open or 2- which workspace is being displayed on each of my monitors (eg, "on this monitor you are looking at workspace 1") Is there a way to get either of these behaviors? Without this information, I do spend some serious time zapping across workspaces to find the window I need. I thought that an easy way to address (2) would be to use an OSD (like libnotify) to pop up a notification providing the workspace name/number when the user switches workspaces. Is there a "hook" in xmonad to which I could link a command "run notification saying this is workspace X"? Many thanks for any help ~lara

7 7