feat(session): integrate kitty as a session backend #199
+355
−14
Conversation
This file contains hidden or 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
thazhemadam
changed the title
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
This PR aims to introduce support for the kitty terminal's default multiplexing functionalities as a session backend for
sidekick.nvim.Features
split: In a split kitty windowwindow: In a new kitty tabterminal: In a new kitty OS window2Note
This doesn't offer persistence management capabilities.
Footnotes
For the nomenclature used by kitty, see https://sw.kovidgoyal.net/kitty/overview/#tabs-and-windows. ↩
terminalopens a new OS window, since it makes more sense semantically for kitty. The kitty backend obviously does not support being opened in the integrated neovim terminal. ↩