Originally created by @Zerogaku on GitHub (Apr 20, 2024).
Describe the bug
After closing a window sometimes the border will persist, and when starting komorebi up, the window border will be placed incorrectly, they sometimes still persist when swapping workspaces
To Reproduce
Steps to reproduce the behavior:
Startup komorebi from terminal with window borders enabled
Close Terminal window
Expected behavior
window border gets positioned properly when komorebi starts, and window border should not persist when window closes
Edition Windows 11 Home
Version 23H2
OS build 22631.3447
Experience Windows Feature Experience Pack 1000.22688.1000.0
komorebic check Output
KOMOREBI_CONFIG_HOME detected: C:\Users\Null\.config\komorebi
Looking for configuration files in C:\Users\Null\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
Additional context
I'm using ahk v2 to run apps:
#Enter::Run "wt.exe"
Originally created by @Zerogaku on GitHub (Apr 20, 2024).
**Describe the bug**
After closing a window sometimes the border will persist, and when starting komorebi up, the window border will be placed incorrectly, they sometimes still persist when swapping workspaces
**To Reproduce**
Steps to reproduce the behavior:
1. Startup komorebi from terminal with window borders enabled
2. Close Terminal window
**Expected behavior**
window border gets positioned properly when komorebi starts, and window border should not persist when window closes
**Screenshots and Videos**
https://github.com/LGUG2Z/komorebi/assets/144664603/490ecca9-4f5f-4fb0-bf52-8a6c208172db
https://github.com/LGUG2Z/komorebi/assets/144664603/3d067714-186f-46c4-802d-00cc765febec
**Operating System**
```
Edition Windows 11 Home
Version 23H2
OS build 22631.3447
Experience Windows Feature Experience Pack 1000.22688.1000.0
```
**`komorebic check` Output**
```
KOMOREBI_CONFIG_HOME detected: C:\Users\Null\.config\komorebi
Looking for configuration files in C:\Users\Null\.config\komorebi
Found komorebi.json; this file can be passed to the start command with the --config flag
No ~/.config/whkdrc found; you may not be able to control komorebi with your keyboard
```
**Additional context**
I'm using ahk v2 to run apps:
```
#Enter::Run "wt.exe"
```
adam
added the bug label 2026-01-05 14:49:53 +01:00
@azinsharaf commented on GitHub (Apr 22, 2024):
it is a known issue.
https://lgug2z.github.io/komorebi/common-workflows/active-window-border.html
"This feature is not considered stable, and you may encounter visual artifacts from time to time."
Pinning this for more visibility and to hopefully find others who are willing to work on fixing these remaining border bugs. 🤞
@LGUG2Z commented on GitHub (May 1, 2024):
Pinning this for more visibility and to hopefully find others who are willing to work on fixing these remaining border bugs. 🤞
@LGUG2Z commented on GitHub (May 11, 2024):
I'm working on a complete overhaul over the border code and I think I have nailed most of the common edge cases.
You can run from this branch if you'd like to try out the new approach (no config changes required) https://github.com/LGUG2Z/komorebi/tree/feature/border-manager
The retile command now also destroys and recreates all borders.
Closing this catch-all issue for now, please open new issues for specific edge cases you find in the future @nahid6970 @Zerogaku
@LGUG2Z commented on GitHub (May 12, 2024):
Ghost tiles have been fixed with https://github.com/LGUG2Z/komorebi/commit/6a1ed3bcaa8d1f6e75535778fc5bd51d9cc3c019
The retile command now also destroys and recreates all borders.
Closing this catch-all issue for now, please open new issues for specific edge cases you find in the future @nahid6970 @Zerogaku
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @Zerogaku on GitHub (Apr 20, 2024).
Describe the bug
After closing a window sometimes the border will persist, and when starting komorebi up, the window border will be placed incorrectly, they sometimes still persist when swapping workspaces
To Reproduce
Steps to reproduce the behavior:
Expected behavior
window border gets positioned properly when komorebi starts, and window border should not persist when window closes
Screenshots and Videos
https://github.com/LGUG2Z/komorebi/assets/144664603/490ecca9-4f5f-4fb0-bf52-8a6c208172db
https://github.com/LGUG2Z/komorebi/assets/144664603/3d067714-186f-46c4-802d-00cc765febec
Operating System
komorebic checkOutputAdditional context
I'm using ahk v2 to run apps:
@azinsharaf commented on GitHub (Apr 22, 2024):
it is a known issue.
https://lgug2z.github.io/komorebi/common-workflows/active-window-border.html
"This feature is not considered stable, and you may encounter visual artifacts from time to time."
@markox92 commented on GitHub (May 1, 2024):
Any news about this problem ?
@LGUG2Z commented on GitHub (May 1, 2024):
Pinning this for more visibility and to hopefully find others who are willing to work on fixing these remaining border bugs. 🤞
@LGUG2Z commented on GitHub (May 1, 2024):
Moving discussion of https://github.com/LGUG2Z/komorebi/issues/801 here
@LGUG2Z commented on GitHub (May 11, 2024):
I'm working on a complete overhaul over the border code and I think I have nailed most of the common edge cases.
You can run from this branch if you'd like to try out the new approach (no config changes required) https://github.com/LGUG2Z/komorebi/tree/feature/border-manager
@LGUG2Z commented on GitHub (May 12, 2024):
Ghost tiles have been fixed with https://github.com/LGUG2Z/komorebi/commit/6a1ed3bcaa8d1f6e75535778fc5bd51d9cc3c019
The retile command now also destroys and recreates all borders.
Closing this catch-all issue for now, please open new issues for specific edge cases you find in the future @nahid6970 @Zerogaku