Tools
Eclipse
Applies to plain Eclipse and to the IDEs built on it, including STM32CubeIDE and NXP MCUXpresso.
Shortcuts
| Action | Windows / Linux | macOS |
|---|---|---|
| Block (column) selection mode | Alt+Shift+A | Alt+Cmd+A |
| Format source | Ctrl+Shift+F | Cmd+Shift+F |
| Organise imports | Ctrl+Shift+O | Cmd+Shift+O |
| Quick fix | Ctrl+1 | Cmd+1 |
| Open type | Ctrl+Shift+T | Cmd+Shift+T |
| Open resource (any file) | Ctrl+Shift+R | Cmd+Shift+R |
| Jump to declaration | F3 | F3 |
| Find references in workspace | Ctrl+Shift+G | Cmd+Shift+G |
| Back / forward in edit history | Alt+← / Alt+→ | Cmd+[ / Cmd+] |
| Toggle comment | Ctrl+/ | Cmd+/ |
| Rename (refactor) | Alt+Shift+R | Alt+Cmd+R |
| Toggle breakpoint | Ctrl+Shift+B | Cmd+Shift+B |
| Run / resume debug | Ctrl+F11 / F8 | Cmd+F11 / F8 |
| Quick access (command palette) | Ctrl+3 | Cmd+3 |
Block selection is a toggle: press Alt+Shift+A again to return to normal
selection, otherwise ordinary click-drag keeps producing rectangular selections.
Formatter settings
Window ▸ Preferences ▸ C/C++ ▸ Code Style ▸ Formatter (or Java ▸ Code Style ▸ Formatter). Built-in profiles cannot be edited — use Edit… and Eclipse will
prompt to save a copy under a new name. Export the profile as XML and commit it
so everyone on the project formats identically.
Known issues
Run and Debug are slow
Uninstall the ANSI Escape in Console plug-in. It hooks every line written to
the console and the overhead becomes obvious on chatty firmware logs.
Help ▸ About ▸ Installation Details ▸ Installed Software, select the plug-in,
then Uninstall… and restart.
Other common causes, worth checking before blaming a plug-in:
- Console output volume itself. Cap it under
Preferences ▸ Run/Debug ▸ Consoleor turn offLimit console outputonly when you really need the full log. - Workspace indexer running in the background. The progress bar in the status bar shows whether the C/C++ indexer is still working.
- Too small a heap for the IDE. Raise
-Xmxineclipse.ini(orstm32cubeide.ini) on large workspaces.
Build Analyzer is empty
See STM32CubeIDE — the linker has to emit a map file first.
EZyoutuber
Auto generator subtitle
Scoop
Scoop is a command-line installer for Windows.
Syncthing
syncthing.exe -no-console
syncthing.exe -home PATH
Postman
Auto Update Environment
Tests
var res = pm.response.json();
pm.environment.set('API_TOKEN', res.token);
Sparkol VideoScribe
videoscribe.co: A user-friendly animation tool.
VSCode
Switching Tabs After Debugging
Here are the steps to prevent Visual Studio Code from switching tabs after debugging using CMake Tools:
Open Visual Studio Code and go to File -> Preferences -> Settings. In the search bar, type "debug" to find debug-related settings. Locate the setting "Debug: Open Debug" which controls the tab-switching behavior after debugging. Set this option to "neverOpen" to prevent automatic tab switching after debugging completes. This configuration change should allow you to stay in the CMake Tools tab after debugging instead of being automatically switched to the Debug tab.
Plug-in
# Export all the extensions
code --list-extensions > vscode-extensions.txt
# Install all the extensions
Get-Content vscode-extensions.txt | ForEach-Object {code --install-extension $_}
Cortex-Debug