Damjan Cvetko

What you can do is, if you have the code both on server and locally, run the script on the server (either from command line or from web server) and...

There are options for this: In case of Listen, you can use `preLaunchTask` and reference a task in tasks, like this: launch.json ``` { "name": "Listen for Xdebug", "type": "php",...

The other `launch.json` key is `serverReadyAction`...

Hi! I'm not sure I'm getting all the information here. The issue is very old (2018) and in the mean time the path mapping code was improved to handle different...

Hi! Would you be able to give me exact examples? Workspace path (UNC), mappings config, VSCode logs so I can try to make some tests to reproduce the issue? Thanks!

Hi! In your launch.json add `log: true`. In VSCode Panel the tab DEBUG CONSOLE will contain a comprehensive log after Xdebug connection happens. Do a right-click and Copy All and...

Hi. I do see some strange things I need to investigate. Here two breakpoints being set from VSCODE to DAP: ``` source: { name: 'app.php', path: '\\\\HOSTING64.DARKDRAGON.LAN\\wwwroot\\ccenter\\app-core\\app.php' }, lines: [...

I'm looking into it. Have managed to compile and run the intelephense extension and got a trace of LSP messages (this helped: https://code.visualstudio.com/api/language-extensions/language-server-extension-guide). I need to setup a linux share...

Hi! Yes, I agree, that is a problem, coming from the fact that there is one VS Code Debug Session running, and connected DBGP sessions presented as Threads. Although I...

Hi! Thanks for the report. I have access to a mac and will test it out.