opening csi.exe in Terminal isnt letting me use the Up key to view previous commands #6356

Closed
opened 2026-01-31 00:36:32 +00:00 by claunia · 5 comments
Owner

Originally created by @hexbinoct on GitHub (Feb 9, 2020).

Environment

Windows build number: 10.0.18363.628
Windows Terminal version (if applicable): 0.8.10261.0

Any other software?
Visual Studio 2015


# Steps to reproduce

So Open Windows Terminal and open a cmd tab. Type the following:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64
adjust the path to whatever is valid for you, I am using Visual Studio 2015. After the above executes, 
now type "csi.exe" (without the quotes) and hit Enter, you will be in the c# interactive console for c# scripting. 
Now write anything which is a valid c# expression, for example:
int x =0;
which does nothing but sets variable "x" to zero. Now use the keyboard Up arrow key so that you can use that same expression you just wrote, you wont get anything, which should not be the case.

# Expected behavior

When you press the Up key, you should be able to go through the history of everything you have written before one by one.

# Actual behavior

Up key doesnt give you anything that you wrote in the csi.exe before
Originally created by @hexbinoct on GitHub (Feb 9, 2020). # Environment Windows build number: 10.0.18363.628 Windows Terminal version (if applicable): 0.8.10261.0 Any other software? Visual Studio 2015 ``` # Steps to reproduce So Open Windows Terminal and open a cmd tab. Type the following: "C:\Program Files (x86)\Microsoft Visual Studio 14.0\VC\vcvarsall.bat" amd64 adjust the path to whatever is valid for you, I am using Visual Studio 2015. After the above executes, now type "csi.exe" (without the quotes) and hit Enter, you will be in the c# interactive console for c# scripting. Now write anything which is a valid c# expression, for example: int x =0; which does nothing but sets variable "x" to zero. Now use the keyboard Up arrow key so that you can use that same expression you just wrote, you wont get anything, which should not be the case. # Expected behavior When you press the Up key, you should be able to go through the history of everything you have written before one by one. # Actual behavior Up key doesnt give you anything that you wrote in the csi.exe before
claunia added the Needs-Tag-FixNeeds-Attention labels 2026-01-31 00:36:32 +00:00
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 10, 2020):

I'm guessing this is a /dupe of #2397

@DHowett-MSFT commented on GitHub (Feb 10, 2020): I'm guessing this is a /dupe of #2397
Author
Owner

@ghost commented on GitHub (Feb 10, 2020):

Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!

@ghost commented on GitHub (Feb 10, 2020): Hi! We've identified this issue as a duplicate of another one that already exists on this Issue Tracker. This specific instance is being closed in favor of tracking the concern over on the referenced thread. Thanks for your report!
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 10, 2020):

Interesting. CSI is actually using cooked read, and I cannot reproduce this on my machine.

What keyboard layout are you using? What locale is your machine set to?

If you press F7 after entering a command, do you get a purple-on-white popup (behind an annoying caret browsing dialog) that contains hello?

@DHowett-MSFT commented on GitHub (Feb 10, 2020): Interesting. CSI is actually using cooked read, _and_ I cannot reproduce this on my machine. What keyboard layout are you using? What locale is your machine set to? If you press <kbd>F7</kbd> after entering a command, do you get a purple-on-white popup (behind an annoying caret browsing dialog) that contains `hello`?
Author
Owner

@hexbinoct commented on GitHub (Feb 11, 2020):

its working now and I have no idea why now and why wasnt it working yesterday, I had a normal cmd.exe running csi and a Terminal running cmd running csi (side by side) and the up key wasnt working in the Terminal. I followed my instructions above and it did work now, tried it twice and its working. So I will close this issue.

@hexbinoct commented on GitHub (Feb 11, 2020): its working now and I have no idea why now and why wasnt it working yesterday, I had a normal cmd.exe running csi and a Terminal running cmd running csi (side by side) and the up key wasnt working in the Terminal. I followed my instructions above and it did work now, tried it twice and its working. So I will close this issue.
Author
Owner

@DHowett-MSFT commented on GitHub (Feb 11, 2020):

Thanks for following up!

@DHowett-MSFT commented on GitHub (Feb 11, 2020): Thanks for following up!
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/terminal#6356