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
ConqueTerm is broken #35
Comments
Not good. There's not much the scraper can do -- it tries to duplicate upstream exactly. Is it easy to fork it and fix it? If you use vim-update-bundles, you can tell it to check out a previous revision. Assuming 2.1 works...
I've had to do this quite a bit to work around broken script releases. |
If you check http://www.vim.org/scripts/script.php?script_id=2771, you will find out that they actually made a second not broken 2.2 release. I guess that vim-updates-bundle only check version to decide to update instead of checking version and date. |
Ah, got it. You're right: if upstream doesn't change the version number, the scraper thinks it already has that version. Downloading every package each time the scraper runs is not an option. Thankfully not many authors do that. I'll force an update. |
How hard would it be to make the scraper also check the release dates ? |
In the next week or two I hope to answer that question... revamping the way the script database is kept. Some comments saying the same thing as this issue (just for the record): |
There's also vim-scripts/Conque-Shell#1 vim-scripts dropped the ball big on this one. |
There are two pull requests for this plugin now - and many +1's over there. |
Last release (2.2) of http://www.vim.org/scripts/script.php?script_id=2771 was broken so https://github.com/vim-scripts/Conque-Shell is also broken.
The text was updated successfully, but these errors were encountered: