Skip to content
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

Jumping to directories results in error status in fish shell #35

Closed
cole-h opened this issue Mar 16, 2020 · 6 comments
Closed

Jumping to directories results in error status in fish shell #35

cole-h opened this issue Mar 16, 2020 · 6 comments

Comments

@cole-h
Copy link
Contributor

cole-h commented Mar 16, 2020

The recent _ZO_ECHO changes made fish shell return an error status after jumping to any directory (see the below screenshot). This doesn't affect functionality, but is certainly annoying and wrong behavior, considering it didn't behave like this before.

image

(I've verified the issue is unrelated to direnv, to assuage any concerns)

Bisected to:

f4cd1159c5419ece11b1d0147c23dba1c7579edc is the first bad commit
commit f4cd1159c5419ece11b1d0147c23dba1c7579edc
Author: Ajeet D'Souza <98ajeet@gmail.com>
Date:   Sun Mar 15 17:44:23 2020 +0530

    Add $_ZO_ECHO to echo match before navigating

 src/subcommand/init.rs | 26 +++++++++++++++++---------
 1 file changed, 17 insertions(+), 9 deletions(-)

Disclaimer: this may be present in other shells, but I only use fish.

@ajeetdsouza
Copy link
Owner

ajeetdsouza commented Mar 16, 2020

The error happens due to the and [ -n _ZL_ECHO] statement, resulting in an error code when the variable isn't set.

@ajeetdsouza
Copy link
Owner

Fixed in 146e570. Thanks for pointing this out!

@cole-h
Copy link
Contributor Author

cole-h commented Mar 16, 2020

Thanks, works perfectly! Hopefully you cut a new release soon, so those using the Nixpkgs package won't have to deal with that annoying (but cosmetic) issue for much longer... ;)

@ajeetdsouza
Copy link
Owner

There's still a few kinks to iron out with the exit codes, but I'm working on it!

@ajeetdsouza
Copy link
Owner

@cole-h, could you check that the latest commit works as expected for you?

@cole-h
Copy link
Contributor Author

cole-h commented Mar 17, 2020

Works fine for me: still no error status!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants