MarkdownEditing
MarkdownEditing copied to clipboard
SublimeText-Markdown
Adding Pandoc support
I think many Markdown users use Pandoc as a backend nowadays.
So it would be nice to provide a separate syntax file for Pandoc's extras.
The pandoc branch in my fork is has an initial draft for such a file
https://github.com/bordaigorl/sublime-markdown-editing/tree/pandoc
if there is some interest we could coordinate to make it fully featured.
There has been an interest on Pandoc markdown. If you are willing to work on this, then it is OK for me. In the end, I can merge it to master. Personally I can't put time on this since I'm not familiar with pandoc and don't have much time. But still I'll try to help.
Some notes:
- I see that
Markdown (Pandoc).tmLanguagecomes in one commit. When forking a file, as a git best practice you should do it in 2 steps. One for just duplicating file and one for making your edits. So we can see what is changed. - Consider putting unrelated edits into different commits. So we can git-cherrypick some of them to main syntax file when applicable.
- You can maintain another branch for improvements to main plugin. So you can cherriypick some commits from pandoc branch to that branch. Looking at your
Markdown (Pandoc).tmLanguage, I see some improvements that can be applied to main syntax file.
Thanks
Excellent points. I'll see if I can amend the history.
About the improvements to the main branch, I already started some branches for that, see #169.
I and maliayas are both not familiar with pandoc. bordaigorl seems to have done some work but never finished.
@hadim my fork adds some support for the Pandoc syntax I use but it does not cover all the extensions.
@bordaigorl whenever you think your fork is ready for merge, you can open a pull request and we will have a look.
@RoyiAvital there is already a limited support if you write like this: $x_i + y_i = 5$.