-
Notifications
You must be signed in to change notification settings - Fork 16
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
Turn off pygments feature? #41
Comments
That's correct, there's no easy way to disable pygments, this gem basically uses the github markdown pipeline and I'm not planning on customizing it to allow swapping out of the various pipelines. You can fork the gem of course, you'll probably want to just pull out this line If you want to submit a PR complete with tests allowing the various pipelines to be switched out then I'd be open to merging that in. Also, I think you should close this issue -> vimwiki/vimwiki#1205 as I'm assuming the fix I gave you on this issue that you raised #39 fixed your issue (you never responded so I can't tell) |
Thanks. And vimwiki/vimwiki#1205 is still a problem. I tried your markdown code, it didn't work. I'll post there shortly. |
I could do a fork, but I have no earthly idea how to write tests with vim. |
The tests would be in I do not have time to write this feature, nor is it a priority (or really direction) I want to take this gem in. Therefore I am going to close this issue. If you want to submit a PR with tests with the feature you want then I will be open to merging it. |
Commenting out that line didn't work. I'm just going to process the output file post hoc. Can't waste any more time on this. |
I'm going to use js for syntax highlighting. There's no easy way to disable pygments?
The text was updated successfully, but these errors were encountered: