November 2009 - xmonad

Issue 338 in xmonad: XMonad.Util.Paste.pasteString
by codesite-noreply＠google.com 28 Jun '15

28 Jun '15

Status: Started Owner: vogt.adam Labels: Type-Defect Priority-Medium Component-Contrib New issue 338 by vogt.adam: XMonad.Util.Paste.pasteString http://code.google.com/p/xmonad/issues/detail?id=338 newfish in #xmonad had trouble pasting urls with pasteString. Note that the difficulties with stringToKeysym are already noted in the module's documentation. What steps will reproduce the problem? 1. Add a binding for > , ( "M-S-b", pasteString "http://code.google.com" ) What is the expected output? What do you see instead? It pastes httpcodegooglecom I've pushed a patch that changes the paste to "http;//code.google.com", which is still wrong with the ';' vs ':'. I believe that other : Sat Nov 14 17:37:26 EST 2009 Adam Vogt <vogt.adam(a)gmail.com> * Bypass more of stringToKeysym in U.Paste But there doesn't seem to be a simple way to detect whether a symbolic key must be sent using shiftMask. ,("M-d", pasteString "?><://\\{}[]" ) gives: /.,;//\[][] Is there a proper way to recognize when a symbol should be sent with shiftMask? -- 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 2

Re: Issue 97 in xmonad: xmonad stops responding to keyboard input after running xscreensaver
by codesite-noreply＠google.com 31 Mar '14

31 Mar '14

Updates: Status: Invalid Comment #29 on issue 97 by byorgey: xmonad stops responding to keyboard input after running xscreensaver http://code.google.com/p/xmonad/issues/detail?id=97 I'm closing this since 1) it hasn't happened to me in a very long time 2) no one seems to have reported a similar problem for a year 3) it was never even clear whether this really was an xmonad problem---I suspect it wasn't. Feel free to reopen if you are having a similar issue and none of the solutions proposed in the comments work for you. -- 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 11

Re: Issue 273 in xmonad: Binding multiple keys to the same keysym fails for xmonad hotkeys
by codesite-noreply＠google.com 02 Mar '13

02 Mar '13

Updates: Labels: Type-Enhancement Component-Core Usability Comment #2 on issue 273 by byorgey: Binding multiple keys to the same keysym fails for xmonad hotkeys http://code.google.com/p/xmonad/issues/detail?id=273 (No comment was entered for this change.) -- 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 5

Re: Issue 158 in xmonad: _NET_WORKAREA support
by codesite-noreply＠google.com 01 Mar '13

01 Mar '13

Updates: Status: Accepted Labels: -Type-Defect Type-Enhancement Comment #6 on issue 158 by byorgey: _NET_WORKAREA support http://code.google.com/p/xmonad/issues/detail?id=158 (No comment was entered for this change.) -- 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 11

Issue 326 in xmonad: floating windows can break Actions.UpdatePointer
by codesite-noreply＠google.com 20 Feb '13

20 Feb '13

Status: New Owner: ---- New issue 326 by OrbisVicis: floating windows can break Actions.UpdatePointer http://code.google.com/p/xmonad/issues/detail?id=326 What steps will reproduce the problem? 1. UpdatePointer (TowardsCentre 1 1) 2. spiralWithDir West CW (4/5) 3. scratchpadManageHook (W.RationalRect 0.25 0.3 0.5 0.55) 4. Open two windows in the spiral layout, launch the scratchpad, and start tabbing 5. One of the windows will never receive focus -- 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 3

Re: Issue 306 in xmonad: Magnifier: keep magnified status if transient focused
by codesite-noreply＠google.com 11 Jan '13

11 Jan '13

Updates: Status: Accepted Labels: Type-Enhancement Component-Contrib Comment #3 on issue 306 by byorgey: Magnifier: keep magnified status if transient focused http://code.google.com/p/xmonad/issues/detail?id=306 This shouldn't be too difficult to implement (either Riccardo or Daniel's proposed behavior) given the new extensible state. -- 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 3

Re: Issue 304 in xmonad: CycleWS should actually track workspace history rather than depending on order of hidden workspaces
by codesite-noreply＠google.com 09 Jan '13

09 Jan '13

Updates: Summary: CycleWS should actually track workspace history rather than depending on order of hidden workspaces Status: Accepted Labels: Type-Enhancement Component-Contrib Comment #2 on issue 304 by byorgey: CycleWS should actually track workspace history rather than depending on order of hidden workspaces http://code.google.com/p/xmonad/issues/detail?id=304 The problem is that toggleWS simply assumes that the "previous workspace" is the one at the head of xmonad's internal list of hidden workspaces. But there are various operations other than switching away from a workspace which will also place it at the head of this list. There is nothing special about scratchpads here; if you shift any window on the current workspace to another workspace, that other workspace will now be the "previous workspace" as far as toggleWS is concerned. The real problem is that the order of workspaces in xmonad's list of hidden workspaces is not really supposed to mean anything, so toggleWS is depending on undefined behavior. The only way to really fix this would be to have CycleWS track the workspace history itself. Here's a sketch of a possible solution: CycleWS could use the new extensible state to track the workspace history, and provide something to put in the logHook that would notify CycleWS every time the current workspace changes. (It would be nicer if putting something in the logHook was not necessary, but otherwise it is not clear how CycleWS would find out about workspace changes.) -- 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 3

Re: Issue 316 in xmonad: AvoidStruts gives wrong window heights with vertically stacked screens
by codesite-noreply＠google.com 03 Jan '13

03 Jan '13

Comment #3 on issue 316 by liskni.si: AvoidStruts gives wrong window heights with vertically stacked screens http://code.google.com/p/xmonad/issues/detail?id=316 http://www.haskell.org/pipermail/xmonad/2009-November/009145.html This, I believe, fixed the issue and discusses why it changes the strut semantics incompatibly with wm-spec. -- 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 2

Re: Issue 211 in xmonad: Error output inconsistency
by codesite-noreply＠google.com 31 Dec '12

31 Dec '12

Comment #1 on issue 211 by byorgey: Error output inconsistency http://code.google.com/p/xmonad/issues/detail?id=211 Status? This seems like a pretty simple change, do other developers have an opinion on this? -- 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 1

Re: Issue 177 in xmonad: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol
by codesite-noreply＠google.com 04 Dec '12

04 Dec '12

Comment #24 on issue 177 by vogt.adam: xmonad does not follow ICCCM and ignores WM_TAKE_FOCUS protocol http://code.google.com/p/xmonad/issues/detail?id=177 Geoff Reedy's last patch doesn't apply cleanly against latest darcs (due to the merging of extensible state stuff). Attached is a patch bundle including the old ones that probably works as the old one did. Attachments: track-currently-processing-event.dpatch 16.1 KB -- 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

4 108