You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running radian on Windows 10 with the following
R version 4.1.3 (2022-03-10) -- "One Push-Up"
Platform: x86_64-w64-mingw32 (64-bit)
through an Anaconda install with Python 3.11.7.
I have an issue that appeared recently with the radian prompt: when I type a character, in some cases the wrong character is displayed on the prompt. The right character is, however, interpreted and executed because the code runs.
In particular, the backspace character is printing the previous characters in a palindromic manner.
For example typing the sequence a>b>c>⬅>⬅>⬅ gives on prompt
r $> abcba
but the interpreted code is indeed an empty string.
I had radian working fine for some time, then this bug appeared, probably because of some dependency changing in Python, but I cannot spot the culprit. Does this ring a bell for anyone ?
The text was updated successfully, but these errors were encountered:
I have a similar issue where when running a chunk, sometimes the last character of the chunk is randomly added instead of an end of the line. This make the code hang waiting for the end of the line and do not execute...
For example here, I run the same chunk 4 times, where the two time did not work ...
this also happens if Im running a .R file line by line..
Using windows 10x86-64
Hello,
I'm running radian on Windows 10 with the following
through an Anaconda install with Python 3.11.7.
I have an issue that appeared recently with the radian prompt: when I type a character, in some cases the wrong character is displayed on the prompt. The right character is, however, interpreted and executed because the code runs.
In particular, the backspace character is printing the previous characters in a palindromic manner.
For example typing the sequence a>b>c>⬅>⬅>⬅ gives on prompt
but the interpreted code is indeed an empty string.
I had radian working fine for some time, then this bug appeared, probably because of some dependency changing in Python, but I cannot spot the culprit. Does this ring a bell for anyone ?
The text was updated successfully, but these errors were encountered: