Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

${workspaceRoot} not supported

See original GitHub issue

I realize code-runner supports using $workspaceRoot in the paths, but there are two problems with it, and they are possibly related:

It doesn’t work with python virtual environments when used. It gets stuck and has to be stopped.
{$workspaceRoot} is the syntax MS uses. So, maybe this is related to whatever causes 1)

. The syntax VS Code uses for this is ${workspaceRoot}, as in:

"python.pythonPath": "${workspaceRoot}\\learning_pytest\\Scripts\\python.exe"

Could code-runner be updated to support ${workspaceRoot}?

Issue Analytics

State:
Created 6 years ago
Comments:8 (4 by maintainers)

Top GitHub Comments

2reactions

formulahendrycommented, Dec 4, 2017

Oh, I see. You need to use "code-runner.executorMap": {"python": $workspaceRoot\\.env\\Scripts\\python.exe $fullFileName"} (If you use any customized parameters, $fullFileName will not be auto added)

0reactions

garytylercommented, Dec 5, 2017

OK yes thank you!

It wasn’t the main issue but if ${workspaceFolderBasename} worked with code-runner paths, the previous inquiry of mine should be possible. It would be nice if that worked someday.

Thank you for helping me!

Top Results From Across the Web

${workspaceRoot} in launch.json is not the Folder path #1104

${workspaceRoot} in launch.json is not the project Folder path that contains task.json. OS: Windows: Programming Language: C++

Variables reference - Visual Studio Code

The variable ${workspaceRoot} was deprecated in favor of ${workspaceFolder} to better align with Multi-root Workspace support. Why aren't variables in tasks.

VSCode environment variables besides ${workspaceRoot}

The following predefined variables are supported: ${workspaceFolder} - the path of the folder opened in VS Code; ${workspaceFolderBasename} - ...

Using with MS Visual Studio Code - Sming Framework

While not as sophisticated in C/C++ support as full featured Visual Studio, ... ${workspaceRoot} below is the directory with your project, this notation...

CMakeSettings.json schema reference - Microsoft Learn

remoteBuildRoot : Specifies the directory on the remote machine in which CMake generates build scripts for the chosen generator. Supported ...