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 meet the problem as the title. My sage version is 9.3 and it is installed on win10. The extention is seemed to use sage <filename> to run .sage file. However, on win10, vscode's console is run as cmd. The same command is not working while i run .sage file. On win, we can't run .sage file from cmd except use the official shell. Is the extension not working on win10?
ps. I tried to set the enviroment path but it doesn't work and i'm not clearly know how to set it.
The text was updated successfully, but these errors were encountered:
My suppose is right. I test the same extention on Kali which is a Debian-based Linux. As i guess, we can directly run sage from console. Thus the extention works through running command sage <filename>.
My suppose is right. I test the same extention on Kali which is a Debian-based Linux. As i guess, we can directly run sage from console. Thus the extention works through running command sage <filename>.
I meet the problem as the title. My sage version is 9.3 and it is installed on win10. The extention is seemed to use
sage <filename>
to run .sage file. However, on win10, vscode's console is run as cmd. The same command is not working while i run .sage file. On win, we can't run .sage file from cmd except use the official shell. Is the extension not working on win10?ps. I tried to set the enviroment path but it doesn't work and i'm not clearly know how to set it.
The text was updated successfully, but these errors were encountered: