Closed trmckay closed 2 years ago
Can we just check for the existance of ~/.zi
instead?
That could work. I'd be happy to draft a PR if this is wanted.
@trmckay please go ahead
We don't check the existance of zi
, but ZPFX
instead. @t4i5uKE can you explain the role of this environment variable?
Maybe my usage of zinit
over zi
is the real issue here. I'm not sure if I completely follow the whole story, but it appears zinit/zi have deleted and revived a few times.
So, if ZPFX is set, there supposed to be a zi
or .zi
directory inside the ZPFX directory?
Hi :wave:
I just noticed this issue. Due to similar issues, I wrapped zi
in a function:
❮▼❯() { zi "$@"; }
which makes zi
available as ❮▼❯
.
Also noticed some confusion, feel free, and also I would appreciate it if mention me to help with zi / zsh
related issues in the future as I am the maintainer of zi
and a user of topgrade
. :octocat:
Thanks,
What did you expect to happen?
ZSH "zi" step should only run if zi is installed, not if the alias
zi
from zoxide is available.What actually happened?
zi
is run, but it fails because it is not the command that the step expects.Additional details
The error occurs here since it is executing the command after sourcing the user's zshrc.
This is tough because for many of the steps, the zshrc needs to be sourced to pick up plugins, but this increases the likelihood of name collisions like this.