Tom

Does this still occur, or did deleting `%appdata%\Code\User\workspaceStorage` solve the issue?

The debugger uses stdio to communicate with lua, so using calls like `io.read()` will interfere with that. If #2 is implemented at some point, that would allow debugging lua code...

Update on this issue: Support for pipe communication was added in version 0.3.3. In theory, this would allow io.read() to be used, but vscode does not provide a built in...

I think the way I documented this might be confusing. To switch to pipe mode, your launch.json needs to look like this: ``` ... "program": { "communication": "pipe", "command": "C:\\Program...

Looking at the error you posted, though, I think you will still run into problems. I don't currently account for the possibility that io.stdout doesn't exist at all. I'll add...

This isn't supported at the moment. I'm actually not sure if VSCode itself even supports this. If it does, it might be possible to implement using a polling mechanism, similar...

`os` is used specifically for `os.getenv` to read settings passed from the vscode extension. It might be possible to refactor things to not require this. But, not having `io` is...

This looks like an internal error is occurring in the debugger and preventing the values from populating. Do you see any errors in the Debug Console in vscode? If not,...

This will require remote debugging support to work (#2).

This may be possible now but I'll have to investigate. Attaching presumes that the Lua program is running when the debugging extension starts, which means Lua needs to create the...