No integration with GNU Screen, VimShell, Conque Shell and screen plugin about vim-r-plugin HOT 7 CLOSED

I may have this set up incorrectly, but the plugin does not seem to be exhibiting proper behavior (splitting the window) when you are already in a tmux session before starting vim. It splits only if you use the tvim function, but embeds a second tmux session into the first rather than splitting a new window in the first as was the previous behavior with a running tmux. This may be expected behavior, but I would prefer to have the R session in a non-embedded split window.

Good work with the plugin by the way, it is very useful, and is the thing allowing me to continue using vim for R rather than using RStudio.

from vim-r-plugin.

Here, it splits the window as before. The only difference is that after

tmux
vim

I have to quit Vim and type “exit” to finish the Tmux session while after

tvim

the Tmux session finishes when I quit Vim. Note that you should NOT do:

tmux
tvim

from vim-r-plugin.

You are correct, I cannot even get it to reproduce the error I was experiencing yesterday. It must have been in a strange intermediate state since I just upgraded to the new version. Thanks again!

from vim-r-plugin.

Thanks for the feedback. I improved a bit the explanation about tvim. Instead of “start Vim inside a Tmux session” the documentation now says “start a Tmux session running Vim”.

from vim-r-plugin.

I know this is closed, but I don't want to open an issue when it is potentially not a bug.

Does this issue affect the ability of having GVIM open a terminal inside the editor window?

So far every time I start GVIM and press rf the plugin seems to start fine, but the R terminal is always opened externally. The object browser on the other hand opens within the editor window. When using tvim this does not happen.

I've seen screeshots that suggest it is possible to have the R terminal inside gvim's window.

Thanks in advance.

from vim-r-plugin.

It is possible to have R running in a Vim buffer (and, thus, inside GVim), but none of the available options (VimShell, ConqueShell) works smoothly because Vim has some limitations. That is why I removed the support to VimShell and ConqueShell. But if someone wants to use VimShell, ConqueShell or similar plugins, he or she can write the code and source it with the option vimrplugin_source. The old Vim-R-plugin source code can be a starting point.

Neovim is a promising Vim replacement. If people developing neovim do everything that is planed, it will be possible to run R inside Vim as emacs+ess does (or even better). However, I think that the best option is to have Vim and R running independently. To have R running inside Vim you have to write a terminal emulator inside Vim. And I have no doubt that the terminal emulator will have many bugs and limitations. For example, even the already mature terminal emulator of emacs+ess can not run the colorout package and does not emit the SIGWINCH signal that the setwidth package relies on to set R's "width" option.

The Object Browser is just Vim. That is why we can simply split Vim window and run the Object Browser in the newly opened Vim window. However, due to Vim limitations, it is more stable to have the Object Browser running in a separate Vim process (Vim may have problems if it receives messages from R while you are doing some complex editing tasks).

from vim-r-plugin.

Thank you for the detailed answer. I understand your reasoning. While not a solution, at least I know now that the problem is not on my end due to a faulty install of the plugin.

I'll keep an eye on NeoVim's development, and of course will continue using Vim-R-plugin. Thank you for writing and sharing it.

from vim-r-plugin.