-
Notifications
You must be signed in to change notification settings - Fork 63
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
Scope stretching various Code-Blocks #74
Comments
Literate programming is definitely something I want to support with this plugin. It would most likely work by combining all JS code blocks into a single consecutive scope, basically just stripping out the Markdown to leave the JS. I haven't used that style myself, so can you point me to some other tools that already support it? I could add a setting in |
hey, sounds awesome!!! For my latest project where I've been using all of that ... you can have a look at it here Litpro by joystylr is using conventions you could easily parse. Now a ##Section Heading will be the starting point for this file ... until a new compile directive's heading begins. I know there's other literate programming libs out there. I don't really know them, I just found this one to be pretty decent :) (eg: writ) |
"combining all JS code blocks into a single consecutive scope" it's a great feature to be able to validate markdown documentation using Markdown javascript |
Based on what I've learned building this processor, it would be difficult to both extract code blocks individually and combine them as in literate programming. I'm closing this issue, but I'd welcome someone using this plugin as inspiration for building another plugin designed for combining code blocks. If you do build it, please share here! |
I am just finding my love for literate programming.
When coding and documenting heavily though, one thing doesn't work as desired ...
thus I can't use literate programming/markdown properly
I understand this is almost impossible to implement, unless you
However, I'm curious if you have thought about this and if there's a common best practice / workaround
The text was updated successfully, but these errors were encountered: