Specify the current directory of the debugger

[actboy168]

I am using a process to implement the debugger, like this

{
    "program": ".\\bin\\lua.exe",
    "args": [
        ".\\script\\main.lua"
    ]
}

For program, its relative path is based on the extension directory. But for args, its relative path is based on the vscode directory. This directory has no value for the extension, so I want to specify the current directory of the program.

[weinand]

@actboy168 what does your JSON snippet from above show?
A part of the extension's package.json or a launch config from the launch.json?

[actboy168]

package.json

[weinand]

why are you trying to "reach" outside of your extension folder for one argument (the .\\script\\main.lua)?

The program to debug comes as an argument via the "launch" request.

[actboy168]

".\script\main.lua" is the code for my debugger, not the code to debug target.

[weinand]

If I remember correctly then a debug adapter executable is specified like this:

	"runtime": ".\\bin\\lua.exe",
	"program": ".\\script\\main.lua"

or even:

	"runtime": "lua",
	"program": ".\\script\\main.lua"

[actboy168]

According to the docs, runtime only supports two options: node and mono.

https://github.com/Microsoft/vscode-docs/blob/master/docs/extensions/example-debuggers.md

[actboy168]

I think my package.json is ok. VSCode does create a lua.exe process and correctly applies args as a command line argument. The problem is that the current directory of this process is the directory of VSCode, and I want to change it.

[weinand]

The doc might be outdated. The implementation probably allows any runtime.
Please try it.

[actboy168]

OK, runtime is also work. But the current directory of the process is still the directory of VSCode.program will be rewritten as an absolute path based on the extension directory, which will solve some of my problems. But I still need to know where the extension directory is.

[weinand]

This is fixed by the new API made available as part of #56646