You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I had lots of problems trying to edit a text in markdown about Git, using filetype=pandoc and syntax on. After some research, I've found that the problem is related to the @ char appearing in some contexts. For example, opening the following minimal example with MacVim causes the segfault:
Commit `HEAD@{yesterday}` is one day before current head.
The problem was solved by commenting out the lines which define regexps for pandocPCite (lines 130 to 137) in syntax/pandoc.vim file.
Although I discovered the culprit and solved the issue (at least for me, since I don't need the PCite syntax), I still don't understand why this could cause a segfault, and why only with MacVim version (other vim versions I tried had no problem).
The text was updated successfully, but these errors were encountered:
It is not only for MacVim but for GVim in Debian (wheezy). Maybe because I'm using self compiled version of Vim (not the one comes from package manager)?
I had lots of problems trying to edit a text in markdown about Git, using
filetype=pandoc
andsyntax on
. After some research, I've found that the problem is related to the@
char appearing in some contexts. For example, opening the following minimal example with MacVim causes the segfault:The problem was solved by commenting out the lines which define regexps for
pandocPCite
(lines 130 to 137) insyntax/pandoc.vim
file.Although I discovered the culprit and solved the issue (at least for me, since I don't need the PCite syntax), I still don't understand why this could cause a segfault, and why only with MacVim version (other vim versions I tried had no problem).
The text was updated successfully, but these errors were encountered: