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
Errors when including syntax highlighted vim code block in a note #68
Comments
Thanks for the clear bug report. This should now be fixed. Happy Vimming! |
Wow, that was fast, thanks! I was just about to add a comment - I've been able to work around this error by only calling BTW, I know the code's MIT, but would you mind if I pinched this code for a PR for vim-markdown (full credit, of course)? |
I would love to have this feature in Vim's markdown mode but it wasn't high priority enough to ever implement :-] so I would say go for it! I actually have a pull request open for vim-markdown myself (tpope/vim-markdown#9) but it was never merged (my fault), might have to pick that up again soon (I miss it). Edit: Apparently I was talking about a different vim-markdown, but who cares, pinch it wherever you want, it's MIT ;-) |
Yeah, I've been looking at plasticboy's vim-markdown, which seems to have a few more features than the standard one from Mr Pope. Very cool PR, too, with the conceal features, and very interesting discussion, too. Tricky one to get right... I've submitted a PR (preservim/vim-markdown#93) for just the syntax highlighting of code blocks, which makes a very nice addition to the formatting of the doc. I've handled the duplicate running of scripts a little differently, only including the new syntax if it's not already included. Seems to work fine. Thanks for the original code! |
If you create a note and type something like:
the code block is correctly highlighted as vim code. However, if you add a new code block with a different language, e.g.
as soon as you hit escape, you see the following errors:
and the new code block doesn't get syntax highlighting.
The text was updated successfully, but these errors were encountered: