Current behavior
I have a fresh install with the default config but with some overridden keybindings, such as "cmd+n" to create a new workspace. This or any other overridden keybinding seems to work until after a create the first workspace with the mouse.
Expected behavior
Keybindings should work on a fresh launch.
Reproduction
Pretty much a fresh install with only some keybindings overridden.
Impact
Until I worked out that I could create a new workspace with the mouse, I was blocking from doing anything. Of course, I could always go back to default keybindings but having to do that every time I restart would get annoying very quickly.
Environment
v0.6.5 on macOs, installed via homebrew and running on fish shell.
Relevant config are all custom keybindings, but more importantly "cmd+n" which I set to create a new workspace.
Contribution intent
Current behavior
I have a fresh install with the default config but with some overridden keybindings, such as "cmd+n" to create a new workspace. This or any other overridden keybinding seems to work until after a create the first workspace with the mouse.
Expected behavior
Keybindings should work on a fresh launch.
Reproduction
Pretty much a fresh install with only some keybindings overridden.
Impact
Until I worked out that I could create a new workspace with the mouse, I was blocking from doing anything. Of course, I could always go back to default keybindings but having to do that every time I restart would get annoying very quickly.
Environment
v0.6.5 on macOs, installed via homebrew and running on fish shell.
Relevant config are all custom keybindings, but more importantly "cmd+n" which I set to create a new workspace.
Contribution intent