VSCode + Clangd: type annotations become obtrusive - how to disable?
I'm using VSCode 1.65.0, the clangd extension, and clangd from latest LLVM (14.0).
It seems to have introduced a feature where it displays type-hints whenever I use auto. Here is an example:
This is becoming very obtrusive to me. How can this be turned off? I couldn't find documentation about this feature.
Thanks.
Solution
You can go to the command palette (⇧⌘P or Ctrl+Shift+P) and start typing clangd: Toggle inlay hints to turn this feature on/off.
- How to cancel the commit while the Source Control VSCode is waiting for the commit message?
- Visual Studio Code - Can "OPEN EDITORS" panel be sorted?
- Jest vscode-jest Extension Running All Tests (Despite Proper Configuration and Using Git)
- Debugging Python C++ extension from Visual Studio Code on Linux
- vs code: Error while fetching extensions. Failed to fetch
- VSCode monospace fonts are not monospaced, how to fix this?
- How can I change cursor color in VSCode?
- How to change vscode-server directory
- VS Code cursor appear as a block and without typical editing abilities
- Visual Studio Code Jupyter not recognising conda kernel
- PyLance in Visual Studio Code does not recognise Poetry virtual env dependencies
- How to setup VSCode to show typescript error inline
- How do I access a dev tunnel from a service/authenticate between apps?
- How to change the version of php in PHP Intelephense?
- How can I download a .vsix version of an extension?
- Disable untitled editor improvement - first line name in the title
- VSCode insert tab character manually
- VSCode is running sh in terminal
- How to fix "failed to install VS code server" error
- Visual Studio Code stops making color pickers after 495th color picker
- How to disable multiline select in vscode
- In VS Code, is there a way (or extension) to run a command ( I.E. 'editor.action.insertSnippet') on each line of text that is selected in the editor?
- How to fix ctrl+f on visual studio code
- ESLint Prettier: Parsing error: Unexpected token with
- Error: Could not find any Visual Studio installation to use when building node-sass with node-gyp on Windows
- How to solve vs code - gopls command is not available
- Why do I get a "ModuleNotFoundError" in VS Code despite the fact that I already installed the module?
- How to send ctrl+f to shell in VS Code's integrated terminal?
- Invalid copilot token: missing token: 403
- VS Code's Source Control icon has gone missing, how do I get it back?