Fix error with zsh when NOCLOBBER is enabled #734
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
According to the zsh documentation, NOCLOBBER prevents you from accidentally overwriting an existing file: % setopt noclobber % cat /dev/null >~/.zshrc zsh: file exists: /u/pfalstad/.zshrc Since the temporary file was just created, we can just append to it, and noclobber does not need to be disabled.
|
|
dirk-thomas
added a commit
that referenced
this pull request
Apr 21, 2015
Fix error with zsh when NOCLOBBER is enabled
|
Thanks for the patch. |
|
Thanks for the quick review and merge 👍 |
cwecht
pushed a commit
to cwecht/catkin
that referenced
this pull request
Mar 20, 2018
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The following option is available in zsh:
(cf. zsh documentation)
This option is not enabled by default, but when it is, sourcing
setup.[z]shfails with:This is caused by this line.
>>could be used instead since the file was just created and is empty. That way,noclobberdoes not need to be disabled, and zsh users with these crazy options are happy.