-
Notifications
You must be signed in to change notification settings - Fork 22
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
antidote tries to clone local package declarations from github #98
Comments
This is a timely bug report. Thanks for submitting it. I was just working on the 1.7.3 release and had already fixed this issue. I was going to put more features in before cutting a release, but since this is affecting someone right now, I'll push those out to 1.7.4 and publish. This should work now if you run |
Much appreciated. |
This is a follow-up on the fix. The plugins get attached, but it still throws up errors.
Despite the errors, the plugins still work. Not a big issue, since antidote still works, but a bit confusing. |
Thank you for reporting back, and for your patience. Right now, 1.7.3 only supports paths beginning with / or ~. If you replace $ZDOTDIR with ~/path/to/zdotdir does it work properly? I have been using |
My bad, I missed responding to this. It worked with /Users/username/path/to/zdotdir. I did not try it with ~/path/to/zdotdir, but I assume it would've worked fine. I tested 1.7.4 and using the $ZDOTDIR var works great. Thank you again for your work on this as well as your responsiveness. |
- don't try to clone missing local plugins - missing local plugins should still output the expected load script - favor not failing during bundling, but when sourcing the result
The text was updated successfully, but these errors were encountered: