.vscode/settings.json

{
  "editor.formatOnSave": true,
  "editor.defaultFormatter": "trunk.io",
  "trunk.enableWindows": true,
  "files.insertFinalNewline": false,
  "files.trimFinalNewlines": false,
  "cmake.configureOnOpen": false,
  "[cpp]": {
    "editor.defaultFormatter": "trunk.io"
  },
  "[powershell]": {
    "editor.defaultFormatter": "ms-vscode.powershell"
  }
}
move my bt experiment into its own repo (about to remove ttn) 2020-02-01 08:30:53 -08:00			`{`
Setup Trunk (#2143) Co-authored-by: Ben Meadors <benmmeadors@gmail.com> 2023-01-17 16:35:26 +10:00			`"editor.formatOnSave": true,`
Enable Trunk on Windows 2023-07-31 21:37:55 +02:00			`"editor.defaultFormatter": "trunk.io",`
Stop Fiddling with Newlines! (#3341) 2024-03-06 13:09:46 -06:00			`"trunk.enableWindows": true,`
			`"files.insertFinalNewline": false,`
Turn off vscode cmake prompt - we don't use cmake on meshtastic (#4122) 2024-06-16 17:17:19 -07:00			`"files.trimFinalNewlines": false,`
tell vscode, if formatting, use whatever our trunk formatter wants (#4186) without this flag if the user has set some other formatter (clang) in their user level settings, it will be looking in the wrong directory for the clang options (we want the options in .trunk/clang) Note: formatOnSave is true in master, which means a bunch of our older files are non compliant and if you edit them it will generate lots of formatting related diffs. I guess I'll start letting that happen with my future commits ;-). 2024-06-27 11:14:16 -07:00			`"cmake.configureOnOpen": false,`
			`"[cpp]": {`
			`"editor.defaultFormatter": "trunk.io"`
Update device-install scripts (#6267) * fix example * check for firmware- filename * add powershell formatter setting * add crlf for ps1 * formatting * check for firmware- filename --------- Co-authored-by: Ben Meadors <benmmeadors@gmail.com> 2025-03-09 12:43:16 +01:00			`},`
			`"[powershell]": {`
			`"editor.defaultFormatter": "ms-vscode.powershell"`
tell vscode, if formatting, use whatever our trunk formatter wants (#4186) without this flag if the user has set some other formatter (clang) in their user level settings, it will be looking in the wrong directory for the clang options (we want the options in .trunk/clang) Note: formatOnSave is true in master, which means a bunch of our older files are non compliant and if you edit them it will generate lots of formatting related diffs. I guess I'll start letting that happen with my future commits ;-). 2024-06-27 11:14:16 -07:00			`}`
Setup Trunk (#2143) Co-authored-by: Ben Meadors <benmmeadors@gmail.com> 2023-01-17 16:35:26 +10:00			`}`