sekogan
commented
9 years ago It's an interesting question, thanks for bringing it up. I noticed the issue myself and it is really annoying. Finally I've got a good reason for doing a little research :-)
First of all the issue is not something that is unique for Markdown Light: all markdown packages for Sublime have it. It doesn't prove anything but is a symptom that the reason is somewhere outside my package.
I've done some experiments with C++ syntax file. Class definitions are handled by a block at line 402. That block captures keywords "class"/"struct" followed by an identifier. There is another block at line 458 inside the previous one for capturing curly braces and everything inside them. That block includes $base at line 496. Actually I did't find any documentation regarding $base but it seems to me that the original intent was in applying all C++ grammar rules recursively to everything inside curly braces.
Let's step back and recall that the C++ code is located inside Markdown file and is enclosed within fenced code block.
The problem is that $base refers to Markdown syntax, not C++. One can easily verify it in Sublime with the following example:
```c++
class A {
***This text will be surprisingly bold in Sublime***
};
Replacing `$base` with `$self` in C++ syntax file solves the issue because `$self` refers to current grammar which is C++ in our case.
Again, I am not 100% sure because the `$base`/`$self` topic is poorly covered in documentation, but for me this is the most reasonable explanation.
So the workaround is:
1. Use PackageResourceViewer -> Open Resource -> C++ -> C++.tmLanguage
2. Save it in your Packages directory.
3. Replace all `$base` with `$self`.
Gnnng
At first, thanks for this bravo plugin.
When I use the syntax ``` (code block) in markdown to put my c++ code in, the rendered area exceeds the code section. It looks like this:
But the normal situation is this (which I remove the type string "c++" to compare with the previous image)
And the most important thing is, this bug is decided by the code I put in the block. The display in the second block of the above image is correct. I guess some code string broke the parser and cause the issue but I am not sure.
The issue doesn't bother me too much, because I can fix it by declaring nothing about the language type. But I wish it could be fixed in the plugin.
I am using Sublime Text 3 Build 3065.