- xmonad - Haskell.org

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

darcs patch: XMonad.Prompt.Pass: Handle hierachical password stores
by Joachim Breitner 18 Feb '15

18 Feb '15

1 patch for repository http://code.haskell.org/XMonadContrib: Wed Feb 18 10:18:16 CET 2015 Joachim Breitner <mail(a)joachim-breitner.de> * XMonad.Prompt.Pass: Handle hierachical password stores pass stores its passwords in directories, so the contents of the directory store needs to be enumerated recursively. Alexander Sulfrian provided this patch on the mailinglist, which I tested (it works) and cleaned up slightly.

1 0

Configure eating of keys based on window class
by Jiří Maršíček 16 Feb '15

16 Feb '15

Hi, would it be possible to configure xmonad to eat certain keys or key combinations to windows based on some predicate (window className) or globaly? I have tried to define this globaly by adding the following line to my keybindings: ((0, xK_Super_L), return ()) (As explained in https://mail.haskell.org/pipermail/xmonad/2012-February/012402.html) But this does not appear to work (key is still processed in the active window) Thanks a lot for any thoughts.

2 5

Issue 576 in xmonad: On FreeBSD Xmonad loses first hotkey sometimes
by codesite-noreply＠google.com 15 Feb '15

15 Feb '15

Status: New Owner: ---- New issue 576 by martin.s...(a)gmail.com: On FreeBSD Xmonad loses first hotkey sometimes http://code.google.com/p/xmonad/issues/detail?id=576 What steps will reproduce the problem? 1. Install FreeBSD (amd64). 2. Write a minimal xmonad.hs with xterm binding. 3. Start xmonad in Xorg. 4. Try (multiple times) Mod+Shift+Return. What is the expected output? What do you see instead? It's expected that xterm opens with the first time Mod+Shift+Return is pressed. Sometimes Xmonad loses the key-combo and you need to press it twice in fast succession. If you wait too long between the first and the second time in sequence, the hotkey will be lost again and again. I repeat once again: it happens SOMETIMES, but on average every 4th time. Try to open terminal and exit it again (Mod+Shift+Return -> Ctrl-D -> Mod+Shift+Return -> Ctrl-D -> ...). What version of the product are you using? On what operating system? hs-xmonad-0.11_7 FreeBSD 10.0 RELEASE (amd64). Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". You don't need mine. Use a minimal one: import XMonad main = xmonad defaultConfig { modMask = mod1Mask , terminal = "xterm" } Additional info: Cannot be reproduced on Linux. Everything works as expected there. -- 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 22

'resetScreenSaver' from 'Graphics.X11.Xlib.Misc'
by Dontdie YCH 08 Feb '15

08 Feb '15

Hello, I'm looking for what is proper method to inhibit screensaver(DPMS) without xscreensaver, KDE, GNOME ... . My video player 'bomi'(was cmplayer) try these, in order, ~~~ [App] Initialize screensaver functions. [App] Try to connect 'org.gnome.SessionManager'. [App] Failed to connect 'org.gnome.SessionManager'. Fallback to 'org.freedesktop.ScreenSaver'. [App] Failed to connect 'org.freedesktop.ScreenSaver'. Fallback to XResetScreenSaver(). [App] Disable screensaver with XResetScreenSaver(). ~~~ But it does not working. I didn't know how I directly deal with X11 lib. Fortunately, I found 'resetScreenSaver' from 'Graphics.X11.Xlib.Misc' that say interface to XResetScreenSaver(). resetScreenSaver.hs : ~~~ import Graphics.X11.Xlib import Graphics.X11.Xlib.Misc import Control.Concurrent import Control.Monad main = do dpy <- openDisplay "" forever $ do putStrLn "reset" resetScreenSaver dpy threadDelay (5*1000000) ~~~ ~~~ $ xset s 10 $ runhaskell resetScreenSaver.hs ~~~ Unfortunately, It does not working. `activateScreenSaver` and `forceScreenSaver` also does not working. But `xset s reset` is working as intended and also there is `xdg-screensaver [ suspend | resume | reset ]` command from 'xdg-utils' package (Arch). It looks like abstraction layer for xset, xscreensaver, KDE, GNOME ... . So I'm curious about whether this is bug of xorg or I misunderstand something. And what is right way to do this if I don't want any screensaver daemon? `xset s` or `xdg-screensaver`? Thanks.

3 3