![]() In terms of those three “lingering disadvantages,” I’ve overcome (2) and (3) but not really (1). Note: You can find instructions for how to install Neovim here. ![]() It is not yet clear to me if the combinations of Neovim’s saner defaults and my vimrc are enough to make interactions with the system clipboard as fluid in iTerm Beta/Nightly + Neovim as they are in MacVim. ![]() Though this is something I should not use at all anyway. I recently mapped to use vim-sneak in my vimrc, which is pretty aggressive/awesome, but it is super natural to make set to Sneak S. ITerm cannot detect key inputs shift + space or shift + enter, as far as I can tell. ![]() Lingering Disadvantages to iTerm Beta/Nightly + Neovim as compared to MacVim I’m betting there’s some conditional I can add to that if statement to accomplish this, but I don’t know it at this point. Ideally my vimrc would be smart enough to use Terminal’s given colors when running Neovim. The if statement in my vimrc is not smart enough to NOT run that set termguicolors line when I’m running ol’ fashioned default OS X Terminal, so now when I run Neovim there all the colors are totally fucked. I haven’t played around with this too much yet, but it seems to work with the setup described in this post! Lingering Issue(s) Let g:terminal_color_background="#202020" " These are supposedly colors for Neovim's terminal emulator Then in your ~/.vimrc (or your nvim config file, without the if statement I suppose):
0 Comments
Leave a Reply. |