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

Correctly interpret options.clobber. #98

Closed
wants to merge 2 commits into from

Conversation

tituomin
Copy link

--no-clobber results in options.clobber being
false.

Fixes #97.

--no-clobber results in options.clobber being
false.

Fixes dthree#97.
@nfischer
Copy link
Collaborator

@tituomin it looks like this breaks a Travis test case. Would you be able to take a look? Default behavior should be clobber = true.

@tituomin
Copy link
Author

tituomin commented Sep 2, 2016

This fixes the problem. However, when testing manually using cash as a command line interpreter, I noticed another bug: it seems that vorpal is a bit confused with the "-n --no-clobber" option specification:

  • "cp -n" results in options.clobber = true (!)
  • "cp --no-clobber" results in options.clobber = false (as expected)

So it seems vorpal equates "n" with "clobber", not with "no-clobber". Unfortunately I don't have time to go into this right now. (Should create an issue in the vorpal repo).

@tituomin tituomin closed this Dec 2, 2020
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

Successfully merging this pull request may close these issues.

cp: --no-clobber and -n do not work
2 participants