- xmonad - Haskell.org

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

Issue 498 in xmonad: Borders are not around the window with the focus
by codesite-noreply＠google.com 26 Jul '13

26 Jul '13

Status: New Owner: ---- New issue 498 by rlblas...(a)gmail.com: Borders are not around the window with the focus http://code.google.com/p/xmonad/issues/detail?id=498 What steps will reproduce the problem? 1. Open a terminal and open a file from it in evince. E.g. type "evince a.pdf &" (assuming a.pdf exists in the current directory). 2. Now evince comes into the focus, it has the borders around its window. 3. Go back to the terminal and type "evince a.pdf". This should refresh evince. 4. Observe that evince is in focus by pressing j/k or other evince shortcuts. 5. Also observe that the terminal's window still has borders around it like it's in focus. Basically the focus and the border decoration is not in sync. One of the applications should have both the focus and the border. $ xmonad --version xmonad 0.10

1 3

prompt for clipboard history
by Donatella Quagli 21 Jul '13

21 Jul '13

Dear all, I would like to have a prompt command to reselect something from my clipboard history. The history is created with a simple cron job that executes xclip -o >> $HOME/.clipboard-history every second. My question is, how can I create the auto completion list from that file? I tried for many hours and finally gave up. My last try was this command: ((mod3Mask, xK_c), inputPromptWithCompl myXPConfig "clipboard" mkComplFunFromList(runProcessWithInput "cat /home/donatella/.clipboard-history") ?+ (\r -> spawn $ "echo" ++ r ++ "| xclip")) which did not work. Can anybody help me? Thanks in advance Donatella

3 6

patches to use data-default
by Daniel Wagner 20 Jul '13

20 Jul '13

I noticed that there's a lot of places in xmonad and xmonad-contrib where we have manually-namespaced, monomorphic default values (especially for configurations and such things). The data-default package was designed for this, so I've drawn up a patch to use it. I've included two patch bundles, one for the xmonad repository, and one for the xmonad-contrib repository. (Technically, I have enough permissions to apply the xmonad-contrib ones myself; but I wanted to invite some review.) The bundle for -contrib includes three patches, in roughly increasing order of pervasiveness: 1. the minimal change to make things compile with the -core patch 2. a patch which eliminates all references to defaultConfig (including in the documentation) 3. a patch that uses data-default for things like defaultXPConfig, defaultPP, and similar things I've done my best to: * maintain backwards compatibility. Configs that use these symbols should generate a warning, but still work perfectly correctly. * ensure that all the places that used to export default values now also export "def", so that working configs can eliminate the warnings without changing their imports (or at worst change imports of defaultXPConfig, etc. to imports of def) Enjoy! ~d

7 8

Did the latest patch break the build?
by Carsten Mattner 20 Jul '13

20 Jul '13

Did the latest patch break the build for anyone else? Building xmonad-contrib-0.11... ... XMonad/Util/CustomKeys.hs:66:29: Not in scope: `def'

4 8