- xmonad - Haskell.org

2 bugs in pasteSelection (7s for /s on german keyboard, whitespaces lost)
by Carlos Franke 17 Nov '13

17 Nov '13

Preliminaries: – I have tried to post the following issue without being subscribed to the mailing list a few days ago, but according to the archive, it did not get through. While I am now a subscriber, I still probably won't follow the discussion on the list (sorry), so if you you want to make sure that a certain message reaches me, CC it to my personal address. – I would have used the bug tracker for this, but I do not have a Google account. Sorry again, if this is inconvenient. I noticed two misbehaviours of pasteSelection (from Xmonad.Util.Paste): 1. In my setup, most notably with a standard German (QWERTZ) keyboard layout, pasteSelection converts slashes ("/") to sevens ("7"), thus messing up URLs and path names. With a QWERTZ keyboard, you get a slash by pressing Shift-7, so this is probably connected. 2. Whitespaces (space, tab, newline) are lost when pasting with pasteSelection. About my setup: I am calling pasteSelection by keystroke, configured like this in my xmonad.hs: `additionalKeysP` [ ("M-p", spawn "dmenu_run") , ("M-f", sendMessage ToggleStruts) , ("M-v", pasteSelection) ] I am running Xmonad 0.11-7 and Xmonad-contrib 0.11.2-2 on Arch Linux. pasteSelection is a great tool and I would love to see the above issues fixed. If I can help with that (testing?), please let me know. Carlos

1 0

[PATCH] XMonad: Use window border width instead of borderWidth
by Radim Krcmar 13 Nov '13

13 Nov '13

I have sent it before, but it did not show up on the mailing list; maybe because I was not subscribed then ... 1 patch for repository http://code.haskell.org/xmonad: Tue Nov 12 00:25:51 CET 2013 Radim Krcmar <radimkrcmar(a)hpx.cz> * Use window border width instead of borderWidth configureWindow border width of floating windows is set to borderWidth regardless of the actual value. This produces an interesting effect when borderWidth < "window border set from layout", where window is repeatedly shrinked, because border makes it bigger than it should be. This patch should not be noticeable unless layout is setting border to different values than borderWidth (we already set border to borderWidth when enslaving the window) or third person is setting up window attributes. (then it is a good thing to leave them that way) Setting border width to 0 is required for sane fullscreen mplayer, because it decides to expand by the border width. (pretty bad behaviour) New patches: [Use window border width instead of borderWidth Radim Krcmar <radimkrcmar(a)hpx.cz>**20131111232551 Ignore-this: ffbaf5f6c085ee13a7b6338863a9693c configureWindow border width of floating windows is set to borderWidth regardless of the actual value. This produces an interesting effect when borderWidth < "window border set from layout", where window is repeatedly shrinked, because border makes it bigger than it should be. This patch should not be noticeable unless layout is setting border to different values than borderWidth (we already set border to borderWidth when enslaving the window) or third person is setting up window attributes. (then it is a good thing to leave them that way) Setting border width to 0 is required for sane fullscreen mplayer, because it decides to expand by the border width. (pretty bad behaviour) ] { hunk ./XMonad/Main.hsc 279 ws <- gets windowset wa <- io $ getWindowAttributes dpy w - bw <- asks (borderWidth . config) - if M.member w (floating ws) || not (member w ws) then do io $ configureWindow dpy w (ev_value_mask e) $ WindowChanges hunk ./XMonad/Main.hsc 286 , wc_y = ev_y e , wc_width = ev_width e , wc_height = ev_height e - , wc_border_width = fromIntegral bw + , wc_border_width = ev_border_width e , wc_sibling = ev_above e , wc_stack_mode = ev_detail e } when (member w ws) (float w) } Context: [Bump version to 0.12 Adam Vogt <vogt.adam(a)gmail.com>**20130720192124 Ignore-this: d73483c2dd30f7eea8f40daff7ef436f This is to make contrib build failures resulting from by data-default lead people to do the right thing: update xmonad-core. ] [warning police: name userCodeDef's argument defValue instead of def Daniel Wagner <daniel(a)wagner-home.com>**20130528164401 Ignore-this: f32b218e2097a52c7ecccae28c23754b ] [depend on data-default, and deprecate the monomorphic name defaultConfig Daniel Wagner <daniel(a)wagner-home.com>**20130528003531 Ignore-this: 1e746731695df3b6f684d5463a3da6a4 ] [use "modm" instead of "modMask" in the sample config Daniel Wagner <daniel(a)wagner-home.com>**20130106174414 Ignore-this: 75ad65ae7a708bce69f811c28912cc4b ] [define the "help" string in the sample configuration bundled with xmonad Daniel Wagner <daniel(a)wagner-home.com>**20130106174254 Ignore-this: 1db666ea921046378921356e14cc828f ] [configurableEventMasks mwlochbaum(a)gmail.com**20130205182858 Ignore-this: 3848de0f8f5ad5995e87a2a01e7752f ] [Grab all keycodes linked to each keysym, not just one Daniel Wagner <daniel(a)wagner-home.com>**20130118225446 Ignore-this: 1a6c001560f68f99d75d5f550e7e83 This patch is based heavily on the one contributed by svein.ove(a)aas.no, but updated to avoid causing a conflict and to work with the newest X11 bindings. The name of the patch (and comment below) are copied verbatim from his patch. XKeysymToKeycode only gives the first code bound to a given symbol. To handle the case where multiple keys are bound to the same symbol, XKeycodeToKeysym is used instead, searching through all possible keycodes for each sym. ] [Issue 135 use wa_border_width for floating windows (neoraider) Adam Vogt <vogt.adam(a)gmail.com>**20130115170715 Ignore-this: c8ed6ceaf9483e31771ac25d86532f6c ] [Add flags for call to ghc closing issue 240 Adam Vogt <vogt.adam(a)gmail.com>**20130101035034 Ignore-this: 42a6a8599b615884c95626f74e3ba4a The -main-is flag goes back to at least ghc 6.10, and maybe the warning that this otherwise redundant flag enables (when xmonad.hs isn't a module Main) also dates back that far. ] [TAG 0.11 actual upload Adam Vogt <vogt.adam(a)gmail.com>**20130101014128 Ignore-this: 2c2a85caeed30cd23f02a7caf229fe7d ] Patch bundle hash: 90a0f22fb90471396fd95bb677d45da8ef116602

