- xmonad - Haskell.org

Issue 555 in xmonad: XDG compatibility
by codesite-noreply＠google.com 20 Aug '13

20 Aug '13

Status: New Owner: ---- New issue 555 by olyasi...(a)gmail.com: XDG compatibility http://code.google.com/p/xmonad/issues/detail?id=555 Right now settings and binaries are stored in ~/.xmonad/ It would be great if XDG specification is respected and ~/.config/xmonad/ is used instead. See http://standards.freedesktop.org/basedir-spec/basedir-spec-latest.html for the reference. -- 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

virt-manager guest view and xmonad
by Thomas Koch 20 Aug '13

20 Aug '13

Hi, I'm running xmonad as wm for gnome3 on Debian stable and a virtualized Debian unstable also with gnome3 and xmonad. I view the guest with the viewer integrated in virt-manager (spice). mod-buttonN work on the viewer instead of being propageted to the guest and effecting the client window running in the guest. mod-[1-9] for example work inside the guest and switch workplaces inside the guest. But I want to modify windows inside the guest. Do you have any hint for me? I have modMask = mod4Mask, so my mod key is the windows key. Regards, Thomas Koch

2 1

darcs patch: pass-through-unrecognised-flags
by gopsychonauts＠gmail.com 19 Aug '13

19 Aug '13

1 patch for repository http://code.haskell.org/xmonad: Sun Aug 18 12:31:19 EST 2013 gopsychonauts(a)gmail.com * pass-through-unrecognised-flags Changes XMonad's core binary so that it won't reject arbitrary flags passed to the xmonad command, but instead simply passes them on to the user's XMonad binary. This allows for -contrib extensions to add their own command-line flags if desired. This does imply slightly less error-checking, but the flexibility afforded is, I think, worth it.

4 3

xmonad does not work well with "lxpanelctl run"
by Mogei Wang 18 Aug '13

18 Aug '13

No matter bind "lxpanelctl run" to some key or run it in xterm, the corresponding dialog will appear, and the cursor can be put in the textbox. However, nothing can be inputted. Instead, the input characters will appear in the xterm which the command is running in. Moreover, "lxpanelctl menu" works fine when run from xterm, but does nothing when binded to a key. I am not saying that, that is a bug of xmonad, but the lxpanelctl works fine with the other wms, e.g., openbox, xfwm4, sawfish,... versions: lubuntu 12.04 lxpanel 0.5.8 xmonad 0.10

1 0

Re: [xmonad] issue 554 in xmonad: mkKeymap (hence additionalKeysP) doesn't handle NLS characters
by codesite-noreply＠google.com 17 Aug '13

17 Aug '13

Updates: Cc: m...(a)twifkak.com Comment by allber...(a)gmail.com: (No comment was entered for this change.) Affected issues: issue 554: mkKeymap (hence additionalKeysP) doesn't handle NLS characters http://code.google.com/p/xmonad/issues/detail?id=554 -- You received this message because you are listed in the owner or CC fields of these issues, or because you starred them. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 554 in xmonad: mkKeymap (hence additionalKeysP) doesn't handle NLS characters
by codesite-noreply＠google.com 17 Aug '13

17 Aug '13

Status: Accepted Owner: allber...(a)gmail.com Labels: Component-Contrib Type-Defect Usability New issue 554 by allber...(a)gmail.com: mkKeymap (hence additionalKeysP) doesn't handle NLS characters http://code.google.com/p/xmonad/issues/detail?id=554 What steps will reproduce the problem? 1. Try to use a national language character such as ù in a keybinding with `additionalKeysP` 2. Observe that the keybinding doesn't work What is the expected output? What do you see instead? If you dump the resulting key bindings from the XConfig, the key is not present at all, even in a mangled form The following code is part of XMonad.Util.EZConfig: -- | Parse an unmodified basic key, like @\"x\"@, @\"<F1>\"@, etc. parseKey :: ReadP KeySym parseKey = parseRegular +++ parseSpecial -- | Parse a regular key name (represented by itself). parseRegular :: ReadP KeySym parseRegular = choice [ char s >> return k | (s,k) <- zip ['!'..'~'] [xK_exclam..xK_asciitilde] ] -- | Parse a special key name (one enclosed in angle brackets). parseSpecial :: ReadP KeySym parseSpecial = do _ <- char '<' key <- choice [ string name >> return k | (name,k) <- keyNames ] _ <- char '>' return key Note that the only options here are literal characters in the range '!' through '~', or specific named sequences. Neither NLS characters outside the /[!-~]/ range nor hex keysyms of the form supported by many Xlib-based mechanisms and widely used for Unicode symbols are supported. -- 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

Externally determine active workspace
by Mina Nagy Zaki 15 Aug '13

15 Aug '13

Hello, is there a way to determine the currently active workspace (that which contains the focused window) externally, i.e., through a command line utility? Thanks! -- Mina Nagy Zaki

2 2

Issue 553 in xmonad: Error: xmonad.hs:132:64: Not in scope: `help'
by codesite-noreply＠google.com 14 Aug '13

14 Aug '13

Status: New Owner: ---- New issue 553 by Geoffrey...(a)gmail.com: Error: xmonad.hs:132:64: Not in scope: `help' http://code.google.com/p/xmonad/issues/detail?id=553 What steps will reproduce the problem? 1. Start a new XMonad session or run 'xmonad --recompile'. What is the expected output? What do you see instead? An XMonad session should be started, or the compilation should be successfull. What version of the product are you using? On what operating system? Version 0.11 on Arch Linux. Are you using an xmonad.hs? Please attach it and the output of "xmonad --recompile". Yes, the default xmonad.hs file, copied from /usr/share/xmonad-0.11/man to ~/.xmonad. Please provide any additional information below. Attachments: xmonad.hs 9.5 KB xmonad.errors 40 bytes -- 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 3

darcs patch: Ewmh: add _NET_WM_STATE_FULLSCREEN in the _NET_SUPPORTED
by moiman2＠gmail.com 12 Aug '13

12 Aug '13

1 patch for repository http://code.haskell.org/XMonadContrib: Mon Aug 12 01:55:38 EEST 2013 moiman2(a)gmail.com * Ewmh: add _NET_WM_STATE_FULLSCREEN in the _NET_SUPPORTED

2 1

CycleWS: shiftTo Next EmptyWS >> andThenSomehowFollow
by Rhys Ulerich 08 Aug '13

08 Aug '13

Hi all, CycleWS's documentation suggests > If you want to follow the moved window, you can use both actions: > > , ((modm .|. shiftMask, xK_Down), shiftToNext >> nextWS) > , ((modm .|. shiftMask, xK_Up), shiftToPrev >> prevWS) I'd like to achieve an action like 'shiftTo Next EmptyWS >> andThenSomehowFollow'. The goal is to move the window to the next empty workspace and then to follow it there. My silly attempts with , ((modm .|. shiftMask, xK_Down), followTo Next EmptyWS) using followTo d = shiftTo d >> moveTo d don't work. I suspect this is because I'm not properly saving the Next EmptyWS result prior to mutating the state. I'm a Haskell noob. Would some kind soul please show me the four lines I need to implement followTo? Thank you, Rhys

3 7