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

check-for-update: use '!' after shell redirection to force overwrite even if noclobber option is set #2

Merged
merged 1 commit into from Jun 26, 2015

Conversation

Projects
None yet
2 participants
@harningt
Copy link
Contributor

harningt commented Jun 25, 2015

In my setup, i have the noclobber shell option set which prevents destructive shell redirection.

The '!' after > forces it to overwrite, even if noclobber is set.

Without this, every time I launch a shell it attempts to update.

@unixorn

This comment has been minimized.

Copy link
Owner

unixorn commented Jun 26, 2015

Thanks for the contribution. I don't use noclobber so this didn't come up in testing.

unixorn added a commit that referenced this pull request Jun 26, 2015

Merge pull request #2 from harningt/fix-noclobber
check-for-update: use '!' after shell redirection to force overwrite even if noclobber option is set

@unixorn unixorn merged commit 6fdbabc into unixorn:master Jun 26, 2015

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment