Damjan Cvetko

I would do this as a VS Code only change, since the extension infrastructure already has some nice helpers DebugConfigurationProvider / resolveDebugConfigurationWithSubstitutedVariables https://github.com/microsoft/vscode-python/blob/3698950c97982f31bb9dbfc19c4cd8308acda284/src/client/common/variables/environment.ts#L21

I've taken the Node.js debugger as a source and implemented something similar. There the original code: https://github.com/microsoft/vscode-js-debug/blob/766b04bcbb737ad711b50970055eb9782f838c07/src/targets/node/nodeLauncherBase.ts#L275 There is no `${env:` substitution in the way you suggested. First, this is...

Indeed, a better guide would be welcome.

Perhaps the official VSCode documentation could also be used as reference: https://code.visualstudio.com/docs/editor/debugging

Hi! The issue that you linked isn't directly related to the problem you are describing. It is interesting, that you moved the DEBUG CONSOLE into the Side bar. Normally it...

Hi. That makes sense, since the extension does two way mappings (for breakpoints and for opening files) and if the mappings overlap (v:\www) it can choose the wrong one. I'll...

Hi! That's one of the shortcomings of VS Code. I will research the issue a bit more soon.

Hi! I will have a more in depth look at this a bit later. However I have already discussed a similar topic with Derick. There is currently a dbgp proxy...

Hi! Thanks for this, but I need to look into this as the runtime executable (php.exe) shouldn't come from any VSCode setting. At least not by default...

Hi. I revisited this issue, but it does not make much sense. `php.validate.executablePath` is used by php intellisense or the build in php validator, not by this extension. If it...