-
Notifications
You must be signed in to change notification settings - Fork 200
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
Add an Span (Inline) Comment Token? #116
Comments
So, this is the actual docutils AST rendered:
<document source="notset">
<paragraph>
line 1
<comment xml:space="preserve">
a comment
<paragraph>
line 2 This is the 'correct' behaviour, given the fact that (as it stands) a LineComment is defined as a block level entity, What you are after here is a span level (a.k.a inline) comment entity, whereby the comment is parsed as: <document source="notset">
<paragraph>
line 1
<comment xml:space="preserve">
a comment
line 2 This essentially would require an additional syntax element to be implemented, which would be fairly tricky, so I can't promise I could achieve this any time soon. Perhaps at a minimum the documentation should make this clear. |
This also add a note to address #116
Got it, thanks for clarification. It's not fair to blame this on the documentation necessarily - I had barreled ahead without realizing the distinction between the line comment and inline comments 😑 . That said, I will take a closer look to see if an extra example in the docs wouldn't hurt. |
No problem, I've added the documentation now in #117. Take a look at https://272-240151150-gh.circle-artifacts.com/0/html/using/syntax.html#comments |
Describe the bug
Adding a line comment (starting with
%
) introduces a newline in the html output.To Reproduce
Using docs at hand:
docs/examples/wealth_dynamics_md.md
cd docs && make html
Expected behavior
Line comments would have no affect at all on the output text.
Screenshots
N/A
Environment (please complete the following information):
Additional context
N/A
The text was updated successfully, but these errors were encountered: