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
vimplugins: update.py supports GitHub Access tokens; add completion-nvim, completion-treesitter #91656
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
so last time I merged a neovim plugin for lsp, there were some complaints that we shouldn't package for an unreleased software. nvim 0.5 is still a few months away but works quite well already so I still believe it's fine to merge.
513f320
to
31938c7
Compare
I've rebased this and also made I think there are more than a few people using neovim 0.5, particularly for the features that these plugins revolve around. It certainly wouldn't be the first unstable thing packaged in nixpkgs, and at least one of them has a tagged release. Hopefully this can be merged. Thanks for considering/reviewing! |
pkgs/misc/vim-plugins/generated.nix
Outdated
pname = "completion-nvim"; | ||
version = "2020-07-05"; | ||
src = fetchFromGitHub { | ||
owner = "haorenW1025"; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
a few plugins recently moved under the org "nvim-lua" so htis is the new home
while at it would you mind packaging https://github.com/nvim-lua/lsp-status.nvim |
@teto Sure, I've redone the PR with Also, I was able to use |
this iteration isn't ready for merging, btw. |
Looks like I had missed another dependency of completion-treesitter. @teto your requested plugin breaks my system config (it looks like maybe vimplugins tests that vim can startup properly?) When I point at this commit, it works. Maybe you can file an issue/pr on I'm going to back out the |
85c4cde
to
05396f7
Compare
pkgs/misc/vim-plugins/update.py
Outdated
@@ -71,6 +70,15 @@ def f_retry(*args: Any, **kwargs: Any) -> Any: | |||
|
|||
return deco_retry | |||
|
|||
def mkreq(url: str) -> urllib.request.Request: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
def mkreq(url: str) -> urllib.request.Request: | |
def makeRequest(url: str) -> urllib.request.Request: |
pkgs/misc/vim-plugins/update.py
Outdated
urllib.request.urlopen( | ||
self.url(f"blob/{self.branch}/.gitmodules"), timeout=10 | ||
).close() | ||
req = mkreq(self.url(f"blob/{self.branch}/.gitmodules")) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
req = mkreq(self.url(f"blob/{self.branch}/.gitmodules")) | |
req = makeRequest(self.url(f"blob/{self.branch}/.gitmodules")) |
Should the token be made a requirement? I mean without it, one does run into request limits quite fast, so it is not really usable. |
@Mic92 I don't know. I didn't want to make a "breaking change" if i I didn't have to. It does update with |
Any chance you can update I tried to update a few plugins but I was also blocked by #91339 |
I don't think so, sorry. I've already churned this PR once for a change I wound up having to back out. I'd really like to see this merged so we can unblock everyone. |
No problems, I'll try to put up a follow up PR. |
Let's merge this 👍 Thanks for your work! |
This still doesn't work for me. I have set up a
|
Unless I made some other coding error, "No route to host" is a very different error condition than an HTTP 429. |
Agreed. Sounds like a local network issue. |
I don't think I have any network issues, it would be nice if someone else could try and see if this works for them. |
I just ran it https://asciinema.org/a/mFnijt0sBehQyxZWUeRKb2Iu2 (and rotated the access token). |
Wow, that really works for you! Thanks for that. Any chance you could try and make the same changes I made to It's really late in my timezone but I promise to post what happens on my end tomorrow first thing. I wish this worked for me too... |
Sure, let's move the conversation over to your PR. Maybe a new issue would be best if you (or anyone) winds up finding something wrong with the update script. |
Motivation for this change
Update vimplugins and add:
Things done
sandbox
innix.conf
on non-NixOS linux)nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
./result/bin/
)nix path-info -S
before and after)