feat: use kitty_mod for keymaps
#30
Labels
Comments
mikesmithgh
added a commit
that referenced
this issue
Nov 1, 2023
BREAKING CHANGE: The default mapping keys changed from `ctrl+shift` to `kitty_mod`. - If you are using the default value for `kitty_mod` of `ctrl+shift`, then no change is needed. - If you are using a different value for `kitty_mod`, then you should correct any potential mapping conflicts that may occur now that `kitty-scrollback.nvim` is using `kitty_mod`. closes #30
mikesmithgh
pushed a commit
that referenced
this issue
Nov 1, 2023
# [2.0.0](v1.1.10...v2.0.0) (2023-11-01) * feat!: use kitty_mod for keymaps ([8e652bf](8e652bf)), closes [#30](#30) * feat!: replace config-file with config name ([e16e96a](e16e96a)), closes [#16](#16) [#12](#12) [#2](#2) ### BREAKING CHANGES * The default mapping keys changed from `ctrl+shift` to `kitty_mod`. - If you are using the default value for `kitty_mod` of `ctrl+shift`, then no change is needed. - If you are using a different value for `kitty_mod`, then you should correct any potential mapping conflicts that may occur now that `kitty-scrollback.nvim` is using `kitty_mod`. * The `--config-file` option has been removed. Custom configurations are now supplied in the setup() function instead of separate config file. The config name correspondes to the key of the table provided to `setup()`.
|
🎉 This issue has been resolved in version 2.0.0 🎉 The release is available on GitHub release Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Use kitty_mod instead of hard coding
ctrl+shiftThe text was updated successfully, but these errors were encountered: