-
-
Notifications
You must be signed in to change notification settings - Fork 39
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
Aliases definitions executed by znap eval
can mess up code later on
#211
Comments
It turns out this is probably because I'm binding
Not sure why though. Feel free to close this issue if you think this is by-design or sort of expected. |
I have the same problem. Switching back to
|
That is indeed the problem. After defining an alias for Try moving |
@marlonrichert the problem still exists though. The workaround I'm using right now is dogin
this way i'm able to using |
I think I figured out a workaround that is otherwise useful, too: Znap could defer all alias definitions until the command line has been loaded. |
znap status
doesn't work when using znap eval
for Zoxideznap eval
can mess up code later on
Describe the bug
When I add this line in my
.zshrc
znap status
gives the following errors:Steps To Reproduce
As mentioned above
Expected behavior
znap status
should be able to list the reposEnvironment:
Additional context
Errors are gone if I switch back to the plain eval
I wonder if this is because the way I'm using
znap eval
is incorrect and that leads to the zoxide not being correctly initialized?The text was updated successfully, but these errors were encountered: