Vscode-code-runner: Suggestion: about temporary file

[Xeonacid]

Currently, after running selected code in Code Runner, it leaves a temporary file with the name set in code-runner.temporaryFileName in working dir. If we don't need that any more, we have to remove it manually.
What about adding a setting about whether the temporary file would be removed automatically after running?

[formulahendry]

Are you running it in terminal? If not in terminal, it should be removed.

[Xeonacid]

@formulahendry Yeah, I'm running it in terminal.

[formulahendry]

OK, for now, you could customize the code-runner.executorMap by yourself.

[Xeonacid]

@formulahendry Could you give an example?

[formulahendry]

Please refer to https://github.com/formulahendry/vscode-code-runner#configuration

[Xeonacid]

@formulahendry I've read this, but sorry for that I have no idea about how to determine whether it's running a temporary file. 😢 Could it read the code-runner.temporaryFileName variable? I would really appreciate it if you could give a little example...
BTW, the code-runner.executorMap is separate settings for each language. Does it have any possible to set globally?

[formulahendry]

You could just use $fullFileName or $fileName, e.g. `"python": "python $fullFileName && del $fullFileName". And, currently it is no support to set globally.

[Xeonacid]

@formulahendry Thanks a lot, but... this would make an unconditional removal, whether it's the temporary file created by running selected code or not. TAT

[formulahendry]

Oh... You are right...

[formulahendry]

Or just use something like "python": "python $fullFileName && del tempCodeRunnerFile.py"

[Xeonacid]

@formulahendry Thanks! (To be honest, I've been using in this way before opening this issue :P
It would be grateful if you could implement a global setting as mentioned above, and/or make variables like the code-runner.temporaryFileName visiable in the code-runner.executorMap!

[filipesilva]

I was also trying to find a workaround/solution for this situation. I can do && rm tempCodeRunnerFile.js for now though, that's fine enough. But it would be a cool option. Thanks for your work!

[filipesilva]

For those interested, this is how my executorMap looks like for the languages I use:

  "code-runner.executorMap": {
    "javascript": "node $fullFileName && rm -f $dirWithoutTrailingSlash\\\\tempCodeRunnerFile.js",
    "typescript": "ts-node $fullFileName && rm -f $dirWithoutTrailingSlash\\\\tempCodeRunnerFile.cljs",
    "clojure": "lumo $fullFileName && rm -f $dirWithoutTrailingSlash\\\\tempCodeRunnerFile.cljs",
  },

Notes:

• I am on Windows, using GitBash, and running on terminal.
• the -f flag is needed to prevent rm: cannot remove 'path/here': No such file or directory when running the real file (without a selection).
• using $dirWithoutTrailingSlash is needed because the path is surrounded by quotes and the final slash on windows will escape the quote.
• double escaped slashes (\\\\) are needed otherwise it will end up as \tempCodeRunnerFile, and \t means escape t.
• will not delete the file if code execution fails.

It works but there are a few things to keep in mind when doing it manually.

[mil1i]

It is not deleting the temp files for me whether it is run in Output or Terminal. They always persist. Doesn't matter which language either.

In order for them to delete, I must use the mappings like above with a 'rm tempCodeRunnerFile.' command at the end.

[tgreen7]

also not getting removed for me with or without "Run in Terminal"

[cherry-geqi]

Why not just create those temp files in system temp dir?

[filipesilva]

@cherry-geqi the file system environment often matters even for snippets. Mostly for imports, but sometimes for global definitions.

[cherry-geqi]

As far as I know, many executors accept scripts from stdin.
Instead

node /path/to/script.js

We can

node < /path/to/script.js

This will avoid the env issues.

[filipesilva]

That's a great idea!

[Xeonacid]

@cherry-geqi Sounds good, but it's not a robust way...