-
Notifications
You must be signed in to change notification settings - Fork 98
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
First line garbage display #61
Comments
Are you able to provide any reproduction for this? Does it work against a minimal vimrc (like the one below)?
|
I've spend some time going through all the startup code (I needed some of the debian vimrc as well). I've got a nice reproducer now. It seems to be a bad interaction between vim-syntastic/syntastic and pearofducks/ansible-vim. I've not reported this to syntastic (yet) although there is a chance it is entirely their fault. See the attached reproduce.zip. Thanks for looking. |
I don't use synstastic and I've seen that output in the past as well. I reckon it's a bug in vim that might have already been fixed with later versions. I'm on 8.1.22. |
I have also found "garbage" output upon installation of this plugin. "^[[>1;2802;0c" appears as the last lines output and moves with scrolling text.
and upon scroll
I'm using vundle to manage plugins.
If I open a file that that has fewer lines than the current occuppied windows max lines, garbage does not appear.
Anyway, hope this helps in the debug. Let me know if you want me to try anything else |
I've done a bit more testing by adding/removing other plugins and it seems to be (at least in my case) a conflict between a couple of plugins:
With this combo it seems to show the garbage output. This plugin just happens to be the bottom of the list. |
When opening a yml file with this plugin enabled, I see only:
---2;2R^[[>1;5200;0c^[]10;rgb:2e2e/3434/3636^G^[]11;rgb:ffff/ffff/ffff^G
This stays for a second or two and then the rest of the file appears. A clear and redraw of the screen (^L) makes the line disappear.
This happens on any yml file I've encountered (for example, those generated by: ansible-galaxy init foo).
The text was updated successfully, but these errors were encountered: