Damjan Cvetko

There's also an easier, far more ugly solution: Spawn one instance of Phpactor per workspace https://github.com/zobo/vscode-php-intellisense/pull/34 Not recommending, just saying...

This would work, since we are talking about a standard DAP message, and the Language Server extension doesn't need to be aware of what the specific implementation is providing debug...

I would argue against that. In the concrete case, php-debug, the adapter barely understands any PHP, let alone the AST and DOM required to understand what variable positions would be...

Hi Ben. Great to see you are implementing this in your LS. Indeed this is a known problem that I'm just revisiting due to the recent changes I did. I'm...

Interesting, it uses the `watch` context. I guess I'll have to build in at least some basic expression parsing to catch things like `$array[$key]` and in that case not use...

That is a very interesting observation. I have, until now, brushed this of as - well there is no context to figure out what variables are in scope and what...

Yes, roughly. But not sure what communication would be required between the two extensions. As the stack trace information is only preset inside the debug adapter, and the extension itself...

Will look at this asap

The real question here is, why is this not already working? https://code.visualstudio.com/docs/reference/variables-reference#_environment-variables

I remembered something about this. I already reported this and provided a patch but not sure what happened to this. https://github.com/microsoft/vscode/issues/245798 https://github.com/microsoft/vscode/pull/245989 I looks like it got merged, but I...