starred/komorebi
1
0
Fork 0
mirror of https://github.com/LGUG2Z/komorebi.git synced 2026-01-11 14:40:25 +01:00
Code Issues 87 Packages Projects Releases 10 Wiki Activity

[BUG]: Window borders misbehave with cycle-move command #223

New Issue
Closed
opened 2026-01-05 14:49:06 +01:00 by adam · 3 comments
adam commented 2026-01-05 14:49:06 +01:00
Owner
Copy Link

Originally created by @DWTW321 on GitHub (Jun 14, 2023).

Describe the bug
When using cycle-move instead of just move (for example I like to change alt + shift + k to komorebic cycle-move previous and alt + shift + j to komorebic cycle-move next), the borders misbehave, the border does not move with the window and instead stays in the previous position even though focus has stayed on the moved window. I hope that makes sense, kinda hard to describe.

To Reproduce
Steps to reproduce the behavior:

  1. Enable borders using the following in komorebi.ps1
     komorebic active-window-border-colour 245 194 231 --window-kind single
     komorebic active-window-border-colour 245 194 231 --window-kind monocle
     komorebic active-window-border-colour 245 194 231 --window-kind stack
     komorebic active-window-border enable
  1. Bind shortcuts to the cycle-move command in whkdrc using the followinf
    alt + shift + k           : komorebic cycle-move previous
    alt + shift + j            : komorebic cycle-move next
  1. Move a window using the cycle-move shortcuts

Expected behavior
The border of the window follows the window that has been moved using the cycle-move command.

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

For example:

    OS Name:                   Microsoft Windows 11 Home
    OS Version:                10.0.22621 N/A Build 22621

komorebic check Output
Provide the output of komorebic check

For example:

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

Looking for configuration files in C:\Users\jaska

Found komorebi.ps1; this file will be autoloaded by komorebi

Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is start
Originally created by @DWTW321 on GitHub (Jun 14, 2023). **Describe the bug** When using cycle-move instead of just move (for example I like to change `alt + shift + k` to `komorebic cycle-move previous` and `alt + shift + j` to `komorebic cycle-move next`), the borders misbehave, the border does not move with the window and instead stays in the previous position even though focus has stayed on the moved window. I hope that makes sense, kinda hard to describe. **To Reproduce** Steps to reproduce the behavior: 1. Enable borders using the following in komorebi.ps1 ```ps1 komorebic active-window-border-colour 245 194 231 --window-kind single komorebic active-window-border-colour 245 194 231 --window-kind monocle komorebic active-window-border-colour 245 194 231 --window-kind stack komorebic active-window-border enable ``` 2. Bind shortcuts to the `cycle-move` command in whkdrc using the followinf ``` alt + shift + k : komorebic cycle-move previous alt + shift + j : komorebic cycle-move next ``` 3. Move a window using the `cycle-move` shortcuts **Expected behavior** The border of the window follows the window that has been moved using the `cycle-move` command. **Operating System** Provide the output of `systeminfo | grep "^OS Name\|^OS Version"` For example: ``` OS Name: Microsoft Windows 11 Home OS Version: 10.0.22621 N/A Build 22621 ``` **`komorebic check` Output** Provide the output of `komorebic check` For example: ``` No KOMOREBI_CONFIG_HOME detected, defaulting to C:\Users\jaska Looking for configuration files in C:\Users\jaska Found komorebi.ps1; this file will be autoloaded by komorebi Found ~/.config/whkdrc; key bindings will be loaded from here when whkd is start ```
adam added the bug label 2026-01-05 14:49:06 +01:00
adam closed this issue 2026-01-05 14:49:06 +01:00
adam commented 2026-01-05 14:49:06 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jun 14, 2023):

Reproduced ^

@LGUG2Z commented on GitHub (Jun 14, 2023): Reproduced ^
adam commented 2026-01-05 14:49:06 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jun 14, 2023):

Fixed and will be part of the next release; if you want to use this now you can build the above commit from source, or go to the GitHub Actions job for that commit and download the prebuilt binaries from the pipeline artifacts 🎉

@LGUG2Z commented on GitHub (Jun 14, 2023): Fixed and will be part of the next release; if you want to use this now you can build the above commit from source, or go to the GitHub Actions job for that commit and download the prebuilt binaries from the pipeline artifacts 🎉
adam commented 2026-01-05 14:49:07 +01:00
Author
Owner
Copy Link

@DWTW321 commented on GitHub (Jun 14, 2023):

Fixed and will be part of the next release; if you want to use this now you can build the above commit from source, or go to the GitHub Actions job for that commit and download the prebuilt binaries from the pipeline artifacts 🎉

Woah, that was fast thanks!

@DWTW321 commented on GitHub (Jun 14, 2023): > Fixed and will be part of the next release; if you want to use this now you can build the above commit from source, or go to the GitHub Actions job for that commit and download the prebuilt binaries from the pipeline artifacts 🎉 Woah, that was fast thanks!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
0.1.36
apps-behaving-badly
bug
bug
cannot-reproduce
documentation
enhancement
github_actions
i-am-stuck
i-will-definitely-work-on-this
i-will-not-work-on-this
i-will-probably-work-on-this
komorebi
komorebi-bar
komorebic
performance
pull-request
Mirrored from GitHub Pull Request
 translation
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
adam
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/komorebi#223
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?