August 2009 - xmonad - Haskell.org

Issue 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 28 Aug '09

28 Aug '09

Comment #3 on issue 311 by wirtwolff: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 This one is a bit puzzling. Testing by other darcs users would be helpful, as it's been reproduced, but not by all testers. It seems unrelated to using core fonts v.s. xft, compiling with or without optimization, architecture. Results for pbrisbin, dschoepe, and vav were on latest darcs after clean and re-install xmonad/contrib. Any tabbed layout with noBorders should demo the problem, i.e. (noBorders simpleTabbed) in layouts is enough. From #xmonad, all testers on ghc-6.10.4: * Can reproduce: pbrisbin, dschoepe -- ds on archlinux 32-bit, pb on 64-bit * Cannot reproduce; tabs update correctly: vav, dmwit -- both 64-bit, v on gentoo, dw on archlinux -- 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

MultiToggle FULL crashes my WM
by aditya siram 28 Aug '09

28 Aug '09

Hi all, The following configuration crashes my xmonad consistently after switching layouts twice. I'd really like to be able to maximize/unmaximize the focused window and this seemed like the best way to do it. If MultiToggle isn't the right solution, I'm open to suggestions. thanks ... -deech -- myLayout = mkToggle1 FULL $ simpleTabbed ||| tiled ||| Mirror tiled ||| Circle -- where -- -- default tiling algorithm partitions the screen into two panes -- tiled = Tall nmaster delta ratio -- -- The default number of windows in the master pane -- nmaster = 1 -- -- Default proportion of screen occupied by master pane -- ratio = 1/2 -- -- Percent of screen to increment by when resizing panes -- delta = 3/100 -- main = xmonad $ -- defaultConfig { layoutHook = myLayout }

3 3

darcs patch: Let the user decide which commands to use in X.H.Serve...
by Daniel Schoepe 25 Aug '09

25 Aug '09

Tue Aug 25 12:16:30 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * Let the user decide which commands to use in X.H.ServerMode

3 2

darcs patch: Improve/correct documentation in X.A.TagWindows
by Daniel Schoepe 25 Aug '09

25 Aug '09

Sun Aug 23 15:12:29 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * Improve/correct documentation in X.A.TagWindows

2 1

darcs patch: Replace nextEvent with maskEvent to prevent GridSelect...
by Clemens Fruhwirth 25 Aug '09

25 Aug '09

Sun Aug 9 15:10:55 CEST 2009 Clemens Fruhwirth <clemens(a)endorphin.org> * Replace nextEvent with maskEvent to prevent GridSelect from swallowing unrelated events (such as map/unmap)

2 1

darcs patch: Better default for ppUrgent in xmobarPP
by Daniel Schoepe 25 Aug '09

25 Aug '09

Sat Aug 22 20:34:16 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * Better default for ppUrgent in xmobarPP Most users would expect workspaces with urgent windows to be highlighted in xmobar when they set up an UrgencyHook. Hence, doing this by default in xmobarPP makes sense. (dzenPP does the same)

2 1

darcs patch: More flexible interface for X.H.FadeInac... (and 1 more)
by Daniel Schoepe 25 Aug '09

25 Aug '09

Fri Aug 21 22:39:36 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * More flexible interface for X.H.FadeInactive This patch allows setting the opacity on a per-window basis and lets the user specify it as a percentage instead of an Integer between 0 and 2^32-1. Sat Aug 22 00:56:46 CEST 2009 Daniel Schoepe <daniel.schoepe(a)gmail.com> * Add backwards compatability in X.H.FadeInactive

2 1

Re: It won't, no. The exec causes the shell to vanish (so the second xmonad isn't seen at all). Try something like /home/eric/bin/xmonad & setenv DISPLAY=beryllium:0.1 exec /home/eric/bin/xmonad Presuming that works OK, you might want to sta
by Eric Thomas 25 Aug '09

25 Aug '09

Bruce Stephens <xmonad-HpBJwjOt1muTY6FTCsQk+9Bc4/FLrbF6 at public.gmane.org> writes: > Eric Thomas <eric.l.m.thomas-Re5JQEeQqe8AvxtiuMwx3w-XMD5yJDbdMReXY1tMh2IBg at public.gmane.org> > writes: > >> My script is currently the following (I use tcsh). >> >> /home/eric/bin/xmonad & >> setenv DISPLAY beryllium:0.1 exec /home/eric/bin/xmonad & >> wait >> >> However, the second screen still isn't loading correctly. Does >> everything look okay for this? > > Try removing the other exec as well. Or (more primitively) just run one xmonad and see if you can run the other one from a terminal. ---------------------------------------------------------------------------------- Hey, that kind of worked! I started an xmonad in the xsession script. Then did the following through a terminal. setenv DISPLAY beryllium:0.1 /home/eric/bin/xmonad & It indeed allows me to get an xmonad on the second screen. Everything works fine with the exception of the mouse. When I want to do anything on the other screen, I need to have the mouse hover over the window that is considered the master pane (I think I have the term correct, please bare with me as I am new to xmonad). So is there a way to gain focus of the other screen without having to move over the master pane (just having to hover over any window on the other screen)? I ask this because it becomes extremely easy for me to forget which one is the master pane (especially if I move it to a different workspace). Thanks, Eric Thomas

1 0

It won't, no. The exec causes the shell to vanish (so the second xmonad isn't seen at all). Try something like /home/eric/bin/xmonad & setenv DISPLAY=beryllium:0.1 exec /home/eric/bin/xmonad Presuming that works OK, you might want to start both insta
by Eric Thomas 25 Aug '09

25 Aug '09

My script is currently the following (I use tcsh). /home/eric/bin/xmonad & setenv DISPLAY beryllium:0.1 exec /home/eric/bin/xmonad & wait However, the second screen still isn't loading correctly. Does everything look okay for this? Eric Thomas -------------------------------- It won't, no. The exec causes the shell to vanish (so the second xmonad isn't seen at all). Try something like /home/eric/bin/xmonad & setenv DISPLAY=beryllium:0.1 exec /home/eric/bin/xmonad Presuming that works OK, you might want to start both instances in the background and use wait (to wait for both) at the end of the script. Or some variant like that---I'm not sure what would be most convenient for someone running two window managers.

2 2

Issue 311 in xmonad: using noBorders on tabbed layout freezes tab bar on workspace change
by codesite-noreply＠google.com 24 Aug '09

24 Aug '09

Comment #2 on issue 311 by pbrisbin: using noBorders on tabbed layout freezes tab bar on workspace change http://code.google.com/p/xmonad/issues/detail?id=311 created a much simpler xmonad.hs for test. defaults plus the noBorders layout only. the freeze behavior remains Attachments: simple.xmonad.hs 313 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 0