profile
viewpoint
If you are wondering where the data of this site comes from, please visit https://api.github.com/users/toscm/events. GitMemory does not store any data, but only uses NGINX to cache data for a period of time. The idea behind GitMemory is simply to give users a better reading experience.

toscm/radian 0

A 21 century R console

toscm/vscode-markdown 0

Markdown All in One

startedyzhang-gh/vscode-markdown

started time in a month

fork toscm/radian

A 21 century R console

fork in 2 months

issue commentrandy3k/radian

Line wrap not working in Windows Terminal

Ah, I did not notice that you were using you're own prompt-toolkit version. Thanks for the explanation. In this case I can see that updating prompt-toolkit has a good chance to solve the problem.

So from my side it would be ok to close the issue now, unless you want to leave it open for other Windows Terminal users who might run into the same problem?

toscm

comment created time in 2 months

issue commentrandy3k/radian

Line wrap not working in Windows Terminal

Thanks for the hint. I checked which version of prompt toolkit I have installed and it's actually 3.0.18, but I think you're right anyways.

I tried to step through the code to find out where the line gets cut off and it seems to happen in line 171-172 of console.py (in the output.write_raw(buf); output.flush() part.

radian_ipdb

As a workaround I replaced the output.write_raw(buf); output.flush() with sys.stdout.write(buf); sys.stdout.flush() and it seems to work for now 🥳

radian_workaround radian_fixed

toscm

comment created time in 2 months

issue openedrandy3k/radian

Line wrap not working in Windows Terminal

Hi, it seems that line wrap is not working when using Windows Terminal (wt) instead of the default terminal emulator used by pwsh.exe/cmd.exe.

wt_radian_bug

I also did a quick check of running radian within wt inside WSL2-Ubuntu-bash instead of pwsh and suprisingly there it worked:

image

So my feeling is, that is has to do with some environment variables that need to be set or some special workarounds that radian does when running on windows, which aren't required for wt. (I tested all options that can be set through .radian_profile, e.g. radian.auto_width without success).

Used versions checks on windows:

  • Windows Terminal Preview Version: 1.9.1523.0
  • Radian: 0.5.11
  • Python: 3.8.8
  • R: 4.0.5

Used versions for check on WSL2:

  • Radian: 0.5.11
  • Python: 3.8.5
  • R: 3.6.3

Any advice on how to fix/debug this issue would be greatly appreciated.

created time in 2 months

fork toscm/stringr

A fresh approach to string manipulation in R

https://stringr.tidyverse.org

fork in 2 months