Bug when commenting macros (# is causing issues)
See original GitHub issueDescription
There is a small problem when documenting a macro.
- The < #de > is removed from the macro definition
- No line break is inserted after the comment
See code example below and screenshots attached
Code example
/** <press enter>
#define MY_MACRO 1
Expected result
/**
* @brief
*
*/
#define MY_MACRO 1
Actual result
/**
* @brief
*
*/fine MY_MACRO 1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:11 (5 by maintainers)
Top Results From Across the Web
Bug in Word? Adding comments via macro does not work in ...
Hi,. I have a macro that adds a comment to the selected text in Microsoft Word. This seems to work, but in rare...
Read more >1224660 – Macros shouldn't expand in comments
Bug 1224660 - Macros shouldn't expand in comments ... Macros are expanded everywhere, so check if it can cause a problem in this...
Read more >Bug in macro comments feature.... | EverQuest Forums
I just started adding comments to my in-game macros (socials). ... is going to cause it to bug out (or attack that specific...
Read more >comments cause errors? - Programming - SAS Communities
Solved: I have just [almost] went insane trying to debug my SAS program!! Luckily brighter minds prevailed :smileysilly:.
Read more >399957 – Trailing comments behind macros are ... - Bugs - Eclipse
... is the second issue I've had with macros in the code causing formatting issues. It'd likely be a good idea to handle...
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 FreeTop 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
Top GitHub Comments
Hi @klonq123 @neocliff @samkearney ,
this will be fixed in 0.7.0 which I just triggered. The update should be visible in VS Code in ~15 minutes. Hope you’re still enjoying the extension and this makes your life a bit easier 😃
@christophschlosser I am and it does! Thank you!!