-
Notifications
You must be signed in to change notification settings - Fork 13
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
feat!: exit kitty-scrollback.nvim with q key instead of esc #272
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
BREAKING CHANGE: Change the default keymap for quitting kitty-scrollback.nvim from `<Esc>` to `q`. If you prefer the previous behavior of using `<Esc>` to exit kitty-scrollback.nvim, this can be reconfigured by adding the following to your kitty-scrollback.nvim setup. ```lua vim.keymap.set({ 'n' }, '<Esc>', '<Plug>(KsbCloseOrQuitAll)', {}) ``` For example, if you are using lazy.nvim, it would look something like this ```lua return { { 'mikesmithgh/kitty-scrollback.nvim', lazy = true, cmd = { 'KittyScrollbackGenerateKittens', 'KittyScrollbackCheckHealth' }, event = { 'User KittyScrollbackLaunch' }, config = function() vim.keymap.set({ 'n' }, '<Esc>', '<Plug>(KsbCloseOrQuitAll)', {}) -- quit kitty-scrollback.nvim with Esc key -- vim.keymap.set({ 'n' }, 'q', '<Plug>(KsbCloseOrQuitAll)', {}) -- uncomment if you would like to also quit with the q key require('kitty-scrollback').setup() end, }, } ```
mikesmithgh
force-pushed
the
exit-with-q
branch
from
November 10, 2024 20:01
baaf528
to
99fe8ec
Compare
mikesmithgh
changed the title
feat!: exit with q
feat!: exit kitty-scrollback.nvim with q key instead of esc
Nov 10, 2024
mikesmithgh
force-pushed
the
exit-with-q
branch
from
November 15, 2024 15:15
cd6f86d
to
4184e47
Compare
mikesmithgh
pushed a commit
that referenced
this pull request
Nov 15, 2024
# [6.0.0](v5.0.2...v6.0.0) (2024-11-15) * feat!: exit kitty-scrollback.nvim with q key instead of esc ([#272](#272)) ([1ae369b](1ae369b)) ### BREAKING CHANGES * Change the default keymap for quitting kitty-scrollback.nvim from `<Esc>` to `q`. If you prefer the previous behavior of using `<Esc>` to exit kitty-scrollback.nvim, this can be reconfigured by adding the following to your kitty-scrollback.nvim setup. ```lua vim.keymap.set({ 'n' }, '<Esc>', '<Plug>(KsbCloseOrQuitAll)', {}) ``` For example, if you are using lazy.nvim, it would look something like this ```lua return { { 'mikesmithgh/kitty-scrollback.nvim', lazy = true, cmd = { 'KittyScrollbackGenerateKittens', 'KittyScrollbackCheckHealth' }, event = { 'User KittyScrollbackLaunch' }, config = function() vim.keymap.set({ 'n' }, '<Esc>', '<Plug>(KsbCloseOrQuitAll)', {}) -- quit kitty-scrollback.nvim with Esc key -- vim.keymap.set({ 'n' }, 'q', '<Plug>(KsbCloseOrQuitAll)', {}) -- uncomment if you would like to also quit with the q key require('kitty-scrollback').setup() end, }, } ```
🎉 This PR is included in version 6.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
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.