I’m using vim+Powershell core on Windows Terminal. I guess the OS is the problem then? gvim is very slightly faster but still very slow and laggy unfortunately.
edit: Also, my vimrc is already pretty lightweight since I only started using it a week ago lol. When I use vim for editing latex files there doesn’t seem to be an issue, which is why I was thinking that it is probably the julia-vim package that is slowing Vim down.
Maybe WSL is a viable alternative? It might also be worth it to file an issue with vim-julia.
I’ll try WSL and if that doesn’t work, I’ll open an issue. thanks!
I haven’t noticed anyone mention vimcmdline which is what I use for interactive data stuff. It’s actually developed in part by someone who also works on NvimR which was mentioned earlier. It uses tmux, which using alone has always proved confusing for me, but vimcmdline was very easy to set up. I don’t know how it compares to vimteractive.
FWIW I experienced the same lag using julia-vim. It got worse with time (as I added more to the file I was working on), until it became bad enough to force me to turn off the plugin. The problem persisted across both OS X and GNU/Linux systems, using both iTerm2 and Alacritty on OS X.
The common exacerbating factor was editing a large file, on the order of 1000 lines with plenty of complicated syntax. Judging by the open issues at the julia-vim repository (e.g. here) it’s conceivable that whatever process does the syntax highlighting doesn’t scale perfectly, at the time of this writing.
A workaround in my particular case was to split my large file into several files and use include().