Looking at this http://daouzli.com/blog/docstring.html#restructuredtext it mentions that both are supported. The current version is just an abbreviated version which personally I have seen the most through open source projects. We can support your version, but then I definitely want this to be a separate doc standard named sphinx. Make sure to follow the contribution guidelines and provide complete tests.

I can do this as well since I'm fast in doing the tests. If you want to do it yourself I suggest copying over the Google doc standard tests and copying this to: functions-doc-sphinx.vader.

I won't merge unless you have tests and the tests passed ofcourse.

I added the new sphinx format and tests in functions-doc-sphinx.vader as requested.

@vigoux Can you fix all of the above requested changes?

I think i resolved all that you wanted @kkoomen

@vigoux After you've resolved the above issues you only have to add your Sphinx documentation standard to the top of the ftplugin/python.vim file. Then you're done.

I think we are done now @kkoomen !

Thank you for your hard work and your co-operation. I'll release v1.5.0 immediately!

That was great !
I just saw that C is not supported and Rust is a project, i might look into it !

I just saw that C is not supported

If you want to support C and know the ins and outs of the language, go ahead. It's on my list, but haven't made the time to add it. It hasn't been requested yet, but I do want to support it. I suggest you use the Doxygen documentation guidelines since this is the most commonly used doc standard for C.

Use the contribution guidelines since adding a language takes some time. You can use the C++ ftplugin and tests as a base.

Rust is a project, i might look into it !

Once again: if you know the ins and outs of the language along with a doc standard that's widely used, go ahead!

Your contribution has been released as v1.5.0.

Feel free to submit any new issues if you experience any unwanted behaviour in the future. Thanks for your contribution.