-
Notifications
You must be signed in to change notification settings - Fork 279
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
no such file or directory #743
Comments
same issue here |
To anyone reading this answer: The project seems lack of maintaince, althought it runs well for now. You may consider choosing another plugin manager. I am still using Antigen just because it is easy to bundle with oh-my-zsh. SolutionSame issue to me today, and I found a solution: # remove old installation, please check before exec it
#rm -r .antigen .antigen.zsh
# and re-install by git clone
git clone https://github.com/zsh-users/antigen.git ~/.antigen
# add source line to .zshrc. you may edit .zshrc manually
echo 'source ~/.angiten/antigen.zsh' >> ~/.zshrc
# finally, source the new file(or restart your shell),
# and wait for a while for antigen to prepare everything for you!
source ~/.zshrc Detailed ReasonI was confused by the error message at first, until I ran antigen () {
local MATCH MBEGIN MEND
[[ "$ZSH_EVAL_CONTEXT" =~ "toplevel:*" || "$ZSH_EVAL_CONTEXT" =~ "cmdarg:*" ]] && source "/home/name/.antigen/antigen.zsh" && eval antigen $@
return 0
} and I search it in source code, and find something here. The issue seems to be caused by the hard encoded path So my first solution to this issue is modifying the # not perfect solution, edit the .antigen.zsh and delete all old caches
sed -i "s/_ANTIGEN_INSTALL_DIR\/antigen.zsh/_ANTIGEN_INSTALL_DIR\/.antigen.zsh/g" .antigen.zsh
antigen reset but this solution is not perfect too, some commands such like Finally, when I am wandering in the repo, I find a file named |
Hi |
When trying to run any antigen command:
installed antigen using the curl command and have this in ~/.zshrc ->
source ~/.antigen.zsh
The text was updated successfully, but these errors were encountered: