Why does Vim mess up the terminal log after closing?

Question

vim

Has anyone encountered the fact that after vim closes, it often leaves behind pieces of content open in it or empty spaces for several screens in the terminal log?

Makes life very difficult
Plays unstably, fails to catch minimum conditions.
----
Versions:
OS X latest
Vim and MacVim both mess up but don't beep
VIM - Vi IMproved 7.3 (2010 Aug 15, compiled Jun 14 2016 16:06:49)
Compiled by [email protected]
VIM - Vi IMproved 7.4 ( 2013 Aug 10, compiled Feb 10 2016 22:59:14)
MacOS X (unix) version
Included patches: 1-1147
Compiled by Homebrew
Iterm2 latest (Build 2.9.20160426)
ZSH latest + OH-MY-ZSH latest
zsh --version
zsh 5.2 (x86_64-apple-darwin15.0.0)
my env: https://gist.github.com/ax-/f598d090879b17cb95365...
detailed mvim and vim vestion: https://gist.github.com/ax-/ 5dd13d22c72f2859f30c9...
vim plugins: https://gist.github.com/ax-/c0bd2064390d9bcaaae47...

Answer 1

Uh-huh, I'm facing.
Similar set of software.
Press Ctrl+L to clear the console screen.
The scenario of using vim and console commands is not entirely clear, for example, I almost never leave vim, I run console commands from it or in an additionally open terminal.
I'll try to tweak Vanga-mode and assume that this will help - unix.stackexchange.com/questions/60499/how-to-set-...

Answer 2

Iterm sucks with custom shells OH-MY-(zsh\fish), and the shells themselves are slightly more than completely curved, which costs half a year of fixing the use of the numeric keypad in zsh. Since the floor returned to its native shell, all such problems have disappeared.