-
Notifications
You must be signed in to change notification settings - Fork 0
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
UPSTREAM Management #3
Comments
Hi @wzrdtales - came across your repo from a comment here: https://www.growingwiththeweb.com/2018/01/slow-nvm-init.html, which admittedly is a bit dated. I have a "loadnvm" solution that's less than optimal right now and was poking around to see if there are any better solutions at this point. Is your fork still reasonably operable since it's been a while since you've updated |
Yes, I am actively using my fork, with no problems at all. So it is maintained in the demand: I use it and around 50 fellow engineers and may be some other people from the internet. I rarely watch upstream, since it is really just working perfectly fine, but if you're stumbling into problems solved in upstream I will take care to get them or also accept PRs of course. |
The upstream reference is btw in this branch : https://github.com/wzrdtales/nvm-ng/tree/hard-line |
And to add as a comment: Performance wise it still is in the same means superior as documented here already #2 and I would definitely notice since I am working solely in a tiling shell and nowhere else (neovim user). Just make sure to make use the fast-reuse flag to get the complete optimization. |
Whenever you feel, upstream has notable changes, hit me up here and reference it and I will go ahead picking it up.
The text was updated successfully, but these errors were encountered: