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
fix: don't generate on error if backup file doesn't exists #1057
Conversation
Signed-off-by: JrCs <90z7oey02@sneakemail.com>
Thanks for the PR @JrCs! Are there any open issues reporting this problem? What OS and version are you on? Can you provide the output from |
@JrCs could create a test that reproduces this issue which we can then use to validate that this change is necessary? |
@jthegedus if you call asdf with a bash script that use a |
Thanks for sharing, asdf is not yet compatible with |
@JrCs , do you know why that happens? |
@Stratus3D i use also |
@JrCs can you share a little more about how you invoked asdf after setting |
@Stratus3D easy: do a |
Hmm... I am unable to reproduce this issue on OSX using Zsh:
Both commands succeed without any issues with this fix. This is not a big deal to me, as I'd eventually like to move to having |
Signed-off-by: JrCs 90z7oey02@sneakemail.com
Summary
If the replacement (sed) is not done the backup file isn't create and the rm command return on error.
With
rm -f
no error is generated even if the file doesn't exists.