qmk_firmware/docs/other_vscode.md, branch master QMK firmware for my keyboards (Corne, Sweep Ferris) and trackball (Ploopy Adept) [docs] Replace Imgur-hosted images (#25690) 2025-11-04T00:05:39+00:00 James Young 18669334+noroadsleft@users.noreply.github.com 2025-11-04T00:05:39+00:00 a9739f78681dee290ede955c02b360f5c133f783 






Deprecate `qmk generate-compilation-database`. (#25237)
2025-05-05T23:52:41+00:00

Nick Brassel
nick@tzarc.org

2025-05-05T23:52:41+00:00

ac991405d0c9f47e815786f4732edd00d0f4f571












[Maintenance] builddefs: common_rules: overhaul debug information generation (#24352)
2024-09-01T17:54:53+00:00

Stefan Kerkmann
karlk90@pm.me

2024-09-01T17:54:53+00:00

d210590d4d8d859d1cd0960c0573391a9bf5d9a5

builddefs: common_rules: overhaul debug information generation

Debug information is always generated while compiling a binary, but
debugging is not the main use-case for the majority of users. Thus the
new default is to explicitly require them with `DEBUG_ENABLE=yes`. The
same is true for linker map files which are gated by the same flag.

As we target the gcc compiler and debug with the gdb debugger we can
specify the ggdb3 flag in the most verbose to get macro expansion.

Signed-off-by: Stefan Kerkmann <karlk90@pm.me>




builddefs: common_rules: overhaul debug information generation

Debug information is always generated while compiling a binary, but
debugging is not the main use-case for the majority of users. Thus the
new default is to explicitly require them with `DEBUG_ENABLE=yes`. The
same is true for linker map files which are gated by the same flag.

As we target the gcc compiler and debug with the gdb debugger we can
specify the ggdb3 flag in the most verbose to get macro expansion.

Signed-off-by: Stefan Kerkmann <karlk90@pm.me>






Vitepress conversion of docs. (#23795)
2024-05-30T02:00:41+00:00

Nick Brassel
nick@tzarc.org

2024-05-30T02:00:41+00:00

6ef97172889ccd5db376b2a9f8825489e24fdac4












Add instructions for debugging ARM with VSCode+BMP. (#11217)
2024-03-08T11:24:11+00:00

Nick Brassel
nick@tzarc.org

2024-03-08T11:24:11+00:00

8946aace5bb3c5397b79b0e5999cc9547e0ade65












Fix VS code live share extension link (#21585)
2023-07-23T08:07:17+00:00

peepeetee
43021794+peepeetee@users.noreply.github.com

2023-07-23T08:07:17+00:00

1ca34c2168d770d5d7b457d0c330fceeba581854












Far better VSCode intellisense support using clangd. (#20382)
2023-05-14T05:32:34+00:00

Nick Brassel
nick@tzarc.org

2023-05-14T05:32:34+00:00

0b672f87755b6326432dfa4c26379d31a025f7ba












Add recommendations for VSCode intellisense (#19402)
2023-04-03T00:05:48+00:00

Woongbin Kang
wbk@outlook.com

2023-04-03T00:05:48+00:00

ec83c0b1857b596c4b53186804bf4452831b3241












[Doc]Remove depracted extension links in vscode guide (#19842)
2023-02-14T03:23:36+00:00

しぐれ
23041178+ForsakenRei@users.noreply.github.com

2023-02-14T03:23:36+00:00

12f02dd8be7e043050ccc1be897d965f95016164












Update other_vscode.md (#17317)
2022-06-08T01:47:57+00:00

JunZuloo
JunZuloo@live.com

2022-06-08T01:47:57+00:00

5f72d542996a378d77f2c52fdfb4556edf8d87f8

Bracket pair colorizer has been deprecated since it is now a native feature, and VIM Keymap no longer exists, so I removed those 2 links.




Bracket pair colorizer has been deprecated since it is now a native feature, and VIM Keymap no longer exists, so I removed those 2 links.