- xmonad - Haskell.org

Bug in X.A.Submap
by Khudyakov Alexey 06 Aug '09

06 Aug '09

Hello I've submitted a bug some time ago. I didn't get any response, so I'm reposing it to ML. http://code.google.com/p/xmonad/issues/detail?id=295 Submap actions don't work when in russian layout. In english layout it does work without problem. Standard xmonad key bindings work in both layouts. I'm using version from darcs. 0.8 is affected to AFAIR. Layout are set up with XCB. $ setxkbmap -model pc104 -layout us,ru -variant basic,winkeys $ setxkbmap -option -option \ "grp_led:scroll,grp:shifts_toggle,compose:menu,ctrl:nocaps" Below is snippet from X.A.Submap. Quick research shown that keymasks m and m' has bit (1<<13) set when russian layout chosen. I have no idea how to interpret it. All valid keymasks are <= (1<<12) as declared in X11 headers. > -- | Like 'submap', but executes a default action if the key did not match. > submapDefault :: X () -> M.Map (KeyMask, KeySym) (X ()) -> X () > submapDefault def keys = do > XConf { theRoot = root, display = d } <- ask > > io $ grabKeyboard d root False grabModeAsync grabModeAsync currentTime > > (m, s) <- io $ allocaXEvent $ \p -> fix $ \nextkey -> do > maskEvent d keyPressMask p > KeyEvent { ev_keycode = code, ev_state = m } <- getEvent p > keysym <- keycodeToKeysym d code 0 > if isModifierKey keysym > then nextkey > else return (m, keysym) > > m' <- cleanMask m > > maybe def id (M.lookup (m', s) keys) > > io $ ungrabKeyboard d currentTime -- Khudyakov Alexey

3 6

Issue 295 in xmonad: X.A.Submap doesn't work in russian layout.
by codesite-noreply＠google.com 06 Aug '09

06 Aug '09

Updates: Status: Fixed Comment #1 on issue 295 by byorgey: X.A.Submap doesn't work in russian layout. http://code.google.com/p/xmonad/issues/detail?id=295 Fixed by patch from Alexey. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 305 in xmonad: Copy and paste by middle click does not work
by codesite-noreply＠google.com 05 Aug '09

05 Aug '09

Comment #5 on issue 305 by florian.bw: Copy and paste by middle click does not work http://code.google.com/p/xmonad/issues/detail?id=305 Yep, I will try that. Once KDE 4.3 is out in the Arch repositories :). So in a day or two. I use X without xorg.conf, on a notebook touchpad with middle mouse button (Dell E6400). The confusing thing is that it sometimes work and sometimes not. I'll test those apps. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

3 2

Issue 305 in xmonad: Copy and paste by middle click does not work
by codesite-noreply＠google.com 04 Aug '09

04 Aug '09

Comment #4 on issue 305 by daniel.wagner: Copy and paste by middle click does not work http://code.google.com/p/xmonad/issues/detail?id=305 Can you verify that this is working as expected in another window manager (on the same machine, with the same xorg.conf, in the same terminal emulator, etc.)? -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Issue 305 in xmonad: Copy and paste by middle click does not work
by codesite-noreply＠google.com 04 Aug '09

04 Aug '09

Comment #3 on issue 305 by florian.bw: Copy and paste by middle click does not work http://code.google.com/p/xmonad/issues/detail?id=305 I still experience this issue, also, for example, from screen (copy mode) to the same terminal, after escaping the copy mode. Is there any other way to copy? Like control-C in text fields. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

What happened to
by Christian Walther 03 Aug '09

03 Aug '09

Hi list, when browsing xmonads website, accessing http://www.xmonad.org/xmonad-docs/xmonad-contrib/XMonad-Doc-Extending.html#5 XMonad.Layout.ScratchWorkspace doesn't seem to be available anymore. At least the webserver returns a: "Not Found The requested URL /xmonad-docs/xmonad-contrib/XMonad-Layout-ScratchWorkspace.html was not found on this server. Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request." It seems to be missing from contrib alltogether, since trying to import it to xmonad.hs results in an error, too: xmonad.hs:23:7: Could not find module `XMonad.Layout.ScratchWorkspace': it is not a module in the current program, or in any known package. Shouldn'it it be removed from the website? And is there any other way to get something like a Scratchpad? Regards Christian Walther

2 1

code for moving/resizing windows in xmonad wiki
by Chengqi Song 31 Jul '09

31 Jul '09

Dear All, Just for your information: http://haskell.org/haskellwiki/Xmonad/Config_archive /lars' xmonad.hs Move/Resize windows using keyboard easily: 1. move window around using M-Arrows. 2. resize windows using C-Arrows. 3. Holding <Shift> to move/resize 2 pixels per step instead of 20 pixels. Please find the lines below comment "-- moving floating window with key" to see details. Thanks to the powerful haskell, the definition for those 4*2*2 = 16 key bindings is quite simple: -- moving floating window with key [(c ++ m ++ k, withFocused $ f (d x)) | (d, k) <- zip [\a->(a, 0), \a->(0, a), \a->(0-a, 0), \a->(0, 0-a)] ["<Right>", "<Down>", "<Left>", "<Up>"] , (f, m) <- zip [keysMoveWindow, \d -> keysResizeWindow d (0, 0)] ["M-", "M-S-"] , (c, x) <- zip ["", "C-"] [20, 2]] I personally found it's very convenient. Hope it can help who want keybindings for moving/resizing windows. lars

1 0

Issue 307 in xmonad: pidgin message windows change repeatedly grow on a multi-monitor setup
by codesite-noreply＠google.com 31 Jul '09

31 Jul '09

Comment #1 on issue 307 by daniel.spoonhower: pidgin message windows change repeatedly grow on a multi-monitor setup http://code.google.com/p/xmonad/issues/detail?id=307 This also occurs in my setup, but not just with Pidgin. It also with gnome-volume-control. Both are managed with doFloat. The ratio between the sizes of two instances of a given window is roughly the same as the ratio between my screens. A seemingly-related (but less intrusive behavior) also occurs with gnuplot: windows that appear on the larger screen are first rendered as if they appeared on the smaller screen (meaning that the plot only covers a portion of the window); the plot is then automatically scaled to fill the entire window. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0

Fwd: [xmonad] Unmarking modules 'Unstable' in contrib
by Braden Shepherdson 30 Jul '09

30 Jul '09

Resending to the list, sorry Brent for the duplicate. ---------- Forwarded message ---------- From: Braden Shepherdson <braden.shepherdson(a)gmail.com> Date: Thu, Jul 30, 2009 at 5:44 PM Subject: Re: [xmonad] Unmarking modules 'Unstable' in contrib To: Brent Yorgey <byorgey(a)seas.upenn.edu> Even when our modules do change, they almost always change in a backward-compatible way, since we try to avoid breaking configs. This sounds fine to me. Braden Shepherdson shepheb On Thu, Jul 30, 2009 at 5:12 PM, Brent Yorgey <byorgey(a)seas.upenn.edu>wrote: > On Wed, Jul 29, 2009 at 08:10:52PM -0400, Adam Vogt wrote: > > Hello, > > > > Most (152/159) modules are marked as unstable in contrib. A good number > of > > these 'unstable' modules have not been modified since a number of > releases. > > > > Here's a rough total number of modules with a last-modified date (per > year): > > > > > (for x in `find .`; do; (darcs changes $x | tail -n 2 | head -n 1); > done) > lastmod > > > for x in {2007,2008,2009}; do; grep $x lastmod | wc -l; done > > 64 > > 43 > > 17 > > > > I wouldn't trust those numbers, since the total falls short of 159, but > the > > point still stands: many so-called unstable modules have not changed in a > > long time, which could make it difficult for users to avoid modules that > > may actually change. > > > > Does anybody mind if I change the oldest modules (unchanged since 1.5 > > years) to be stable? > > Sounds good to me. I think most of the 'unstable' designations are > because of cargo-culting someone else's module comments. That and the > fact that by definition you would only change the stability > designation when you are not changing anything. No one ever thinks > "gee, it's been 6 months since I even thought about that module, > better go back and change it to 'stable'". =) > > -Brent > _______________________________________________ > xmonad mailing list > xmonad(a)haskell.org > http://www.haskell.org/mailman/listinfo/xmonad >

1 0

Issue 307 in xmonad: pidgin message windows change repeatedly grow on a multi-monitor setup
by codesite-noreply＠google.com 29 Jul '09

29 Jul '09

Status: New Owner: ---- New issue 307 by matt.fowles: pidgin message windows change repeatedly grow on a multi-monitor setup http://code.google.com/p/xmonad/issues/detail?id=307 Initial set up requires two monitors of different resolutions (call them "large" and "small") On "small monitor" 1. bring up the pidgin buddy list 2. double click a contact (this should bring up a message window in the floating layer) 3. give the message window focus and hit escape (this should dismiss the message window) 4. repeat steps 2-3 several times. Each time the message window should be the same size as it was before. Repeat everything on "large monitor". On my machine everything works correctly for the "small" case; however, each time I open the message window in the "large" case the window has grown from the last time it was opened. This leads to ever growing message windows (unless I resize them by hand, which is my current periodic work around). I am using: xmonad 0.8 ubuntu 9.04 Attachments: xmonad.hs 5.3 KB xmonad.recompile 0 bytes -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings

1 0