You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here is the snippet in question, which demonstrates the problem:
.. cpp:function::const m64::frame& at(uint32_t index) const
Returns a reference to the :cpp:expr:`index`\th input frame of this M64.
Unlike :cpp:func:`m64::operator[]()`, :cpp:expr:`at()` checks input bounds.
:param index: The index of the frame to get
:return: the requested frame
:throws std::out_of_range: if :cpp:expr:`index >= this->size()`
GitHub highlights Sphinx's directives and info fields, but this extension does not.
The text was updated successfully, but these errors were encountered:
Good suggestion! I'll try working out a pattern to use for all the sphinx language domain entries, looks like they get treated as comments or raw monotyped strings.
Will be fixed in #5, where the snippet now looks like this in the editor:
I initially added language specific highlighting for literal blocks like :cpp:expr:index >= this->size()`, but this looked really messy, and it was hard to distinguish the contents from surrounding rst.
I'll do some more testing before merging and publishing a new release to the marketplace.
Causes vscode-restructuredtext/vscode-restructuredtext#309.
Here is the snippet in question, which demonstrates the problem:
GitHub highlights Sphinx's directives and info fields, but this extension does not.
The text was updated successfully, but these errors were encountered: