[all-commits] [llvm/llvm-project] daa1e1: [lldb-dap] Make lldb-dap.executable-path machine s...

[Jonas Devlieghere via All-commits]

  Branch: refs/heads/main
  Home:   https://github.com/llvm/llvm-project
  Commit: daa1e175531495b0ba07179a2c7fc609eb7d371c
      https://github.com/llvm/llvm-project/commit/daa1e175531495b0ba07179a2c7fc609eb7d371c
  Author: Jonas Devlieghere <jonas at devlieghere.com>
  Date:   2025-04-27 (Sun, 27 Apr 2025)

  Changed paths:
    M lldb/tools/lldb-dap/package.json

  Log Message:
  -----------
  [lldb-dap] Make lldb-dap.executable-path machine specific (#137485)

Change the scope [1] of lldb-dap.executable-path to
"machine-overridable":

> Machine specific settings that can be overridden by workspace or
> folder settings.

Practically speaking, this means that the path won't be synced across
machines and "(Not synced)" will show up next to the setting. I believe
it doesn't make sense to sync this setting (and I remember a bug report
where this caused trouble when using VS Code remotely), plus it matches
what clangd does for its corresponding setting. The extension has logic
to find the binary in your path or with `xcrun` which in most cases
should do the right thing and prevent you from having to override this
setting.

[1]
https://code.visualstudio.com/api/references/contribution-points#Configuration-property-schema



To unsubscribe from these emails, change your notification settings at https://github.com/llvm/llvm-project/settings/notifications