REPL - can't handle arrow input on Msys2

[RickBarretto]

Describe the bug The REPL can't handle arrows input while running on Msys2. The same is not true for VsCode/ium, for instance.

What are the problems it causes:

• Malfunction of the REPL's history
• I can't turn back to rewrite something

Ok, I'll do an explanation story-like step-by-step as an example:

I have a list a: [1 2 3 4 5] and I chopped it by mistake doing an in-place return.

What I would do to undo my mistake? I should return on REPL's history to got the original a. Let's see what happens here:

As you can see above, the cursor went to the above line. (weird...) But let's continue, since in theory I'm on print as.value a line, let's press twice more Arrow up to return to a: [1 2 3 4 5] in history, and then press Enter:

Yes, What was bad, is even bad now... 💣

But, as I said, it doesn't affects just the history... It can't handle arrows. Let's see more!

Returning to our example story. Now I want to see what chop actually does, since it was not the function I wanted to use to process a...

But before press Enter, I saw that I made a mistake here again. I'm not passing chop as a literal, and I would get big problems here. So, let's return to left, as in any other terminal application, and add the ' before chop, easy right? Let's see!

Wait, where is the c of chop now? I just returned my cursor to before chop and pressed '. Let's press Enter now and see what happens:

Yes, It made a big mess, passing nfo 'hop to the REPL's eval...

---

Now, doing the exact same steps on VsCode/ium:

Desktop (please complete the following information):

• OS: amd64/windows
• Version v/0.9.83 b/170
• Msys2: MSYS_NT-10.0-14393 version 3.4.6.x86_64 (gcc version 11.3.0 (GCC) ) 2023-02-15 18:03 UTC
• VsCodium: 1.76.1

Additional context This comment started this issue

[drkameleon]

Total disaster! lol

And imagine I thought MSYS2 was the "safe" way to go about Windows...

I'll have to spin a cloud instance and start testing.

Great job spotting all this! 😉

[stale[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[stale[bot]]

Closing issue as stale.