fix for upstream issue #177 #178
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
About the other interesting folding issue I mentioned in #177:
I had broken folding when code blocks were too long (more than 150 lines). I found that it had nothing to do with vim pandoc plugin itself but rather with vim's syntax sync feature. To fight with this I added in my .vimrc following line
and folding got fixed. In theory this setting says that vim must sync at least 500 lines around current cursor position upon loading a buffer (to be more exact when it applies file type pandoc to a buffer) and should make loading time longer, but I did not notice any discomfort. After loading a buffer this setting does not affect anything.
So probably it makes sense to mention this trick somewhere in docs?