Move a window to the next lowest numbered empty workspace #369

wgmayer0 · 2022-01-20T06:17:43Z

wgmayer0
Jan 20, 2022

How would I move the currently selected window on any workspace to the lowest numbered empty workspace? Can it also switch to the workspace that the window is moved to?

For example,
-I have msn.com on workspace 1
-I have a tall screen on workspace 2 with 2 windows open:
-Code
-A reference sheet

Let's say I run the the desired code on a new instance of my browser while I am on workspace 5. The desired behavior is that xmonad moves my browser window to workspace 3 because 1 and 2 are occupied.

Now I close msn.com on workspace 1 so that all I have is:
-Workspace 1 is empty
-I have a tall screen on workspace 2 with 2 windows open:
-Code
-A reference sheet
-I have that same browser window on workspace 3

Assuming I am on workspace 3 currently and I hit the shortcut key, my browser window and me should immediately move to workspace 1 because it is lower than 3 and it is currently empty.

Let me know if this is clear or not. Thanks!

Answered by geekosaur

Jan 20, 2022

XMonad.Actions.CycleWS supports much of what you want, although it would select the first empty workspace in the direction you specify (so if you have two empty workspaces before workspace 5 it would select the second instead of the first). The operations it provides only do one or the other of moving the window or viewing the workspace, but it also provides a more general function that would let you do both at once.

The thing you'd bind to your chosen key would look something like

doTo Prev emptyWS (\ws -> withFocused (\w -> windows (W.view ws <> W.shiftWin ws w)))

Note that I have not tested this and it may not be quite what you want.

View full answer

geekosaur · 2022-01-20T11:36:31Z

geekosaur
Jan 20, 2022
Maintainer

XMonad.Actions.CycleWS supports much of what you want, although it would select the first empty workspace in the direction you specify (so if you have two empty workspaces before workspace 5 it would select the second instead of the first). The operations it provides only do one or the other of moving the window or viewing the workspace, but it also provides a more general function that would let you do both at once.

The thing you'd bind to your chosen key would look something like

doTo Prev emptyWS (\ws -> withFocused (\w -> windows (W.view ws <> W.shiftWin ws w)))

Note that I have not tested this and it may not be quite what you want.

11 replies

wgmayer0 Jan 20, 2022
Author

XMonad will use ghc to recompile, because "/home/wgm/.xmonad/build" does not exist.
Error detected while loading xmonad configuration file: /home/wgm/.xmonad/xmonad.hs

xmonad.hs:62:106: error:
    • No instance for (Monoid
                         (W.StackSet
                            WorkspaceId (Layout Window) Window ScreenId ScreenDetail))
        arising from a use of ‘<+>’
    • In the first argument of ‘windows’, namely
        ‘(W.view ws <+> W.shiftWin ws w)’
      In the expression: windows (W.view ws <+> W.shiftWin ws w)
      In the first argument of ‘withFocused’, namely
        ‘(\ w -> windows (W.view ws <+> W.shiftWin ws w))’
   |
62 |         , ("M-C-<Space>", doTo Prev EmptyWS getSortByIndex (\ws -> withFocused (\w -> windows (W.view ws <+> W.shiftWin ws w))))
   |                 ^^^

Please check the file for errors.

xmonad: xmessage: executeFile: does not exist (No such file or directory)

geekosaur Jan 20, 2022
Maintainer

Hrm, that seems wrong.

Wait, WindowSet vs. WindowSet -> WindowSet. Lemme dig.

geekosaur Jan 20, 2022
Maintainer

Right, I'm confusing windows with a manageHook. Replace <+> with ..

wgmayer0 Jan 20, 2022
Author

It compiles and is functioning now but it goes back one workspace. Anyone have ideas on how to get the original stated functionality? Seems we are getting closer.

geekosaur Jan 20, 2022
Maintainer

It should go back to the previous empty workspace from the one you are currently on. As I stated earlier, it isn't really possible to have it go forward from the first workspace.

wgmayer0 · 2022-01-20T18:29:59Z

wgmayer0
Jan 20, 2022
Author

Is there anyway I can upgrade to the latest version? I don't have any version constraints set and I am running pacman package manager on Arch Linux

…

On Thu, Jan 20, 2022, 1:25 PM brandon s allbery kf8nh < ***@***.***> wrote: Sigh, that's right, you're still on 0.15. You want EmptyWS instead of emptyWS. — Reply to this email directly, view it on GitHub <#369 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ARTB5TORVNLIFDD6XYYN5STUXBHQVANCNFSM5ML3HS6A> . Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>. You are receiving this because you authored the thread.Message ID: ***@***.***>

1 reply

geekosaur Jan 20, 2022
Maintainer

My understanding is that there is no longer a maintainer for the package on Arch, so you would have to install it via cabal or stack instead.

wgmayer0 · 2022-01-20T19:27:16Z

wgmayer0
Jan 20, 2022
Author

Basically it works, but it is taking me to the last workspace available and empty instead of the first one On Thu, Jan 20, 2022 at 11:08:24AM -0800, brandon s allbery kf8nh wrote:

1 reply

geekosaur Jan 20, 2022
Maintainer

Right, that's what I warned you it would do. There's no good way to do the other without some weird corner cases (like never putting anything on workspace 1).

wgmayer0 · 2022-01-20T19:36:56Z

wgmayer0
Jan 20, 2022
Author

Ok thank you I changed the `Prev` to `Next` and that functionality is close to what I am looking for. Thanks!

