-
-
Notifications
You must be signed in to change notification settings - Fork 1k
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
Kitty 0.14.6 Rendering Glitch with NeoVim and Tmux #2047
Comments
Trying to debug the combination of tmux and nvim is way too much work. Does |
Also, I see the same effect in ssh session but not always. |
|
Use xterm-kittyinside tmus as well and you should be fine. |
Thank you! |
This feels like a weird recommendation, but I'll test it for a few days to see what happens. |
FWIW none of my friends are using Thanks again |
As expected changing the terminal to |
Also it's easily fixable by closing kitty and opening it again, even using the exact same tmux session. |
@juanibiapina I dont know what your issue is, my recommendation was for the original poster. "Characters all going crazy" is about as useless a problem description as I have ever heard. If you wish some help, at least make the minimum effort of posting a screenshot along with details of your operating system, the output of kitty --debug-config and ideally some way to reproduce your isse with minimal configs of all software involved. |
My problem is similar to the one reported by the OP. Also I think he made quite an effort to share a screenshot and his config, along with one way that he was able to solve it. I also contributed two more pieces of information given my knowledge. If you had requested more information before closing the issue I'm sure both me and OP would have provided. Instead you have now replied aggressively. There have been cases before where you did that. This kind of behavior is not acceptable. |
Hey fellas, no problem 😅 We'll figure this out together! I know that my issue is a little tricky because it works for all of friends, except for me right now. I will continue investigating until I can offer more valuable feedback :) |
Then please leave. People that make minimum effort posts and expect me to jump through hoops to help them are not acceptable. |
@peterpme If I were you I would bisect the configs of the involved software: kitty, shell, nvim, tmux until finding the culprit. |
Hi, I'm encountering this as well. Here's my setup, which I've tested using clean configs for tmux 3.1, vim 8.0, and kitty 0.14.6, and which works on UXTerm:
To replicate:
This does not occur if any of the following is true:
Vim-specific workarounds:
Detaching from and reattaching to the To clarify, this bug:
|
Whoops, sorry, I should have done a ping here. @kovidgoyal I can confirm that this bug is still present. Steps to reproduce are in my previous comment. Also, I should have mentioned my UXTerm version. Running |
@SliceThePi Sadly those steps dont reproduce the issue for me. To be precise
|
To be clear, the vim command I ran was |
Using :h instead of :vert h does not reproduce it either. |
For all the confused souls that end up here - it's not
🍀 |
I just installed Kitty to try it out and I came across this problem right away. I do not use |
it's not tmux or neovim or kitty's problem it's the system |
FWIW, I disabled the |
I have the same issue with lualine.nvim plugin. Disabling fixed this. |
Thank you so much! I had issues after moving from Gnome to KDE and Tmux wasn't showing any ligatures, this solved it! |
Hi, I love Kitty!
This repainting issue will happen from time to time:
![image](https://user-images.githubusercontent.com/1211905/66681574-9a25c100-ec38-11e9-8cfa-01c02f709c4b.png)
This is what it's supposed to look like:
![image](https://user-images.githubusercontent.com/1211905/66681621-b164ae80-ec38-11e9-80ad-c1171e3d80d4.png)
The way I fix it is by scrolling the part out of view and scrolling back up.
Here is my kitty config. The only thing that I uncommented out is the font size and font_family (Liga Iosevka, a patched font that includes Fira Code's ligatures)
Thank you!
The text was updated successfully, but these errors were encountered: