- xmonad - Haskell.org

Issue 279 in xmonad: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null
by codesite-noreply＠google.com 26 Feb '09

26 Feb '09

Status: New Owner: ---- New issue 279 by seschwar: Some GTK2 apps crash X when XMonad's stderr is not redirected to /dev/null http://code.google.com/p/xmonad/issues/detail?id=279 I usually like to start X form the console in the background an then logout. I do it like this: - Using zsh's builtins: startx &!; exit - Or using another shell and detach [1]: detach startx; exit Then the following actions will crash the whole X server: - Save and overwrite an already existing file with Firefox - Execute "Verify versions and deprecations" in Glade's preference dialog I can get my programs to behave normal again by appending "2> /dev/null" to the "exec xmonad" line in my ~/.xinitrc. I have no idea what's going on. The problem doesn't appear when i just have "exec xterm" in my ~/.xinitrc. Also it doesn't matter whether I use a log hook or not. I am using XMonad and XMonad-contrib from hackage and the following packages on Arch Linux: detach 0.2.0-1 firefox 3.0.6-1 glade 3.5.4-1 ghc 6.10.1-2 gtk2 2.14.7-1 xmonad 0.8.1 xmonad-contrib 0.8.1 zsh 4.3.9-1 [1] http://detach.sourceforge.net/ -- 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 277 in xmonad: Red border on two windows
by codesite-noreply＠google.com 25 Feb '09

25 Feb '09

Comment #7 on issue 277 by lit...(a)hethrael.org: Red border on two windows http://code.google.com/p/xmonad/issues/detail?id=277 This sounds similar to issue 237 that I was having. It started on its own, and it went away by itself. I suspect it had something to do with upgrading Xorg or some other library, because I didn’t make any changes to my xmonad configuration when the issue started happening or when it stopped. -- 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 277 in xmonad: Red border on two windows
by codesite-noreply＠google.com 25 Feb '09

25 Feb '09

Comment #6 on issue 277 by lykahb: Red border on two windows http://code.google.com/p/xmonad/issues/detail?id=277 I have x86_64 machine based on Asus AM2 690G. GHC installed as a dependency for XMonad has 6.8.2 version. Setting borderColors does not help - I just get two green borders. I played with bigger number of windows and found more general steps to reproduce - bug occurs when you move window that is in the rightest position of subordinate area to the left with mod-shift-k. I got the attached picture with 2.5 borders but I cannot reproduce the situation. Perhaps it points that the bug is due to interaction with X. Attachments: Screenshot-1.png 56.2 KB -- 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 darcs, haddock, ghc and Ubuntu Intrepid
by Kathryn Andersen 25 Feb '09

25 Feb '09

I'm running Ubuntu Intrepid (8.10) and I'd like to switch from the default xmonad (0.8) to the xmonad in darcs. The ghc version is 6.8.2, which I gather is okay, but the haddock version is the ancient 0.8 version, which is not. However, if I try to remove haddock (in order to replace it with a newer version) apt then removes ghc as well! Any tips as to how to get around this? Kathryn Andersen -- _--_|\ | Kathryn Andersen <http://www.katspace.com> / \ | \_.--.*/ | GenFicCrit mailing list <http://www.katspace.com/gen_fic_crit/> v | ------------| Melbourne -> Victoria -> Australia -> Southern Hemisphere Maranatha! | -> Earth -> Sol -> Milky Way Galaxy -> Universe

2 2

Issue 278 in xmonad: quick xmonad restart is not enough to make IM layout work
by codesite-noreply＠google.com 25 Feb '09

25 Feb '09

Comment #1 on issue 278 by Braden.Shepherdson: quick xmonad restart is not enough to make IM layout work http://code.google.com/p/xmonad/issues/detail?id=278 This is likely to be a problem where the layouts are not always fully updated on a mod+q. After doing a mod+q, try pressing mod+shift+space and seeing if that updates things properly. -- 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] New XMonadContrib module: IndependentScreens
by Fred Blasdel 25 Feb '09

25 Feb '09

On Tue, Feb 24, 2009 at 12:39 PM, <wagnerdm(a)seas.upenn.edu> wrote: > > Quoting Fred Blasdel <blasdelf(a)gmail.com>: > > Isn't this how workspaces have worked in xmonad for a long itme? Each >> screen is already a view onto an independent workspace from a shared >> list of workspaces -- I'm confused as to what you're trying to add. >> > > This is exactly the thing that annoys me -- that the list of workspaces is > shared. My module changes that (sort of). The shared workspace pool is the thing I love most about xmonad! I was thinking of writing my own window manager to get just that feature when xmonad was released (and I was already a haskeller). It annoys me to no end how nearly every "virtual desktop" implementation treats multiple monitors as one desktop. Does your module segregate the workspaces into monitor-specific sets, that can still be switched independently? -- Fred

3 4

New XMonadContrib module: IndependentScreens
by Don Stewart 25 Feb '09

25 Feb '09

Forwarded from the offlist buffer: Date: Sat, 21 Feb 2009 19:06:20 -0500 From: wagnerdm(a)seas.upenn.edu Subject: New XMonadContrib module: IndependentScreens Hey all, I've written a short contrib module to scratch an itch I've had even since jcreigh made the first Xinerama support. I like dwm's module, where workspaces on different screens are conceptually distinct, even if they have the same name. Now XMonad.Layout.IndependentScreens makes that possible. Many thanks to Brent Yorgey, who sat next to me and helped me get it into a releasable state. =) (There's no patch attached; Brent applied it for me.) ~d P.S. I'm not actually on this list, so be sure any complaints have daniel(a)wagner-home.com somewhere in the to: line. ;-)

3 2

Issue 277 in xmonad: Red border on two windows
by codesite-noreply＠google.com 25 Feb '09

25 Feb '09

Comment #5 on issue 277 by wirtwolff: Red border on two windows http://code.google.com/p/xmonad/issues/detail?id=277 Can confirm intrepid (ubuntu 8.10) does install xmonad-0.8 rather than 0.8.1, however those differences only apply to x86_64 ghc-6.10 users, and intrepid's on 6.8.2. Still can't reproduce this here. Dist upgraded ubuntu box to intrepid. Tried with clean install of xmonad package only: Could not reproduce using either the XMonad gdm session or .xsession method of replacing metacity. Ensured default installed binary was used. I.e. had no ~/.xmonad, much less xmonad.hs (also no xmonad.conf xmonad-light config.) Then installed libghc6-xmonad and libghc6-xmonad-contrib and tried with no xmonad.hs, with default xmonad.hs, and with a basic Config.Gnome xmonad.hs similar to the attached xmonad.hs, but borders behaved normally with these, too. Yes, don't see how the xmonad.hs has anything to do with this, would have to set both focused and unfocusedBorderColor red to get this effect by normal means. All the explanations I can think of are pretty bizarre. Explicitly setting the border colors should work regardless. If even that doesn't work and the xmonad.hs is truly getting recompiled, (check with 'xmonad --recompile' in terminal if any doubt), then I guess maybe time to look at bizarre ideas. , focusedBorderColor = "green3" , normalBorderColor = "gray10" -- 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 278 in xmonad: quick xmonad restart is not enough to make IM layout work
by codesite-noreply＠google.com 24 Feb '09

24 Feb '09

Status: New Owner: ---- New issue 278 by arseni.buinitsky: quick xmonad restart is not enough to make IM layout work http://code.google.com/p/xmonad/issues/detail?id=278 To reproduce: 1. configure xmonad like this myLayout = onWorkspace "ims" ( avoidStruts(withIM (1%5) (ClassName "Kopete" `And` Role "MainWindow#1") Grid) ) $ avoidStruts( Mirror tiled ||| tiled ||| Full ) 2. quick restart xmonad (restart "xmonad" True) Expect kopete roster window mapped at "ims" workspace in the left corner of the screen having 1/5 of window size. Instead - mapped as usual using Mirror tiled layout. Restarting Xorg makes window mapped as expected. using Linux 2.6.28, Gentoo amd64, ghc 6.8.2, xmonad 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 277 in xmonad: Red border on two windows
by codesite-noreply＠google.com 24 Feb '09

24 Feb '09

Comment #4 on issue 277 by lykahb: Red border on two windows http://code.google.com/p/xmonad/issues/detail?id=277 I have already modified my xmonad.hs to make it work with Gnome and make borders thicker. The bug appears not only when I open terminals but with usual windows as well. When I use Xmonad without Gnome bug also appears. I attached screenshot of this bug and xmonad.hs Attachments: Screenshot.png 71.2 KB xmonad.hs 361 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