-
Notifications
You must be signed in to change notification settings - Fork 11
feat: add an expressive-code plugin to support marks in code block #62
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
|
@Sudrut is attempting to deploy a commit to the microcber's projects Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
|
Could you also update the development documentation at |
Ok I will try to add instructions to that page in a section named "Code block inline markers". I couldn't figure out a better name for it. |
|
The documentation is added. Sorry I'm terribly sick and will be unable to work for a period of time. |
Lancern
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM!
With the plugin one can specify part of code block as "is a syntax notion", "is exposition only", or "is optional" rendered in cppref style.
Enable this feature by adding
cxx-markafter the language name of code block's opening fence. When enabled, inside the code block type /*$s:content*/ for syntax notation, /*$expos:content*/ for exposition-only things and /*$opt*/ for an optional mark. The syntax /*$...*/ above is chosen just for convenience.For example, provided the following
DeclDoccomponent:Output: