-
Notifications
You must be signed in to change notification settings - Fork 8
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
Feature: Support ix.io ? #13
Comments
Hello @jakejohns, Indeed, updating the let g:sprunge_providers = "sprunge,ix,etc" If you've a better idea feel free to share it. |
that sounds reasonable. Looping until it finds one seems a like it'll be a bit of performance hit waiting for the last one if it's the only one up. But bumping the preferred/functioning one to the front of the list is no different than designating a single one, and will be more resilient. noting here also that sprunge.vim:84 needs to be updated for ix.io highlighting: if g:sprunge_open_browser | call sprunge#OpenBrowser(l:url . '/' . &filetype) | endif
" ^ "/" instead of "?" Although I think you can post the file type as well, and just get the url back with it. |
it could be both @jakejohns, by default it could use let g:sprunge_providers = "sprunge,ix,etc" But users could configure let g:sprunge_providers = "ix" Or let g:sprunge_cmd = 'curl -s -F "f:1=<-" http://ix.io' If they only want to use a single or custom service, still not sure about highlighting, probably will end writing a wrapper function to modify the generated url before calling |
Hello @jakejohns I've added an initial implementation of the suggested feature, it's working on my side, but feel free to comment any issue. |
Cool! I'll check it out. Thanks! |
sprunge is down rupa/sprunge#35
ix.io is quite similar rupa/sprunge#10
@rupa seems frustrated with the hosting situation for sprunge.
Maybe this could possibly support http://ix.io as well?
from reddit
.... I guess it kinnda already does with:
However, there are other fancy features, and the syntax highlight is not a query in ix.io.
The text was updated successfully, but these errors were encountered: