We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Describe the bug After commit be5945c, 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:
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
!2
!1
Expected behavior can't switch to a different workspace
Screenshots and Videos
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.
The text was updated successfully, but these errors were encountered:
I have finally been able to reproduce this! 🎉
Sorry, something went wrong.
5d094f6
No branches or pull requests
Describe the bug
After commit be5945c, 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:
!2
)!1
), and see that you're stuck on the empty workspace.Expected behavior
can't switch to a different workspace
Screenshots and Videos
JMyE9mF7.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
Additional context
somme other autothotkey scripts, but shouldn't interfere.
The text was updated successfully, but these errors were encountered: