Thx :-)

Tbh I'm not sure whether it is a good idea to include that file in the git tree. It might be automatically changed by VSCode according to the local setup and it will be necessary to double-check we don't overwrite the file by mistake :/

It is in .gitignore, so unless git add --force is used, changes be users can be freely made and won't be tracked.

There is btw. no GUI or configuration knob in VS Code to manually point it to the file. With this PR, it will just work out of the box.

Tbh I'm not sure whether it is a good idea to include that file in the git tree. It might be automatically changed by VSCode according to the local setup and it will be necessary to double-check we don't overwrite the file by mistake :/

The same could apply to the settings.json that we provide. Of course users can overwrite this file or use settings from their custom workspace, etc.
Nevertheless, I think it is a good idea to provide a default and working environment for vscode users that they can customize the way they want.

Murdock results

✔️ PASSED

fb4c388 vscode: Add hard-coded path to compile_commands.json

Artifacts

• Documentation preview

Thx :)

It is in .gitignore, so unless git add --force is used, changes be users can be freely made and won't be tracked.

Sorry. This is not true. Once you add a file to the git tree it will be tracked. It does not matter if it in a gitignore (that also means .git/info/exclude).

I was sure that this did work for me at some point in time 😦

Looks like one has to run git update-index --skip-worktree <file path> these days to ignore changes.