[BUG]: cycle-move-to-monitor in sequence only works twice before getting in a focus loop, counter to the two ways I'd expect this to work #318

New Issue

2026-01-05T14:49:40+01:00

adam commented

2026-01-05 14:49:40 +01:00

Originally created by @NireBryce on GitHub (Mar 24, 2024).

Describe the bug
When you use cycle-move-to-monitor multiple times in a row, it will move the first window to the new monitor, move the second window in that workspace, and then immediately start moving them back from the second window.

This matches neither expected behavior, "focus follows the window you moved" or "focus stays in the location you're moving from"

To Reproduce
Steps to reproduce the behavior:
0. have more than 2 windows open, have 2 monitors

focus window 4
cycle-move-to-monitor next moves window_4 FROM display_1 to display_2
cycle-move-to-monitor next moves window_3 FROM display_1 to display_2
cycle-move-to-monitor next moves window_4 FROM display_2 to display_1
cycle-move-to-monitor next moves window_3 FROM display_2 to display_1
cycle-move-to-monitor next moves window_4 FROM display_1 to display_2
cycle-move-to-monitor next moves window_3 FROM display_1 to display_2

Expected behavior
focus moves to the next window in the monitor you're moving applications from
OR
focus moves to the window you just moved, such that cycle-move-to-monitor next sends it to the next monitor in the ring
Screenshots and Videos
Add screenshots and videos to help explain your problem.

Operating System
Provide the output of systeminfo | grep "^OS Name\|^OS Version"

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22631 N/A Build 22631

komorebic check Output
Provide the output of komorebic check

No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\elly

Looking for configuration files in C:\Users\elly

Found komorebi.json; this file can be passed to the start command with the --config flag

Found C:\Users\elly\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag

Additional context
active focus border also breaks

Originally created by @NireBryce on GitHub (Mar 24, 2024). **Describe the bug** When you use cycle-move-to-monitor multiple times in a row, it will move the first window to the new monitor, move the second window in that workspace, and then immediately start moving them back from the second window. This matches neither expected behavior, "focus follows the window you moved" or "focus stays in the location you're moving from" **To Reproduce** Steps to reproduce the behavior: 0. have more than 2 windows open, have 2 monitors 1. focus window 4 2. `cycle-move-to-monitor next` moves window_4 FROM display_1 to display_2 3. `cycle-move-to-monitor next` moves window_3 FROM display_1 to display_2 4. `cycle-move-to-monitor next` moves window_4 FROM display_2 to display_1 5. `cycle-move-to-monitor next` moves window_3 FROM display_2 to display_1 6. `cycle-move-to-monitor next` moves window_4 FROM display_1 to display_2 7. `cycle-move-to-monitor next` moves window_3 FROM display_1 to display_2 **Expected behavior** focus moves to the next window in the monitor you're moving applications from OR focus moves to the window you just moved, such that `cycle-move-to-monitor next` sends it to the next monitor in the ring **Screenshots and Videos** Add screenshots and videos to help explain your problem. **Operating System** Provide the output of `systeminfo | grep "^OS Name\|^OS Version"` ``` OS Name: Microsoft Windows 11 Home OS Version: 10.0.22631 N/A Build 22631 ``` **`komorebic check` Output** Provide the output of `komorebic check` ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\elly Looking for configuration files in C:\Users\elly Found komorebi.json; this file can be passed to the start command with the --config flag Found C:\Users\elly\.config\whkdrc; key bindings will be loaded from here when whkd is started, and you can start it automatically using the --whkd flag ``` **Additional context** active focus border also breaks

adam added the bug label 2026-01-05 14:49:40 +01:00

adam closed this issue

2026-01-05 14:49:40 +01:00

adam commented

2026-01-05 14:49:41 +01:00

@LGUG2Z commented on GitHub (May 12, 2024):

I believe this was also fixed as part of https://github.com/LGUG2Z/komorebi/commit/1b30561989e79beccac5ed459eca53912268d914

Please re-open the issue if the issue still persists after that commit

@LGUG2Z commented on GitHub (May 12, 2024): I believe this was also fixed as part of https://github.com/LGUG2Z/komorebi/commit/1b30561989e79beccac5ed459eca53912268d914 Please re-open the issue if the issue still persists after that commit

adam referenced this issue

2026-01-05 14:53:12 +01:00

[PR #318] [CLOSED] chore(deps): bump goreleaser/goreleaser-action from 3 to 4 #856

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/komorebi#318