Originally created by @crosstyan on GitHub (Aug 24, 2021).
Originally assigned to: @LGUG2Z on GitHub.
Currently, komorebic will switch to the target workspace with move-to-workspace. That's fine until you need to move multiple window to a certain workspace and it's a little bit of confusing for new users (at least I'm confused when I start using komorebi)
I think a subcommand like move-to-workspace-without-switching-workspace (bad naming) is helpful here.
Originally created by @crosstyan on GitHub (Aug 24, 2021).
Originally assigned to: @LGUG2Z on GitHub.
Currently, komorebic will switch to the target workspace with `move-to-workspace`. That's fine until you need to move multiple window to a certain workspace and it's a little bit of confusing for new users (at least I'm confused when I start using komorebi)
I think a subcommand like `move-to-workspace-without-switching-workspace` (bad naming) is helpful here.
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 @crosstyan on GitHub (Aug 24, 2021).
Originally assigned to: @LGUG2Z on GitHub.
Currently, komorebic will switch to the target workspace with
move-to-workspace. That's fine until you need to move multiple window to a certain workspace and it's a little bit of confusing for new users (at least I'm confused when I start using komorebi)I think a subcommand like
move-to-workspace-without-switching-workspace(bad naming) is helpful here.@LGUG2Z commented on GitHub (Aug 24, 2021):
The
send-to-workspacecommand in the last commit should do what you're looking for now. 🚀