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
The behaviour of the shell output of the wrapper is odd on Windows to the point it is practically unusable with CMD and Powershell without clearing history before running a command.
It is hard to describe but the output sometimes does not update and displays the actual command prompt path, then if you press enter, it kind of update but you missed the question that was asked. I think this happens if there is already content/history in the shell, typing cls mostly fix the issue.
Cheers,
Thomas
The text was updated successfully, but these errors were encountered:
Hello,
The behaviour of the shell output of the wrapper is odd on Windows to the point it is practically unusable with CMD and Powershell without clearing history before running a command.
It is hard to describe but the output sometimes does not update and displays the actual command prompt path, then if you press enter, it kind of update but you missed the question that was asked. I think this happens if there is already content/history in the shell, typing
cls
mostly fix the issue.Cheers,
Thomas
The text was updated successfully, but these errors were encountered: