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
Sparkup itself only needs to know if it should use the XML or HTML dialect. Therefore the --xml and --html options make totally sense.
The Vim invocation of sparkup needs to be fixed (issue Not working with eruby #69).
Also, sparkup.py does not appear to be compatible with Python3, and therefore the shebang (/usr/bin/env python2) should be kept for Linux/Unix systems (just recently introduced in 04cfd22). I will therefore rename sparkup.py to sparkup again, and change the symlinks.
(You have to think about sparkup being used standalone here!)
I am quite sure to have left a comment with issue #69 or its pull request a few days ago, stating that I would fix the filetype issue (but cannot find it anymore).
--xmland--htmloptions make totally sense.The Vim invocation of sparkup needs to be fixed (issue Not working with eruby #69).
/usr/bin/env python2) should be kept for Linux/Unix systems (just recently introduced in 04cfd22).I will therefore rename sparkup.py to sparkup again, and change the symlinks.(You have to think about sparkup being used standalone here!)
I am quite sure to have left a comment with issue #69 or its pull request a few days ago, stating that I would fix the filetype issue (but cannot find it anymore).
I will provide a pull request in an hour or so.