1 0

Re: [xmonad] Issue 57 in xmonad: Amarok OSD goes missing
by codesite-noreply＠google.com 29 Oct '13

29 Oct '13

Comment #4 on issue 57 by andrew.s...(a)gmail.com: Amarok OSD goes missing http://code.google.com/p/xmonad/issues/detail?id=57 This also happens to nagstamon. xprop output includes _NET_WM_STATE(ATOM) = _NET_WM_STATE_ABOVE, _NET_WM_STATE_STICKY, _NET_WM_STATE_SKIP_TASKBAR WM_HINTS(WM_HINTS): Client accepts input or input focus: True Initial state is Normal State. window id # of group leader: 0x1400001 _MOTIF_WM_HINTS(_MOTIF_WM_HINTS) = 0x2, 0x0, 0x0, 0x0, 0x0 _NET_WM_SYNC_REQUEST_COUNTER(CARDINAL) = 20971525 _NET_WM_WINDOW_TYPE(ATOM) = _NET_WM_WINDOW_TYPE_UTILITY _NET_WM_USER_TIME_WINDOW(WINDOW): window id # 0x1400004 WM_CLIENT_LEADER(WINDOW): window id # 0x1400001 _NET_WM_PID(CARDINAL) = 20371 WM_LOCALE_NAME(STRING) = "en_AU.UTF-8" WM_CLIENT_MACHINE(STRING) = "xps-l502x" WM_NORMAL_HINTS(WM_SIZE_HINTS): program specified minimum size: 102 by 17 window gravity: NorthWest WM_PROTOCOLS(ATOM): protocols WM_DELETE_WINDOW, WM_TAKE_FOCUS, _NET_WM_PING, _NET_WM_SYNC_REQUEST WM_CLASS(STRING) = "nagstamon", "Nagstamon" WM_ICON_NAME(STRING) = "nagstamon" _NET_WM_ICON_NAME(UTF8_STRING) = "nagstamon" WM_NAME(STRING) = "nagstamon" _NET_WM_NAME(UTF8_STRING) = "nagstamon" -- 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

Re: [xmonad] [Haskell-cafe] [ANN] xmobar 0.19 released
by Alfredo Di Napoli 28 Oct '13

28 Oct '13

Great news, thanks! On 27 October 2013 21:31, Jose A. Ortega Ruiz <jao(a)gnu.org> wrote: > > I've just released version 0.19 of xmobar, a lightweight system monitor > written in Haskell. > > Homepage: http://xmobar.org > Release notes: http://xmobar.org/releases.html > > As of this release, the old bug tracker at Google code is deprecated. > Please use [Github's tracker] for new bugs. > > Details: > > _New features_ > > - New monitor `BatteryN`, a variant of `BatteryP` that lets you > specify the name of the monitor in the template. > - Support for configuration file living in `XDG_CONFIG_HOME` (see > [github #99]). > - `Com` uses safer `runInteractiveProcess` instead of spawning a > shell (David McLean). If you're using shell expansion in your > `Com` (e.g. "~/bin/script") here's a workaround: `Run Com > "/bin/bash" ["-c", "~/bin/script"]` (cf. [github #127]). > - New plugin `UnsafeStdinReader` that allows actions from stdin. > Now it's possible to have clickable workspaces! > (Thiago Negri, see [github #125]). > - New monitor configuration option (`-x` or `--nastring`) that allows > specifying what string to display when a monitor is not available > (defaulting to "N/A"). Cf. [github #119]. > > _Bug fixes_ > > - Using the width options `-w`, `-m` and `-M` in battery monitors > watts display ([github #118]). > - Using the `-d` option in `CoreTemp` ([github #115]) > - Fix for systems not supporting PCRE regular expressions: we use > now BCEs, so regex-compat should be enough everywhere (see > [github #117]). > - Weather monitor: support for stations without name (Sergei > Trofimovich, [issue #65]). > > [Github's tracker]: https://github.com/jaor/xmobar/issues > [github #99]: https://github.com/jaor/xmobar/issues/115 > [github #115]: https://github.com/jaor/xmobar/issues/115 > [github #117]: https://github.com/jaor/xmobar/issues/117 > [github #125]: https://github.com/jaor/xmobar/issues/125 > [issue #65]: http://code.google.com/p/xmobar/issues/detail?id=65 > [github #118]: https://github.com/jaor/xmobar/issues/118 > [github #119]: https://github.com/jaor/xmobar/issues/119 > [github #127]: https://github.com/jaor/xmobar/issues/127 > _______________________________________________ > Haskell-Cafe mailing list > Haskell-Cafe(a)haskell.org > http://www.haskell.org/mailman/listinfo/haskell-cafe >

1 0

Re: [xmonad] Issue 210 in xmonad: xmonad.hs not accepted, xmonad.errors empty
by codesite-noreply＠google.com 18 Oct '13

18 Oct '13

Comment #7 on issue 210 by xming.song(a)gmail.com: xmonad.hs not accepted, xmonad.errors empty http://code.google.com/p/xmonad/issues/detail?id=210 xmonad.hs:18:18: Could not find module `XMonad.StackSet' Use -v to see a list of the files searched for. -- 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

avoidStruts not working on first start
by Kasza Péter 15 Oct '13

15 Oct '13

Hello XMonad list! For some reason avoidStruts doesn't seem to work the first time I log in, my dzen bars are hidden. However if I reload XMonad it seems to work fine. I can only reproduce this behaviour by rebooting the machine. This configuration used to work before, but recently I've switched to an ssd, so I suspect that the problem might be related to some race condition. Did anyone had this problem before? I've pasted my xmonad.hs here: http://pastebin.com/6nzAWCQa -- Best Regards, Peter Kasza http://www.iit.uni-miskolc.hu/~kasza1 mr.schyte(a)gmail.com () ascii ribbon campaign - against html e-mail /\ www.asciiribbon.org - against proprietary attachments

4 7

Xmonad.Util.Paste patch
by Daan van Rossum 08 Oct '13

08 Oct '13

This patch fixes pasting strings that contain whitespace characters -- Daan van Rossum

2 3

Problem with flickering white lines for some apps.
by Dominik Schrempf 04 Oct '13

04 Oct '13

Hello, I use xmonad standalone with an 3.11.2-1-ARCH kernel on an 21.5 inch iMac with the xf86video-nouveau driver (I log in using slim). For some applications I observe white flickering lines at the bottom right quadrant of the screen. If I let these windows float, the flickering still appears if I move them to the bottom right (I can only see the lines inside the window, not at the wallpaper), but it disappears if I move them more to the top left of the screen. Gnome applications like nautilus and gnome-terminal are not affected by these white lines, the wallpaper isn't either. Emacs, Okular, Firefox flicker though and I didn't try it out with other software. I am a bit at a loss, because I am not sure, how I could provide any log files or other evidence that could help me to solve the problem. Do you have any suggestions? I could provide my xmonad.hs. I noticed one other suspicious thing regarding the flickering applications: they lag 5 to 10 seconds when I start them. E.g. when I start emacs --daemon at the terminal it shows the Daemon does not run, starting emacs daemon and client. Warning: due to a long standing Gtk+ bug ... message, then it hangs for about 5 seconds. Any suggestions are highly appreciated! Cheers, Dominik

1 0

Is there a feature...
by emacstheviking 01 Oct '13

01 Oct '13

Hi, I've used xmonad for about two and a half years as a "stock" item from the repositories but I have always wanted (or wanted to know) if there is a feature or option that lets you create a new window on top of another one but inside the current frame? Imagine the screen, then using Alt+1 to Alt+9 to switch screens, I'd like to be able to do that inside a currently active region so instead of having another window appear and cause a relayout, I'd like the new open application to sit on top, a stack I guess...I used to use the Lisp "stumpwm" window manager and the ability to flip between windows but within another frame on the screen was brilliiant. I have a suspicion that it will be a "layout" class but I have no idea what one if it exists. Thanks, Sean.

4 3

Missing windows
by Jacek Generowicz 01 Oct '13

01 Oct '13

Hi, When experimenting with new layouts, I inadvertently deleted some workspaces, I'm not exactly sure how. All the windows that were on those workspaces have disappeared: they do not appear on any workspace. And yet xwininfo -tree -root reports that they still exist. Any ideas how to retrieve them?

2 2