Conversation
|
MD reminds me of MySQL in that respect: a billion different slightly incompatible forks ;-) |
README.md
Outdated
|
|
||
| You set it up like this: | ||
|
|
||
| % skip: next |
There was a problem hiding this comment.
Maybe just % skip: start to cut out the noise and move it down as you get things working?
There was a problem hiding this comment.
I tried that but it didn't work either.
There was a problem hiding this comment.
Did you remove the % skip: next? I found a bug where a %skip: start followed by a % skip: next disables the % skip: start. I think that nesting should raise an exception so working on that.
I believe everyone just uses HTML comments: https://github.github.com/gfm/#example-648 – so the answer is no. |
Co-authored-by: Chris Withers <chris@withers.org>
Yay! Consistency! I guess skip and other single line comment things on MyST also need to be expressable as: |
Yeah, this would be the best. I've solved it using: <!--
; skip: next
-->But <!-- skip: next -->would obviously be much nicer. |
|
Big success, thank you! |
|
@hynek - so I'm chipping away at things from the Sybil side, I'm actually hoping to "officially" support GH flavoured markdown at some point, and I'd like you ask for your review on that PR if that's okay? In the meantime, it looks like you're actually using MyST for the docs, can I just check that this commenting pattern works properly on MyST? |
|
What PR do you mean? This one has been merged and Sybil doesn't have a PR that looks related. I'm using |
|
This PR ;-) |
Continuing from #2
So @cjw296 I think this is what you had in mind? It doesn't seem to work and
%also isn't a Markdown thing, but a MyST thing if I'm not wrong (I'm trying to sound constructively helpful, not entitled, sorry if I'm failing I'm still traveling).But I guess I can wrap the % thing in
<!-- -->tho if we can make it work.