I wonder about the point of torturing a minimalist text editor with no graphics support (such as Vim into a comprehensive development and visualization enviromment, by invoking several plugins and some very specific workflows. Would it not make more sense to take the interface (modal editing, etc) and wrap it into module that can be easily embedded into several different IDEs, to handle text-specific tasks? That way,…
Alternately, would it make sense in R to separate the code and the result instead of a WYSIWYG approach? This is how many work with tools like latex/pdf (among others), edit the source in vim and have a viewer window open next to it.
Turning Vim into an R IDE
21–27 of 27 posts
Re: Turning Vim into an R IDE
#22I wonder about the point of torturing a minimalist text editor with no graphics support (such as Vim into a comprehensive development and visualization enviromment, by invoking several plugins and some very specific workflows. Would it not make more sense to take the interface (modal editing, etc) and wrap it into module that can be easily embedded into several different IDEs, to handle text-specific tasks? That way,…
Re: Turning Vim into an R IDE
#23R studio already has vim key bindings, so trying to make vim into rstudio-like seems like spending time on the wrong problem. As in, even if you succeed beyond your wildest dreams you're still not going to compete with R studio.
Things that make Rstudio great that is not so easy to implement include the knitR integration and Rmarkdown integration and embedded graphs and most importantly Rstudio server.
Re: Turning Vim into an R IDE
#24As much as I love Vim and R, I think the experience is pointless without embedded graphs. It would be perfect if it was possible to view a graph in a Vim split.
Re: Turning Vim into an R IDE
#25I wonder about the point of torturing a minimalist text editor with no graphics support (such as Vim into a comprehensive development and visualization enviromment, by invoking several plugins and some very specific workflows. Would it not make more sense to take the interface (modal editing, etc) and wrap it into module that can be easily embedded into several different IDEs, to handle text-specific tasks? That way,…
Absolutely would. The issue is that this is (evidently) a surprisingly hard problem. I say evidently because I dont know /why/ it is so hard, only that extremely few people have succeeded.
Re: Turning Vim into an R IDE
#26I wonder about the point of torturing a minimalist text editor with no graphics support (such as Vim into a comprehensive development and visualization enviromment, by invoking several plugins and some very specific workflows. Would it not make more sense to take the interface (modal editing, etc) and wrap it into module that can be easily embedded into several different IDEs, to handle text-specific tasks? That way,…
Can not Spacemacs + ESS fill the gap?
Re: Turning Vim into an R IDE
#27> Why Not RStudio? > Yes, I know RStudio has Vim keybindings, but it isn’t the real thing. At this point, I’m ruined by Vim. I say the next step is that we have NeoVim running inside of RStudio. I also think we will have that happening in VSCode a mind bending text editor inside of a text editor.
https://github.com/Chillee/VSCodeNeovim
https://github.com/VSCodeVim/Vim#neovim-integration
"We now have neovim integration for Ex-commands. To enable,..."