October 2010 - xmonad

darcs patch: minor documentation fixes
by Daniel Wagner 07 Oct '10

07 Oct '10

1 patch for repository code.haskell.org:/srv/code/XMonadContrib: Wed Oct 6 21:19:57 EDT 2010 Daniel Wagner <daniel(a)wagner-home.com> * minor documentation fixes

3 2

darcs patch: Minor documentation fixes in X.U.ExtensibleState
by Daniel Schoepe 06 Oct '10

06 Oct '10

1 patch for repository code.haskell.org:/srv/code/XMonadContrib: Mon Oct 4 14:05:09 CEST 2010 Daniel Schoepe <daniel.schoepe(a)googlemail.com> * Minor documentation fixes in X.U.ExtensibleState

3 2

Re: Bug#599211: xmonad: if another wm is already running, please give a more descriptive error message
by Joachim Breitner 06 Oct '10

06 Oct '10

Hi Timo, thanks for your bug report. Am Dienstag, den 05.10.2010, 20:11 +0300 schrieb Timo Juhani Lindfors: > Package: xmonad > Version: 0.9.1-2+b1 > Severity: wishlist > > Steps to reproduce: > 1) Start some other wm > 2) Run xmonad > > Expected results: > 2) xmonad informs the user that a wm is already running and exits > > Actual results: > 2) xmonad prints > > /home/lindi/.xmonad/xmonad-x86_64-linux: executeFile: does not exist (No such file or directory) > X Error of failed request: BadAccess (attempt to access private resource denied) > Major opcode of failed request: 2 (X_ChangeWindowAttributes) > Serial number of failed request: 7 > Current serial number in output stream: 8 > > and leaves the user completely puzzled. Please consider printing > something like > > "xmonad: Another window manager already running, exiting..." > > instead or in addition to the above error message. I’d say it should just replace the running window manager, but if that is not easily possible, you are right. I’m therefore CC’ing the xmonad mailing list: Is there a taker for this issue? Greetings, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 1

Passing ModMask inputs to application
by Wei Hu 05 Oct '10

05 Oct '10

Hi, I'm using NX to connect to a remote Linux box, and both machines are running XMonad. How can I tell XMonad to pass every keyboard/mouse input to the remote desktop? In other words, I would like the remote desktop to "grab" my inputs, like the way VMWare and Remote Desktop work on Windows. Thanks, Wei

2 1

Re: Bug#598659: xmonad ignores xrandr --primary and assumes leftmost screen is the primary
by Joachim Breitner 02 Oct '10

02 Oct '10

Dear xmonad list, a user of the xmonad package in Debian reports problems with xmonad/xmobar and two screens, where the wrong screen seems to be used as the primary screen. As I don’t have a dual screen setup myself, maybe you can help Albin? The full discussion so far can be read on http://bugs.debian.org/598659 Thanks, Joachim -- Joachim "nomeata" Breitner Debian Developer nomeata(a)debian.org | ICQ# 74513189 | GPG-Keyid: 4743206C JID: nomeata(a)joachim-breitner.de | http://people.debian.org/~nomeata

2 1

XMonad.Layout.Groups followup
by Quentin Moser 02 Oct '10

02 Oct '10

Hi people, I know I promised to try and merge my Groups layout into X.L.Sublayout; it won't happen. I've just spent a long while without a Linux machine, and in the meantime my interest in hacking XMonad has waned considerably. So I plan on leaving X.L.Groups as a separate module. Its functionality does overlap with Sublayouts, but not completely, and from what I remember about my attempts to merge them it's not at all trivial. They also offer very different interfaces, which make different things easy to do. The patch file I've attached contains a few fixes to the Groups layout which I hadn't sent yet, a minor redesign of the interface which, as far as I'm concerned, is now frozen, and a patch to orphan all the modules I was supposed to be maintaining. With these fixes, the only outstanding problem left with X.L.Groups (as far as I'm aware) is that when deleting the focused window focus may jump back to another one at surprising places in the layout, but I don't see a obvious way of fixing and I don't want to spend too much time on this anymore, so I'm leaving it as-is. Cheers, Quentin

3 2