I use vim on Mac OS X, but this is realy slow in Terminal.app and iTerm.
Progress over many lines becomes tedious.
some idea of solution?
Super User is a question and answer site for computer enthusiasts and power users. It only takes a minute to sign up.
Sign up to join this communityI use vim on Mac OS X, but this is realy slow in Terminal.app and iTerm.
Progress over many lines becomes tedious.
some idea of solution?
For me, deleting .viminfo
helped.
Maybe you have installed some broken plugins or something like that. Try to temporary rename directory with vim configs:
mv ~/.vim ~/.vim.backup
And/or main config file: mv ~/.vimrc ~/.vimrc.backup
And try to use vim without configs
Try MacVim. There is also a 64 bit version available somewhere on the blog, which includes a new rendering layer.
I had this problem (just painfully slow) and it ended up being the Consolas font I was using in Terminal.App and ITerm Switching to Monaco in my case sped things up considerably
I regularly have problems, a few commands are just slow at redrawing. This is a shot in the dark but if you are using cursorline
, try disabling it, it dramatically improved performance for me
For me, using a Retina iMac, neovim, tmux, and a bunch of neovim plugins, I found that the only thing that made a difference in scrolling & rendering speed was keyboard repeat rate! Nothing else — Terminal.app vs iTerm.app, neovim vs vim, no vim configuration vs my usual, tmux vs no tmux, cursorline vs no cursorline, etc — made any real difference in the slow rendering & scrolling I experienced.
Once I set key repeat faster than available through System Preferences, rendering & scrolling in vim became 2x as fast, regardless of whether I was loading all my plugins or not. I wrote a bit more about the factors I investigated in this comment on tmux issue #353.
I would investigate whether keyboard repeat rate improves the situation for you.
Check if you have any other mapping which starts with 'hjkl' in your vimrc. When you have some other mapping starting with these, vim waits to check the next input which results in reduced responsiveness.