-
-
Notifications
You must be signed in to change notification settings - Fork 644
New issue
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
tmux like key bindings option #225
Comments
Hey! I have similar issues as you. I updated the example config file for now. Edit: Maybe it makes sense to add a prefix mode, that has no default mappings? Even if you let people customize some of the mappings, what happens if I want to have all my input modes flattened into one big category? You can do that with the config file:
|
We want to provide sane defaults for people, |
I'd like to be assigned this, I think I can get close, and get a list of functions that are Tmux specific that are not implemented in Zellij, but may wish to be in the future. |
Awesome! This would be very helpful. |
@SaintFenix |
hi I can't find a config file example with tmux keybindings. has this been removed? |
Tmux keybindings work out of the box, just try 'em. |
thanks. I worded it poorly. I wanted as a complete emulation of tmux as possible since keybindings were also clashing with keybindings in other terminal apps. I've added lots of keybindings and cleared the one that comes by default. Would be cool to have an example config where it's already all done |
Related to #25 and #220.
I think the getting started mode and status toolbar are great. but I can't work without tmux and I am very attached to my key bindings. I don't think I could ever make the switch without being able to configure zellij with my key bindings.
Why not just continue to use tmux then? Maybe one day there's some cool plugins to make a user curious about zellij, but someone who's a tmux power user would never bail if they can't take their key bindings with them.
alt+<h/j/k/l>
. That's definitely one I can't live without.The text was updated successfully, but these errors were encountered: