Replies: 6 comments 4 replies
-
I've resolved this issue by simply disabling Zellij using Ctrl+G. I've become quite accustomed to doing it, although initially, it didn't feel comfortable. I'm very eager to hear if there's a more effective approach. |
Beta Was this translation helpful? Give feedback.
-
+1 looking forward to a better solution |
Beta Was this translation helpful? Give feedback.
-
At last I arrived at a solution that doesn't hinder my workflow—make zellij work well even when it's locked. That way I can just stay in the locked mode 99% of the time. I added the following keybinds (to
|
Beta Was this translation helpful? Give feedback.
-
|
Beta Was this translation helpful? Give feedback.
-
hey guys, this is the set of remaps i currently implement in my project, yazelix: https://github.com/luccahuguet/zellij#keybinding-remaps you can either copy the relevant config (from yazelix.kdl) to your own zellij layout, or manually add the remaps to your zellij/config.toml or even use my project directly |
Beta Was this translation helpful? Give feedback.
-
Zellij added configuration which allows updating the keymaping which lead to key conflicts. Now you can assign different key modifiers to commands which are used the most. Also Ctrl+g is an option. See: https://zellij.dev/documentation/rebinding-keys |
Beta Was this translation helpful? Give feedback.
-
I would like to use Helix in a Zellij session, but there are many collisions in the keyboard mapping. Zellij uses the same key combinations as Ctrl+s or some other Ctrl and Alt combinations.
This makes it difficult to use Helix within Zellij without having to do a lot of remapping. Are there any options other than remapping or not using Helix within a Zellij session?
Beta Was this translation helpful? Give feedback.
All reactions