Support WezTerm mux splits

[JonGretar]

I'm not quite familiar with how R.nvim handles external_term but I would love to be able to open R in a WezTerm pane much like in a tmux pane. This should work for darwin much like tmux.

I guess in a Linux machine I could just set the full command but I am not sure why it is not allowed for darwin. I'm sure there are good reasons but I don't know why this would not be possible with WezTerm much like with tmux.

The command to run would be something like wezterm cli split-pane --bottom --percent 30 -- R

[jalvesaq]

It's possible with Kitty. Please, see the last comments on https://github.com/R-nvim/R.nvim/issues/115. You can try to adapt the solution for WezTerm.

[JonGretar]

It's possible with Kitty. Please, see the last comments on #115. You can try to adapt the solution for WezTerm.

As I understand it. Then on MacOS R.term only allows true or some tmux command in external_term. Am I incorrect about this? Actually the docs don't mention allowing tmux but it seems it does.

[JonGretar]

Got this working by lying to R.nvim about being on a mac.

    local options = {
      is_darwin = false,
      external_term = 'wezterm cli split-pane --bottom --percent 30  -- ',
      R_app = 'radian',
    }

[jalvesaq]

Thanks for sharing your solution!

The last time that I tried Nvim-R on a Mac was in 2015, and, as far as I remember, OS X always started R in whatever was the default terminal. Did macOS inherit this feature (or limitation)? You, people who have access to a macOS, can decide whether the is_darwin config option is still necessary or not.

[jalvesaq]

Another option that I don't know if still works on macOS is applescript = true.

[JonGretar]

Thanks for sharing your solution! The last time that I tried Nvim-R on a Mac was in 2015, and, as far as I remember, OS X always started R in whatever was the default terminal. Did macOS inherit this feature (or limitation)?

This seems to be a design choice that R.nvim itself makes. By using the open command to launch when external_term is set to true. The open command simulates what would happen if double click on the file in the GUI file finder unless it is set to tmux. But as I am using a command to interface to the terminal that NVim is running in this does not seem to work so well.

I guess this comes down to the capability of modern terminals on macOS these days. Back in 2015 the choice was the default terminal or iTerm. But in modern times with newer terminals, some of which with their own mux, and alternatives to tmux such as zellij this system might need to be reconsidered.

[jalvesaq]

Could you make a pull request for this?