January 2015 - xmonad

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

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

Re: Issue 254 in xmonad: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal"
by codesite-noreply＠google.com 06 Feb '15

06 Feb '15

Comment #6 on issue 254 by klu...(a)gmail.com: XMonad.Contrib.Util.Run.runInTerm does not work with terminal = "gnome-terminal" http://code.google.com/p/xmonad/issues/detail?id=254 I wrote a routine to double-quote and escape shell input, and it _seems_ to work for me. I've added it to Prompt.Ssh instead of changing runInTerm, but it logically belongs there. That is, I call ssh s = runInTerm "" (bashDblQuote ("ssh " ++ s)) where bashDblQuote is the quoting function. Attachments: dblquote.hs 866 bytes OtherSsh.hs 3.4 KB

1 3

Dealing with large amounts of pages in a common web browser
by Troels Henriksen 02 Feb '15

02 Feb '15

I have been using xmonad for some years now, and all throughout, the browser I have been using has been a private fork of surf[0], which is essentially just a Webkit webview in a window by itself. However, I would like to switch to a more widely used browser (Chrome, Firefox, Conkeror, whatever) for usability and security reasons. The nice thing about surf is that it opens a window per page, which means that they are all visible to xmonad, and navigable through things like GridSelect, which would not be the case if I simply had two dozen tabs open in Firefox. However, sometimes tabs are nice - specifically, it's practical to use CTRL-clicking to open new pages in the background. Do you have any suggestions on how to deal with this? Some combination of Firefox hacks and xmonad layouts? How do you set up your browsers? [0]: http://surf.suckless.org/ -- \ Troels /\ Henriksen

4 5

Issue 590 in xmonad: different azerty layouts
by codesite-noreply＠google.com 30 Jan '15

30 Jan '15

Status: New Owner: ---- New issue 590 by bert.mo...(a)gmail.com: different azerty layouts https://code.google.com/p/xmonad/issues/detail?id=590 What steps will reproduce the problem? 1. Switch to Belgian keyboard layout 2. Add azertyconfig to xmonad.hs as described in docs 3. Try switching to workspace 6 or 8 What is the expected output? What do you see instead? I expect to switch to workspace 6 or 8 respectively, but nothing happens. Switching to other workspaces works fine. What version of the product are you using? On what operating system? xmonad-0.11 xmonad-contrib-0.11.3 Debian 8 The issue are the keymappings in XMonad/Config/Azerty.hs. The Belgian keyboard layout seems to need different codes for certain keys. My workaround Copy the source from Azerty.hs to the appropriate places in xmonad.hs. Replace the keymappings in function azertykeys: [0x26,0xe9,0x22,0x27,0x28,0x2d,0xe8,0x5f,0xe7,0xe0] by [ xK_ampersand , xK_eacute , xK_quotedbl , xK_apostrophe , xK_parenleft , xK_section -- 6 0xa7 , xK_egrave , xK_exclam -- 8 0x21 , xK_ccedilla , xK_agrave , xK_parenright ] Proposed solution 1. Replace the original key names like 0x26 by their more readable name like xK_ampersand (6 and 8 still need to be matched for the original azerty layout) 2. Add the variant for the belgian keyboard layout (and maybe others) to the documentation of Azerty.hs. Alternative solution 1 Add a module for the belgian keyboard layout: e.g. AzertyBe.hs Alternative solution 2 Actually the best solution in my opinion. Provide an easy, well-documented way to convert keymappings to other keyboard layouts, so the original keystrokes are preserved. The xmonad cheat sheet would stay valid, just with other symbols on the keys. -- 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 588 in xmonad: xmonad --restart doesn't seem to work
by codesite-noreply＠google.com 30 Jan '15

30 Jan '15

Status: New Owner: ---- New issue 588 by tmartin....(a)gmail.com: xmonad --restart doesn't seem to work https://code.google.com/p/xmonad/issues/detail?id=588 What steps will reproduce the problem? 1. running xmonad --restart at the terminal apparently does nothing 2. hitting mod-q apparently does nothing 3. What is the expected output? What do you see instead? xmonad restarts and reruns my configuration startups etc. What version of the product are you using? On what operating system? darcs up to date version 0.12 on Ubuntu 14.04. Logging directly into xmonad from the dm. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". No output. Compiles without errors. Please provide any additional information below. If I exit to the dm and log back in, xmonad restarts without any problems. It is only when I try to restart the running xmonad session that it seems to fail. Attachments: xmonad.hs 21.4 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 14

Issue 587 in xmonad: GridSelect's defaultNavigation will not respond to KP_Divide or AltGr-q
by codesite-noreply＠google.com 22 Jan '15

22 Jan '15

Status: New Owner: ---- New issue 587 by igor.con...(a)gmail.com: GridSelect's defaultNavigation will not respond to KP_Divide or AltGr-q https://code.google.com/p/xmonad/issues/detail?id=587 What steps will reproduce the problem? 1. Use defaultNavigation for something, e.g. ", ((...), goToSelected defaultGSConfig)" 2. Open some windows 3. Call goToSelected and hit KP_Divide (Fn-0, on my laptop keyboard) or AltGr-q What is the expected output? What do you see instead? I expected some 'search mode' to start, but nothing happens. What version of the product are you using? On what operating system? xmonad-0.11 on Arch Linux Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Please provide any additional information below. -- 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

Fwd: 'resetScreenSaver' from 'Graphics.X11.Xlib.Misc'
by Dontdie YCH 22 Jan '15

22 Jan '15

---------- Forwarded message ---------- From: Dontdie YCH <dontdieych(a)gmail.com> Date: Fri, Jan 23, 2015 at 3:33 AM Subject: Re: [xmonad] 'resetScreenSaver' from 'Graphics.X11.Xlib.Misc' To: Brandon Allbery <allbery.b(a)gmail.com> I had same idea about that so I tried as I already showed. Set screensaver timer to 10 sec then call resetScreenSaver every 5 sec. If this is right, screensaver should not appeared. But It was. 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 ~~~ On Wed, Jan 21, 2015 at 10:14 PM, Brandon Allbery <allbery.b(a)gmail.com> wrote: > On Wed, Jan 21, 2015 at 1:22 AM, Dontdie YCH <dontdieych(a)gmail.com> wrote: >> >> 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 is a one-shot operation that turns off any currently > running screen saver by resetting the no-activity timer. If you want to keep > the screen saver off, you need a thread that periodically calls > resetScreenSaver, perhaps once every 30 seconds. > > -- > brandon s allbery kf8nh sine nomine associates > allbery.b(a)gmail.com ballbery(a)sinenomine.net > unix, openafs, kerberos, infrastructure, xmonad http://sinenomine.net

1 0