ruby and python dependence

[dsanson]

Perhaps we should add a check for ruby and python has('ruby') and has('python'), and return an error message saying they are required if either is false. Long term, we might consider separating out the features that have these dependencies, and only making them conditional on has('ruby') and has('python'). Also long term, we might consider which features that currently depend on ruby and python could be rewritten (without too many headaches) in pure vimscript.

This is all very low priority. I'm really not quite sure how to think about these issues. I don't know that anyone will ever use the plugin who doesn't have support for ruby and python, and I'd rather have code that we can all understand written in familiar idioms than cryptic code written in vimscript.

[jonahkagan]

I tried to install vim-pandoc, but was getting fatal errors on startup (specifically, this one). So I tried installing Vim using Macports with Python and Ruby support, and started getting new, non-fatal errors. I finally traced one about "relpath" down to the fact that the default Vim from Macports has Python 2.5, which is not a new enough version (you need >= 2.6). Installing a variant from Macports with Python 2.7 fixed the issues.

I think it would be very helpful to list the dependencies in the README at least, even if you don't catch them automatically. That's generally a standard practice, no?

[rom1v]

I don't know that anyone will ever use the plugin who doesn't have support for ruby and python

Current Debian testing (wheezy) vim does not have support for python.

[dsanson]

I've just pushed some commits that (I think) manage to wrap all the direct calls to python functions in if has('python') tests. So vim-pandoc now (more) gracefully degrades in functionality when vim doesn't have python support. I'm sure there are still lots of ways to make it cough up errors.