Sublime Forum

Radian console issues

#1

Hi All,

I am trying to use the Radian console with Terminus to execute R code, but there are a couple of inconveniences.

First, Radian seems a bit laggy and slow on autocomplete, is there anything that can be done to speed it up?

Secondly, I cannot place the cursor using the mouse on the command line. I often browse back in history to execute previous commands, some can be a few lines long. So I am forced to use arrows or home/end to navigate to the specific section in the text. It behaves like VIM on a linux console, I fee like being back in the 80s :confounded:

Is there a setting anywhere to correct this behavior?

Thanks!

0 Likes

#2

Do you experience the same things when running radian from a full terminal emulator, or is it just within Terminus?

0 Likes

#3

Thanks for the response. If I open radian say in Command prompt (I work in Windows) it’s snappier but I still can’t place the cursor using the mouse.

0 Likes

#4

The performance problem is likely due to Sublime Text or Terminus, though I don’t know how fixable that is. The cursor issue sounds like it’s inherent to Radian.

0 Likes

#5

thanks. Is there any alternative to Radian to send R code from ST4 to R console?

0 Likes

#6

Terminus uses and slightly extends pyte library for terminal emulation. It uses a proxy process to communicate with console host on Windows. Especially recent rust-based-versions are terribly slow, with regards to sending input and receiving responses.

It uses python generators to interpret output streams received from interpeter and translates it into text manipulation commands to render text to output panel / view. Keeping track of cursor positions, based on terminal commands is complex task, and as pure python implementation, limited in speed. Also regions being needed to render text with custom colors may quickly degrate rendering/update performance on large outputs.

Terminus sends required key codes for cursor placement based on custom key bindings. It doesn’t (or can’t?) track selection or caret location changes to do so. Hene mouse navigation is not supported by current implementation. As caret is also re-located by text output streams, it may be difficult to distinguish them from mouse interactions.

1 Like

#7

Thanks for the detailed info, another nail in the coffin for R work in ST, what a shame.

0 Likes