vindicatorr

I've been away for awhile, but do remember XSD a little. Yeah, that magic your extension does, getting the project includes, is what I thought would also be used for...

No worries, and no rush. I have no dependency on it and think I might only had installed it for json intellisense or something. I really don't remember.

Hey, I'm back at it, and your extension isn't the only one (https://github.com/OmniSharp/omnisharp-vscode/issues/2851)... I've got 3 instances of rzls still alive, and 6 instances of yours, all after having closed...

Maybe, though that would also mean I need to downgrade nodejs dependencies, and be wary of what doing so would break what already exists, no? I know it worked when...

Just an update: ``` $ GENERATE_SOURCEMAP=false npm start > [email protected] start > concurrently -k "npm run start:frontend" "npm run start:electron" [0] [0] > [email protected] start:frontend [0] > cross-env BROWSER=none PORT=3001...

I'm sure `upgarde` was just a mistype for `upgrade` by them. Anyway, just `source` a v16 node environment like I did or wait for the next LTS (v18).

@aster94 I came across that today and was very hopeful of making use of it... buuuuut I was bummed to find that atmega16 doesn't have the capability to use it,...

Does yours also take into account the `${workspaceFolder:}` syntax?

Can confirm that the `${workspaceFolder:}` syntax does work now. Previously: `"cwd": "${workspaceFolder[]}",` Currently (previously failed): `"cwd": "${workspaceFolder:}",`

Not specific to the workspaceFolder usage: https://github.com/augustocdias/vscode-shell-command/pull/19#issuecomment-1902904006 (actually, that would be a separate/unrelated PR. Dunno if I should open an issue on it, or my comment in the PR is...