0 replies

wgmayer0 · 2022-03-16T04:11:46Z

wgmayer0
Mar 16, 2022
Author

I was thinking that this may work if I use the existing code:
Figure 1

        , ("M-C-<Space>", doTo Next EmptyWS getSortByIndex (\ws -> withFocused (\w -> windows (W.view ws . W.shiftWin ws w))) >> asks (layoutHook . config) >>= setLayout)

But added to the algorithm. If before it does the above step, it always moves the window to workspace 9, it will always go to the next available window that is closest to 1 or is 1. For example, let's say that the target window is on workspace 3. I have a window open on workspace 2. There is also a window open on workspace 1. And one open on workspace 9. If I closed the one on 2, and run the code, it would ideally send the window to workspace 9 (This is the part I need help with) who is already populated. Once there, the code from figure 1 would skip 1 because it is populated. 2 is not populated now since I closed it. The window will land on 2. Thus it started on 3, a workspace greater than 2 but was able to land back a window, keeping it as close as possible to 1. It would be a nice algorithm if I can get some help on how to send the window to 9, then run figure 1's code.

3 replies

wgmayer0 Mar 16, 2022
Author

Also it is ok if 9 is empty in regards to corner cases. I'd like it to default there.

wgmayer0 Mar 22, 2022
Author

Checking on this

geekosaur Mar 23, 2022
Maintainer

Sorry, I've been chewing on this a bit trying to figure a better way to do it. (Like I have a better way to do the earlier one that avoids calling windows for each individual window.) But I'm not thinking of one.

You would need to put before the doTo something like

withFocused (windows . W.shiftWin "9") >>

(so the doTo follows the >>). The problem is, after that it's not focused any more. Hm.

withFocused (\w -> windows (W.shiftWin "9" w) >>
                   doTo Next emptyWS getSortByIndex (\ws -> windows (W.view ws . W.shiftWin ws w))) >>
asks (layoutHook . config) >>= setLayout

This at least typechecks here.

wgmayer0 · 2022-03-24T06:02:53Z

wgmayer0
Mar 24, 2022
Author

1 reply

wgmayer0 Mar 24, 2022
Author

Changed emptyWS to EmptyWS.

After restarting, looks like there is still a problem: it functions the same as I had before.

geekosaur · 2022-03-24T16:50:22Z

geekosaur
Mar 24, 2022
Maintainer

Sorry, forgot you're still on 0.15, and 0.17.0 throws deprecation warnings with EmptyWS.

And I was afraid of it not working; I suspect it's got to shift you to workspace 9 for the doTo to operate correctly. It's a minor change but may be annoying in use.

withFocused (\w -> windows (W.view "9" . W.shiftWin "9" w) >>
                   doTo Next EmptyWS getSortByIndex (\ws -> windows (W.view ws . W.shiftWin ws w))) >>
asks (layoutHook . config) >>= setLayout

0 replies

wgmayer0 · 2022-03-24T17:00:15Z

wgmayer0
Mar 24, 2022
Author

Wow it works beautifully! Thank you for your help! Great work!! It does EXACTLY what I was looking for! You really understood the problem. Thank you

0 replies

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Move a window to the next lowest numbered empty workspace #369

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Replies: 8 comments 17 replies

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{title}}

{{editor}}'s edit

{{editor}}'s edit

Select a reply

Move a window to the next lowest numbered empty workspace #369

wgmayer0 Jan 20, 2022

Replies: 8 comments · 17 replies

geekosaur Jan 20, 2022 Maintainer

wgmayer0 Jan 20, 2022 Author

geekosaur Jan 20, 2022 Maintainer

geekosaur Jan 20, 2022 Maintainer

wgmayer0 Jan 20, 2022 Author

geekosaur Jan 20, 2022 Maintainer

wgmayer0 Jan 20, 2022 Author

geekosaur Jan 20, 2022 Maintainer

wgmayer0 Jan 20, 2022 Author

geekosaur Jan 20, 2022 Maintainer

wgmayer0 Jan 20, 2022 Author

wgmayer0 Mar 16, 2022 Author

wgmayer0 Mar 16, 2022 Author

wgmayer0 Mar 22, 2022 Author

geekosaur Mar 23, 2022 Maintainer

wgmayer0 Mar 24, 2022 Author

wgmayer0 Mar 24, 2022 Author

geekosaur Mar 24, 2022 Maintainer

wgmayer0 Mar 24, 2022 Author

wgmayer0
Jan 20, 2022

Replies: 8 comments 17 replies

geekosaur
Jan 20, 2022
Maintainer

wgmayer0 Jan 20, 2022
Author

geekosaur Jan 20, 2022
Maintainer

geekosaur Jan 20, 2022
Maintainer

wgmayer0 Jan 20, 2022
Author

geekosaur Jan 20, 2022
Maintainer

wgmayer0
Jan 20, 2022
Author

geekosaur Jan 20, 2022
Maintainer

wgmayer0
Jan 20, 2022
Author

geekosaur Jan 20, 2022
Maintainer

wgmayer0
Jan 20, 2022
Author

wgmayer0
Mar 16, 2022
Author

wgmayer0 Mar 16, 2022
Author

wgmayer0 Mar 22, 2022
Author

geekosaur Mar 23, 2022
Maintainer

wgmayer0
Mar 24, 2022
Author

wgmayer0 Mar 24, 2022
Author

geekosaur
Mar 24, 2022
Maintainer

wgmayer0
Mar 24, 2022
Author