-
Notifications
You must be signed in to change notification settings - Fork 73
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
vim blinking when editing with unsaved tabs #9
Comments
ok... perhaps it's connected with redrawing... I have an idea how it could be fixed. I'll try to push it in a minute. |
Ok, please check how does it work for you now. |
Hi, @szw! I just updated and isn't fixed yet. |
Well, so it's not that case. But redrawing just the current status line is better anyway. Ok, I'd like to ask you to check with vanilla Vim (no other plugins). And could you provide a link here to your .vimrc (gist, pastie or whatever)? Moreover, I've found this: junegunn/seoul256.vim#3. Perhaps this is connected with your issue too? |
Hi @tarciozemel! Thanks for your .vimrc. Could you provide more info about your setup, os, Vim version, terminal, etc. I'd like to try to reproduce that issue somehow. |
I'm running Ubuntu 13.04 with terminal (Guake) Vim 7.4.113 built from source. Hope this help, I believe other people have that same issue. Regards! |
Can you also check if that issue happens on the "vanilla" Vim (no other plugins)? |
I started Vim with About the others, how do I check what's my TERM value and if I'm using multiplexers? |
That's good! 👍 ;) To print out the TERM variable use echo $TERM in the terminal. As to multiplexers, if you asking, I guess you are not using them ;). If you are curious more about TMux this post looks like a nice intro. |
I'm using terminal vim and, when I search and open some files in different tabs, if some of this tabs are unsaved, when I'm typing in any other tab, the screen blinks in every keystroke... If I change to that unsaved tab and save it, boom, the blink immediately stops!
I'm not sure, but I think this is happening after I updated the plugin (today).
The text was updated successfully, but these errors were encountered: