Reputation: 25403
While I'm working in vim, I often suspend the vim process with ctrlz so I can access my bash shell. I'm on Ubuntu 14.10.
I have plugins such as syntastic loaded which take action after actions like file writes.
Something that happens all-to-frequently is that I will save a file and immediately want to do something on the shell, such as a git operation.
If I do this too fast though (save and then immediately suspend the vim process) my shell get's in a weird state where the blinking cursor is gone and half the screen needs to be repainted.
Then, when I fg
back into the vim process it too is messed up visually and I need to redraw the screen (with ctrll).
I understand I can "fix" the problem by forcing the redraw but any suggestions on how to avoid getting in this state?
Perhaps something like a mapping to wrap ctrlz and kill all plugin execution before the suspend occurs?
Upvotes: 1
Views: 326
Reputation: 1976
The first step in debugging vim is to follow the instructions in How do I debug my vimrc file?.
In this particular question, the problem could also reside in the terminfo configuration. A typical example of such a problem is when $TERM
is defined in .bashrc to a value that is not compatible with the used terminal.
Upvotes: 1