You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Apologies for the heinous title I didn't know how else to title this.
I've noticed since swapping to Kitty that sometimes when I am done with a file in vim and I either :wq or :q or :q! out of it that I will get the following in my next prompt such that the next prompt is foo@location ~ $ <this string of stuff>.
It only happens sometimes, and whenever it happens I make a mental note "remember if you're pushing anything next time you exit vim" but then it takes a while before it crops up again and by that time I've forgotten my mental note.
I assume this is Kitty as it hasn't happened with any other terminal I've used, I wonder what it could be or if anyone has any insight unless this is a bug.
Please let me know what further information I can provide.
The text was updated successfully, but these errors were encountered:
First make sure TERM is xterm-kitty and not something else. That
gobbelydook is a DCS control sequence which kitty will send is eom
program running inside it requests terminfo data from it. IIRV vim does
so in various circumstances. For whatever reason it is not sticking
around long enough to read the response, so it bleeds into the shell
instead. Bisect your vimrc/plugins to find the culprit.
Apologies for the heinous title I didn't know how else to title this.
I've noticed since swapping to Kitty that sometimes when I am done with a file in vim and I either
:wq
or:q
or:q!
out of it that I will get the following in my next prompt such that the next prompt isfoo@location ~ $ <this string of stuff>
.It only happens sometimes, and whenever it happens I make a mental note "remember if you're pushing anything next time you exit vim" but then it takes a while before it crops up again and by that time I've forgotten my mental note.
I assume this is Kitty as it hasn't happened with any other terminal I've used, I wonder what it could be or if anyone has any insight unless this is a bug.
Please let me know what further information I can provide.
The text was updated successfully, but these errors were encountered: