-
-
Notifications
You must be signed in to change notification settings - Fork 61
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
Publish stable version to vim.org #2
Comments
webapi-vim was experimental project. however it have been used for many other vim-scripts. I'm thinking about this issue. But I couldn't get answer yet. |
I know the problem. For my own plugins [1], I use a prefix (e.g. If I think the library is useful on its own, or may be reused by others (and therefore must be properly tested and documented, too), I release it separately on vim.org, and instruct users to download the dependency. But this only works well when there are few such dependencies, or hunting them down becomes a hassle. Other plugins have something similar (e.g. FuzzyFinder uses a library called l9). [1] http://vim.sourceforge.net/account/profile.php?user_id=9713 |
I just changed namespace of webapi-vim. I'm ready in release it. |
Ref mattn/webapi-vim#2 mattn/webapi-vim#2 Not compatible with older webapi-vim.
ありがとう! Works fine together with the updated gist.vim! PS: Did you update this in the middle of the night, or aren't you currently in your native time zone?! |
No. Now is 9:00AM in japan. |
As gist.vim now requires webapi.vim, a stable version of webapi.vim should be published to vim.org. Not everyone is using a Vim package manager, and not everyone (including me) is keen on consuming potentially unstable latest bits from GitHub. By publishing stable releases on vim.org (and referencing those as a gist.vim dependency, including the version number needed), you allow people to consume gist.vim and its dependencies solely from vim.org.
PS: I also would suggest putting all webapi autoload scripts into a
webapi
subdirectory, as the module names are quite generic ("json", "html"), so there's a high likelihood of clashes with other plugins. (Or even separate versions of them; you seem to have copied some scripts from other authors.)The text was updated successfully, but these errors were encountered: