Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
command 'macros.commentDown' not found
See original GitHub issueI’m using vscode 1.19.0 on Mac OS X. I’ve added the “macros” key and “commentDown” example macro to my user settings.json file:
I’ve also added example shortcut to my keybindings.json
But when I press cmd+ctrl+/ vscode complains with command 'macros.commentDown' not found:
Have I configured something incorrectly? I’m expecting it to comment the line, not show the above error.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:5
- Comments:8
Top Results From Across the Web
Cannot locate certain Microsoft Build command Macro ...
In my investigation into the problem, I am trying to determine where the values for many of the build command macros are coming...
Read more >"File not found" When using command instead of plain text - TeX
1 Answer 1 · Path to file. The path to the file is to be stored in the macro \filename@area . · Name...
Read more >macros - Visual Studio Marketplace
Extension for Visual Studio Code - automate repetitive actions with custom macros.
Read more >Customize Commands categories: "Macros" missing
Customize Commands categories: "Macros" missing ... under "Tools" and discovered I don't have the command category "Macros" listed there.
Read more >THE WHOLE SCOOP ON THE CONFIGURATION FILE
It can be used to correlate information gathered from those headers using the macro storage map. One possible use is to check for...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I had this same issue until I noticed that the “macros” section in settings has a warning on it (the squiggly green underline in your first screen-cap).
This usually means VS Code doesn’t know what that setting is - i.e. VSCode isn’t loading the extension. In my case, all I had to do was uninstall/reinstall the extension.
It’s working for me on both macOS and Ubuntu 16.04.
I had the exact same issue as well. Restarting Visual Studio Code fixed it.