summaryrefslogtreecommitdiff
path: root/content/blog/vim-kitty-compat.md
diff options
context:
space:
mode:
authorrtk0c <[email protected]>2025-09-01 13:31:50 -0700
committerrtk0c <[email protected]>2025-09-01 13:31:50 -0700
commit3b3ded70587af4e780ed18697cd2be8ff48efe67 (patch)
tree7c24e6719b2f34a7395432470c74c3e5d8ebd79b /content/blog/vim-kitty-compat.md
parent6e3af2d649b2931b9928a6d3ef21a90bbd86c35d (diff)
Big spell correction, using LTeX vscode extension
which is languagetools under the hood which I struggled immensely trying to setup in emacs back then... now I give up
Diffstat (limited to 'content/blog/vim-kitty-compat.md')
-rw-r--r--content/blog/vim-kitty-compat.md8
1 files changed, 4 insertions, 4 deletions
diff --git a/content/blog/vim-kitty-compat.md b/content/blog/vim-kitty-compat.md
index 67debeb..af6f1b9 100644
--- a/content/blog/vim-kitty-compat.md
+++ b/content/blog/vim-kitty-compat.md
@@ -5,7 +5,7 @@ ShowToc: false
---
**TL;DR**: kitty uses a custom terminfo `xterm-kitty`. Vim doesn't like it.
-If you're in a pinch, commit a [crime](#i-just-want-it-work-right-now) and hopefully it works fine.
+If you're in a pinch, commit a [crime](#i-just-want-it-work-right-now), and hopefully it works fine.
If you're not, switch to another terminal for vim, or switch to neovim, or [attempt to teach vim to speak kitty](#configure-vim).
---
@@ -13,11 +13,11 @@ If you're not, switch to another terminal for vim, or switch to neovim, or [atte
If you use Vim in kitty, local machine or going through SSH, and (at least) one of these is happening:
1. Paste <kbd>Ctrl+Shift+V</kbd> from system clipboard is egregiously slow. Like two lines per second slow[^arch].
-2. Paste is glitchy. All the whitespaces get eaten, nowhere to be seen. Lines get jumbled together, parts of the clipboard overwrite another, etc[^debian].
+2. Paste is glitchy. All the whitespace get eaten, nowhere to be seen. Lines get jumbled together, parts of the clipboard overwrite another, etc[^debian].
3. kitty tells you your clipboard contains terminal escape sequences. Except it absolutely does not. Pasting elsewhere, still in kitty, like into `bash` or `nvim` works completely fine[^debian].
[^arch]: happened on a local ArchLinux machine
-[^debian]: happened on SSH to an Debian Bookworm arm64 supplied by AWS EC2
+[^debian]: happened on SSH to a Debian Bookworm arm64 supplied by AWS EC2
then congratulations, you have just discovered that Vim isn't very compatible with kitty as a terminal emulator. Instead of trying to poorly summarize _why_, you can instead read the problem being extensively discussed _con fuoco_ in the [Vim issue tracker](https://github.com/vim/vim/issues/11729).
@@ -32,7 +32,7 @@ Try `TERM=xterm-256color vim /my/file.txt`.
It seems like by setting `TERM` to `xterm-256color`, Vim will understand at least the paste part mostly fine. I don't know if bracketed paste is happening.
**This is highly discouraged** per kitty's [documentation](https://sw.kovidgoyal.net/kitty/faq/#i-get-errors-about-the-terminal-being-unknown-or-opening-the-terminal-failing-or-functional-keys-like-arrow-keys-don-t-work) and [opinion](https://github.com/kovidgoyal/kitty/issues/2192).
-Don't use it long term, or you'll find other inexplicable weirdness (which I had, but it's all a blurry mess so I can't recite to you the war story. alas).
+Don't use it long term, or you'll find other inexplicable weirdness (which I had, but it's all a blurry mess, so I can't recite to you the war story, alas).
# Other solutions
As far as I know, all other terminals pretend to be xterm well enough that Vim plays happily long. So you use them instead.