Skip to content
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

Closed
inkarkat opened this issue Apr 3, 2012 · 6 comments
Closed

Publish stable version to vim.org #2

inkarkat opened this issue Apr 3, 2012 · 6 comments

Comments

@inkarkat
Copy link

inkarkat commented Apr 3, 2012

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.)

@mattn
Copy link
Owner

mattn commented Apr 3, 2012

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.
Most easy way is picking up some functions which gist-vim used and include gist#http#get or something others.

@inkarkat
Copy link
Author

inkarkat commented Apr 3, 2012

I know the problem. For my own plugins [1], I use a prefix (e.g. autoload/ingobuffer.vim) for such common, experimental functionality, and I include those scripts with the plugin. There are some issues with versioning and older plugins overriding newer libraries, but I haven't received any complaints so far.

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

@mattn
Copy link
Owner

mattn commented Apr 9, 2012

I just changed namespace of webapi-vim. I'm ready in release it.

bootleq added a commit to bootleq/vim-ref-bingzh that referenced this issue Apr 11, 2012
Ref mattn/webapi-vim#2
mattn/webapi-vim#2

Not compatible with older webapi-vim.
@mattn
Copy link
Owner

mattn commented Apr 15, 2012

@mattn mattn closed this as completed Apr 15, 2012
@inkarkat
Copy link
Author

ありがとう! 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?!

@mattn
Copy link
Owner

mattn commented Apr 16, 2012

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.
I'm sleepy... zzzz

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants