While the current version of rvisidata supports tmux, this is not the case for GNU screen (the other, older terminal multiplexer).
From my understanding, GNU screen-support should also be possible using the following commands in a script with the following options in the function options(rvisidata.tmux = "path/to/your/script"):
screen -X split to create a (horizontal) split.
screen -X screen -t rvisidata bash to create a new split running bash.
screen -X focus && screen -X prev to open the current window on the bottom split.
screen -X at rvisidata stuff "vd\n" starts vd in the rvisidata-window (technically: stuff the string "vd" to rvisidata and then run Enter).
screen -X focus gets the focus back to the vd-pane
Also it should be possible to find out if you're running in a screen-session by looking at the $STY-variable (unset if not, returns the session-name if it is).
Any chance to add screen-support in the future? I'd also support you in any way if you're interested.
While the current version of
rvisidata
supportstmux
, this is not the case forGNU screen
(the other, older terminal multiplexer).From my understanding,
GNU screen
-support should also be possible using the following commands in a script with the following options in the functionoptions(rvisidata.tmux = "path/to/your/script")
:screen -X split
to create a (horizontal) split.screen -X screen -t rvisidata bash
to create a new split running bash.screen -X focus && screen -X prev
to open the current window on the bottom split.screen -X at rvisidata stuff "vd\n"
startsvd
in thervisidata
-window (technically: stuff the string "vd" torvisidata
and then run Enter).screen -X focus
gets the focus back to thevd
-paneAlso it should be possible to find out if you're running in a
screen
-session by looking at the$STY
-variable (unset if not, returns the session-name if it is).Any chance to add
screen
-support in the future? I'd also support you in any way if you're interested.