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]: Can't move away from an empty workspace #135

New Issue
Closed
opened 2026-01-05 14:48:29 +01:00 by adam · 1 comment
adam commented 2026-01-05 14:48:29 +01:00
Owner
Copy Link

Originally created by @es183923 on GitHub (Aug 24, 2022).

Describe the bug
After commit be5945c64b, it seems that I can't switch from a workspace with no windows/containers to a diferent one.

To Reproduce
Steps to reproduce the behavior:

  1. use the commit be5945c
  2. in config, have some workspaces set up, and shortcuts, eg:
Run, komorebic ensure-workspaces 0 5, , Hide

!1::Run, komorebic focus-workspace 0, , Hide
!2::Run, komorebic focus-workspace 1, , Hide
!3::Run, komorebic focus-workspace 2, , Hide
!4::Run, komorebic focus-workspace 3, , Hide
!5::Run, komorebic focus-workspace 4, , Hide
  1. start komorebi
  2. switch to an empty workspace (!2)
  3. attempt to switch back (!1), and see that you're stuck on the empty workspace.

Expected behavior
can't switch to a different workspace

Screenshots and Videos

https://user-images.githubusercontent.com/72744903/186525947-9dafa790-126b-4896-bb35-a0d035db40fa.mp4

Observe top left corner showing workspace number
Bottom left showing keystrokes
terminal shows git info and commands used to compile and run komorebi

Operating System

OS Name:                   Microsoft Windows 11 Home
OS Version:                10.0.22000 N/A Build 22000

Additional context
somme other autothotkey scripts, but shouldn't interfere.

Originally created by @es183923 on GitHub (Aug 24, 2022). **Describe the bug** After commit https://github.com/LGUG2Z/komorebi/commit/be5945c64b614784cb3b5d16887c00388884c36d, it seems that I can't switch from a workspace with no windows/containers to a diferent one. **To Reproduce** Steps to reproduce the behavior: 1. use the commit be5945c 2. in config, have some workspaces set up, and shortcuts, eg: ```ahk Run, komorebic ensure-workspaces 0 5, , Hide !1::Run, komorebic focus-workspace 0, , Hide !2::Run, komorebic focus-workspace 1, , Hide !3::Run, komorebic focus-workspace 2, , Hide !4::Run, komorebic focus-workspace 3, , Hide !5::Run, komorebic focus-workspace 4, , Hide ``` 3. start komorebi 4. switch to an empty workspace (`!2`) 5. attempt to switch back (`!1`), and see that you're stuck on the empty workspace. **Expected behavior** can't switch to a different workspace **Screenshots and Videos** https://user-images.githubusercontent.com/72744903/186525947-9dafa790-126b-4896-bb35-a0d035db40fa.mp4 Observe top left corner showing workspace number Bottom left showing keystrokes terminal shows git info and commands used to compile and run komorebi **Operating System** ``` OS Name: Microsoft Windows 11 Home OS Version: 10.0.22000 N/A Build 22000 ``` **Additional context** somme other autothotkey scripts, but shouldn't interfere.
adam added the bug label 2026-01-05 14:48:29 +01:00
adam closed this issue 2026-01-05 14:48:30 +01:00
adam commented 2026-01-05 14:48:30 +01:00
Author
Owner
Copy Link

@LGUG2Z commented on GitHub (Aug 27, 2022):

I have finally been able to reproduce this! 🎉

@LGUG2Z commented on GitHub (Aug 27, 2022): I have finally been able to reproduce this! 🎉
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#135
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?