-
Notifications
You must be signed in to change notification settings - Fork 6
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Lacking vim documentation #7
Comments
I'm open to adding native vim docs, but haven't had a chance to do it myself. Pull requests are welcome. :^) |
Ok, I see. I don't have the time to do it myself, though (sorry). However, I think @junegunn has written a parser to turn markup files to vim docs. See vim-easy-align for an example. |
Such a parser would be mighty handy, but I don't see that he's yet published it as a project. Or I'm missing it. |
Neither have I. I remember there was a discussion about it in an issue for Perhaps he would be willing to share it? Best 2014-08-01 18:16 GMT+02:00 Reed Esau notifications@github.com:
|
Actually I do have one, but sorry I don't think it's ever going to be ready for public release. It's just a collection of fragile, horrible hacks that is only supposed to work with my documents. |
A horrible hack would be my approach as well. I checked to see if pandoc had support for vimdoc markup. No such luck. |
Relevant to this task: https://github.com/FooSoft/md2vim |
Oh, nice. Thanks for sharing. |
I propose that you add a vim documentation, even if it is only a parsed version of the README file.
The text was updated successfully, but these errors were encountered: