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]: active-window-border-colour for monocle does not change correctly when workspace is switched #204

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

Originally created by @Fuann-Kinoko on GitHub (May 10, 2023).

Originally assigned to: @LGUG2Z on GitHub.

Describe the bug

When switching from one workspace to another, if there is only one single window in one of the workspaces, then the active-window-border-colour for monocle-kind does not change correctly

To Reproduce
Incorrect behavior 1:

  1. Assume workspace 1 has only 1 window, while workspace 2 has 2 windows.
  2. Enter monocle layout in workspace 2, which changes the color of border.
  3. Switch to workspace 1, the border color changes to the normal color, which is correct.
  4. Then switch back to workspace 2, however, the border color does not change to the "monocle color".

Incorrect behavior 2:

  1. Assume workspace 1 has only 1 window, while workspace 2 has 2 windows.
  2. Enter monocle layout in workspace 1, which won't change the color since there's only one window.
  3. Switch to workspace 2, everything's fine.
  4. Then switch back to workspace 1, the border disappears.

Expected behavior
active-window-border-colour for monocle updates seperately and correctly for different workspaces, according to the current workspace layout.

Operating System

OS Name:                   Microsoft Windows 10
OS Version:                10.0.19044 N/A Build 19044
Originally created by @Fuann-Kinoko on GitHub (May 10, 2023). Originally assigned to: @LGUG2Z on GitHub. **Describe the bug** When switching from one workspace to another, if there is only one single window in one of the workspaces, then the active-window-border-colour for monocle-kind does not change correctly **To Reproduce** Incorrect behavior 1: 1. Assume `workspace 1` has only 1 window, while `workspace 2` has 2 windows. 2. Enter monocle layout in `workspace 2`, which changes the color of border. 3. Switch to `workspace 1`, the border color changes to the normal color, which is correct. 4. Then switch back to `workspace 2`, however, the border color does not change to the "monocle color". Incorrect behavior 2: 1. Assume `workspace 1` has only 1 window, while `workspace 2` has 2 windows. 2. Enter monocle layout in `workspace 1`, which won't change the color since there's only one window. 3. Switch to `workspace 2`, everything's fine. 4. Then switch back to `workspace 1`, the border disappears. **Expected behavior** active-window-border-colour for monocle updates seperately and correctly for different workspaces, according to the current workspace layout. **Operating System** ``` OS Name: Microsoft Windows 10 OS Version: 10.0.19044 N/A Build 19044 ```
adam added the bug label 2026-01-05 14:48:59 +01:00
adam closed this issue 2026-01-05 14:48:59 +01:00
adam commented 2026-01-05 14:49:00 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (May 10, 2023):

Reproduced

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

@NathanealV commented on GitHub (Jan 15, 2024):

I've also noticed this issue when using Komorebi - have there been any updates on this?

@NathanealV commented on GitHub (Jan 15, 2024): I've also noticed this issue when using Komorebi - have there been any updates on this?
adam commented 2026-01-05 14:49:00 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Jan 15, 2024):

This was recently fixed on master and will be in the next release, forgot to link it to this issue!

fix commit: 5a6dcef7ea
video: https://www.youtube.com/watch?v=WiUVRRKHD4k

@LGUG2Z commented on GitHub (Jan 15, 2024): This was recently fixed on master and will be in the next release, forgot to link it to this issue! fix commit: https://github.com/LGUG2Z/komorebi/commit/5a6dcef7eaede5815318e7821121fd8476e3287f video: https://www.youtube.com/watch?v=WiUVRRKHD4k
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#204
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?