feat: add <!-- panvimdoc-only content --> support #48
Conversation
|
That is a neat feature! Can we change the name to |
|
I was thinking of making another PR to augment the existing "include" function, since as written, the Where as if we used a comment it would be invisible, you could have something like Obviously I have not written that yet, or looked at how complex it would be to do -- though I guess it should be the same as the current include, just matching on another block type? Would that influence what name you'd want to give this and the other theoretical PR? Happy to make whatever change you prefer of course, |
rktjmp
force-pushed
the
panvimdoc-only-comments
branch
2 times, most recently
from
793ca80
to
d3ceb43
Compare
The inverse of `<!-- panvimdoc-ignore-start/end -->`, where the content is only visible in the vimdoc output. Because we have no control on the mardown renderer, all content must be embedded in the comment, instead of using a start and end marker.
rktjmp
force-pushed
the
panvimdoc-only-comments
branch
from
d3ceb43
to
497a1ff
Compare
|
Interesting PR idea! That PR would be welcome. I believe you can reuse some of the machinery for the existing include functionality.
These seem good to me. I'm open to suggestions as well! Alternatively, |
|
I think I like |
The inverse of
<!-- panvimdoc-ignore-start/end -->, where the content is only visible in the vimdoc output. Because we have no control on the mardown renderer, all content must be embedded in the comment, compared to using a start and end marker.The test is written expecting #47 to be merged.