February 2015 - xmonad

Issue 585 in xmonad: Fullscreen window grows with each click on HTML5 videos in Google Chrome
by codesite-noreply＠google.com 09 Mar '15

09 Mar '15

Status: New Owner: ---- New issue 585 by mikebrod...(a)gmail.com: Fullscreen window grows with each click on HTML5 videos in Google Chrome https://code.google.com/p/xmonad/issues/detail?id=585 What steps will reproduce the problem? 1. Open Google Chrome and play HTML5 embedded video. 2. Fullscreen the video (I'm using `isFullscreen --> doFullFloat` in my ManageHook) 3. Click anywhere with the fullscreened video, and it's window will "grow" with each click. What is the expected output? What do you see instead? I don't expect the window to grow when I click it. What version of the product are you using? On what operating system? Xmonad 0.11 on Ubuntu 14.04 (installed using cabal, not APT) Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output from "xmonad --recompile". Please provide any additional information below. Attachments: xmonad.hs 6.8 KB -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 2

Vanilla Xmonad distribution
by Alexander Genaud 01 Mar '15

01 Mar '15

Years ago, I set my girlfriend up with Ubuntu 12.04 LTS and xmonad (0.8 or 0.9 maybe). With minor tweaks, mod4Mask, etc, it just worked for years. This weekend, I tried to set up Linux Mint Mate, then Cinnamon, then Xubuntu (Xfce) with xmonad-0.11, each with their own unique issues. Xubuntu was most promising, but just doesn't work very well (panel disappears, or meta-key is intercepted such that Win-1 or Win-Shift-Return are typed into the highlighted app or ignored). I am reading a hodge-podge of different config tutorials focusing on an assortment of versions. I have not come across an installation/config wiki page that seemed relevant and up to date. I'm willing to install just about any distribution (not Arch nor Gentoo) and nearly any DE, but I'd like all the niceties of a stable (LTS-ish) DE with graphical networking, application selection menus, panel, notifications, but with the latest xmonad tile windowing. I like the idea of Xfce because it's light weight and easy. Gnome2 fallback is fine too. I expected Mate would 'just work'. Is there a stable reference distro? Can someone point me to a tutorial from late 2014 or 2015 for installing xmonad on a recently distro?

6 5

dmenu in xmonad with KDE
by Zachary Peterson 28 Feb '15

28 Feb '15

Hello, I've decided to give xmonad a try after hearing some good things about it. I installed it and configured it as described in the wiki (https://wiki.haskell.org/Xmonad/Using_xmonad_in_KDE) I have no knowledge of Haskell yet, so the only change I've made to the config given in the wiki is the change of 'kdeConfig' to 'kde4Config', as directed. When running, I'm unable to launch dmenu through mod-p, though I am able to start it with 'dmenu_run' in a terminal. I checked my .xsession-errors file, and found the following lines after trying: QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Bad _NET_DESKTOP with data[0]=-1 QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. [/usr/bin/nepomukservicestub] QObject::connect: Cannot connect XSyncBasedPoller::destroyed() to (null)::_k_x11FilterDestroyed() QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. QDBusConnection: session D-Bus connection created before QCoreApplication. Application may misbehave. Bad _NET_DESKTOP with data[0]=-1 This is all through Debian Wheezy with KDE4, with all relevant installations done through Debian's repositories. Any help you can provide will be greatly appreciated. Thank you. -- Zachary Peterson zap5029(a)psu.edu (317) 828-2377 OpenPGP key: BF5879D6

2 2

New hook to set a distinct wallpaper per workspace, please add to xmonad-contrib
by Anton Pirogov 28 Feb '15

28 Feb '15

Hi, I am new on the list so I hope I do this correctly... I have written a log hook to set wallpapers. The special thing here is, that you can assign a wallpaper (or a set to be chosen randomly from) to each workspace, so when you have workspace A on screen 1 and B on screen 2, you see the according images on these screens and if you swap the workspaces, the wallpapers get swapped too. Wallpapers are always applied scaled and it detects vertical screens and rotates images accordingly (so any wallpaper will be rendered on any screen in a sane way). This hook has been tested by me for over a year already and has not failed me, so I decided to show it to the public, I hope this is worth being integrated into xmonad-contrib. Best regards, Anton Pirogov

3 5

Issue 592 in xmonad: xmonad doesn't allow other window managers to take replace xmonad
by codesite-noreply＠google.com 27 Feb '15

27 Feb '15

Status: New Owner: ---- New issue 592 by np.hard...(a)gmail.com: xmonad doesn't allow other window managers to take replace xmonad https://code.google.com/p/xmonad/issues/detail?id=592 xmonad can request to take over managing windows from another window manager by way of xmonad --replace. However, if another window manager (marco in my case) calls their replace method (in my case marco --replace) xmonad does not pass management of windows over to the calling window manager. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 0

darcs patch: Split out the X event get function from xmonad.
by Lally Singh 26 Feb '15

26 Feb '15

Hello! Please tell me what you think, of both the patch and the process I'm sending this in-by. First time for both. Thanks! 1 patch for repository http://code.haskell.org/xmonad: Thu Feb 26 10:22:06 EST 2015 lally.singh(a)gmail.com * Split out the X event get function from xmonad. This lets xmonad users specify their own functions that get the next X event, and consequently have access to the Display and run in xmonad's thread. Useful for providing such access to other threads. New patches: [Split out the X event get function from xmonad. lally.singh(a)gmail.com**20150226152206 Ignore-this: de10517364b9c642552ff62ebb614d28 This lets xmonad users specify their own functions that get the next X event, and consequently have access to the Display and run in xmonad's thread. Useful for providing such access to other threads. ] { hunk ./src/XMonad/Main.hs 49 -- The main entry point -- xmonad :: (LayoutClass l Window, Read (l Window)) => XConfig l -> IO () -xmonad initxmc = do +xmonad initxmc = xmonad' defaultEventGetter initxmc + +-- | Default X event getter. +defaultEventGetter :: Display -> XEventPtr -> X Event +defaultEventGetter _ = io . getEvent + +-- | Actual entry point, with a parameter for the X event getter. The getter +-- has access to the X event loop. +xmonad' :: (LayoutClass l Window, Read (l Window)) => (Display -> XEventPtr -> X Event) -> XConfig l -> IO () +xmonad' eventGetter initxmc = do -- setup locale information from environment setLocale LC_ALL Nothing -- ignore SIGPIPE and SIGCHLD hunk ./src/XMonad/Main.hs 158 userCode $ startupHook initxmc -- main loop, for all you HOF/recursion fans out there. - forever $ prehandle =<< io (nextEvent dpy e >> getEvent e) + forever $ prehandle =<< eventGetter dpy e return () where }

3 3

darcswatch still useful?
by Joachim Breitner 25 Feb '15

25 Feb '15

Dear xmonad and darcs communities, many years ago¹ I created a service called darcswatch, which tracks the state of submitted darcs patches, by watching the mailinglists and repositories. It has been running since then at http://darcswatch.nomeata.de/ I have not actively used it myself since at least 4 years, and the last patches are from 2011. It still works, but also not always, i.e. it seems to miss some patches it cannot parse. As far as I know, the darcs and xmonad projects were the only that somewhat actively use(d) it. So I wonder: Is there a point in keeping it alive? Is there maybe even someone interested in taking over? Or can I just silently pull the plug? Greetings, Joachim ¹ almost seven, actually: https://www.joachim-breitner.de/blog/290-Announcing_DarcsWatch That was when GitHub was not ubiquitous and still many projects were using Darcs. -- Joachim “nomeata” Breitner mail(a)joachim-breitner.de • http://www.joachim-breitner.de/ Jabber: nomeata(a)joachim-breitner.de • GPG-Key: 0xF0FBF51F Debian Developer: nomeata(a)debian.org

1 1

Issue 591 in xmonad: XMonad "fights" with toolkits when focusing a window with a child modal dialog
by codesite-noreply＠google.com 23 Feb '15

23 Feb '15

Status: New Owner: ---- New issue 591 by MathStuf(a)gmail.com: XMonad "fights" with toolkits when focusing a window with a child modal dialog https://code.google.com/p/xmonad/issues/detail?id=591 When a window has a modal dialog, trying to select the parent window causes the toolkit to then focus the modal dialog, but this puts XMonad's data structures out-of-sync with reality. Here it shows up as the focus (as indicated by the border) rapidly flipping back and forth between the two windows. Focusing any window other than the parent window fixes it. I can think of a few solutions: - skip giving focus to windows with a modal child; or - focus the modal child instead (if on the same workspace? monitor? visible?). I prefer the second with "if visible", but maybe this could be an option to the configuration. The problem with implementing anything right now comes in trying to track modal child/parent relationships. X.U.WindowState is useful here, but there's no place to intercept all calls to XMonad.Operations.focus to change the behavior. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 0

Issue 570 in xmonad: add systemd support
by codesite-noreply＠google.com 22 Feb '15

22 Feb '15

Status: New Owner: ---- New issue 570 by olyasi...(a)gmail.com: add systemd support http://code.google.com/p/xmonad/issues/detail?id=570 There are few user-made .service files for xmonad. It would be great to see such file available as part of xmonad or xmonadcontrib so users could easily start xmonad with "systemd --user" -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 1

Issue 543 in xmonad: StackSet: non-positive argument to StackSet.new with mroe monitors than workspaces
by codesite-noreply＠google.com 22 Feb '15

22 Feb '15

Status: Accepted Owner: nome...(a)gmail.com New issue 543 by nome...(a)gmail.com: StackSet: non-positive argument to StackSet.new with mroe monitors than workspaces http://code.google.com/p/xmonad/issues/detail?id=543 At http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=706149 this bug was reported (Version 0.10): My xmonad configuration only sets up a single workspace: I create the rest dynamically as I need them. I use a laptop, and sometimes have an external monitor. If I have a single workspace when I attach the second monitor, xmonad fails to start. A minimal .xmonad.hs that exhibits the problem: --- 8< --- import XMonad import XMonad.Config.Gnome main :: IO () main = do xmonad $ gnomeConfig { workspaces = ["GTD"] } --- 8< --- Procedure for reproducing: * Use the above .xmonad.hs. * Log into a GNOME+Xmonad session in wheezy. * If there are two monitors, xmonad fails to start. * If there is a single monitor, this works. If I attach a second monitor, xmonad does not crash. However, re-starting it (e.g., due to a change to .xmonad.hs) doesn't work. The error message xmonad gives when starting up: xmonad-x86_64-linux: xmonad: StackSet: non-positive argument to StackSet.new I am probably unsual in liking to create my workspaces dynamically on demand. However, it would be good if xmonad would at least start even if it can't have something on every monitor. -- You received this message because this project is configured to send all issue notifications to this address. You may adjust your notification preferences at: https://code.google.com/hosting/settings

1 5