search

mfornet / acmx

Competitive programming made simple. VSCode extension.
MIT License
148 stars 9 forks source link

stderr file not showing after compilation errors when using a terminal with bash on Windows #111

Closed MickyOR closed 2 years ago

MickyOR commented 3 years ago

After compilation errors, I get this in the terminal:

$ type "C:\HomePath.acmx\solutions\Contest\Problem\attic\stderr" bash: type: C:\HomePath.acmx\solutions\Contest\Problem\attic\stderr: not found

mfornet commented 3 years ago

The issue is not having a unified way provided by the vscode api to display text in a terminal. The culprit code: https://github.com/mfornet/acmx/blob/master/src/errors.ts#L33

Salil03 commented 2 years ago

We could try recompiling the file but this time in the terminal. This will compile the file twice(if stderr is not empty) but it will work on all os. I could submit a PR for this if you want

mfornet commented 2 years ago

Yes please, go ahead and submit a PR. More than welcome

Salil03 commented 2 years ago

I used https://code.visualstudio.com/api/references/vscode-api#Pseudoterminal api to display the stderr in terminal itself without compiling it twice. It also does not use any os specific commands. Hopefully this will close this long standing issue!