![]() ![]() Vi/Vim is, of course, an extremely powerful text editor, which is infamously difficult to learn. We have higher standards, and things to get done, and that's why we'll be using MacVim. I'm sure your $DEITY will still love you. If you for some reason, need to have less features because due to some unseen yet crippling inability to teach your muscles to do something, which is a vim requirement, then by golly use something with an "easier learning curve". If you are are fearful, why, pay fear's price and fire up some 100 meg IDE and have it hold your hand and change your diapers. Of course, people program are not stupid, people who program on unix platforms are unafraid of complexity, or at least _were_ not stupid, and _were_ unafraid of complexity. Vim has a steep learning curve, like all things Unix. MacVim is gvim for os X, what an os X program should be like, combined with every optimization that code editing needs and thousands more that are "nice". Troll lurking under the bridge named /Applications. Vim on os X used to be like firefox, a thing from another place, a foul, alien and misshapen MacVim is an excellent version of gvim, easily the lushest and sexiest one i've ever seen. This is _the_ editor, unless you run emacs, and of course all those people, having internalized the concept of "false gods" have cheerily begun running textmate instead.Įnough about that. I read that slow scrolling due to rendering long lines was less pronounced in GVim and MacVim than in terminal Vim, but that was not the case for me.Well, exactly what I want are thousands of text specific features. Besides using iTerm instead of Terminal.app for the key repeat issue, no other changes in how I was running Vim helped. Note that I did not mention using tmux over screen, or Neovim instead of Vim. All the tricks I currently know for dealing with slow scrolling in Vim. I don’t use this setting anymore because nocursorline was more useful. It turns off syntax highlighting after a max column value, so lines longer than that abrubtly lose syntax coloring. Basically, it seems to limit the number of times Vim renders, which sped up scrolling for me. You can read about it with help lazyredraw. That’s kind of a bummer, but if it means I can scroll through HTML and Ruby files, then I’ll take it. It turns off the bar that highlights the current line you’re on. This setting had the most impact of the three. There are three settings that helped this on my systems. If you’re a programmer, that means a lot of files! And the problem affects more than just macOS. The magic KeyRemap4MacBook values for me were:Įven with fast repeat settings, Vim can slow to a craw while scrolling through files that have long lines, when syntax highlighting is turned on. Tweak the repeat values even more with KeyRemap4MacBook.Terminal.app couldn’t cope with faster key repeat settings – Vim was still slow, though a bit faster. Now, the vanilla options helped some, but in order to get really fast scrolling speed, I had to take two more steps: Tweak the Key Repeat and Delay Until Repeat settings to find a good speed. I had to restart after changing these settings to see any effect. You can change Key Repeat settings in System Preferences -> Keyboard. It turns out there was a simple cause for the problem: key repeat settings. Scrolling with j and k was blindingly fast on Linux, but plodded along on my Mac so slowly that I began using Control-F and Control-B most of the time. There was always a marked difference between Vim on my Mac and Vim on Linux. Other times, the problem is really about Vim’s ability to render long lines with syntax highlighting.įear not! There are solutions to both problems. In some cases, the problem is OS-specific: key repeat settings can slow down scrolling with the j and k keys. Vim, Neovim, and MacVim can all exhibit slow scrolling in macOS. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |