fix(mv): add -n option, make -f default behavior #328
Merged
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.
This lets
mv()
have-f
as the default behavior (the flag exists for legacy reasons). I introduce the-n
flag, which will allow the opposite behavior. This is the default behavior on Bash.This also introduces a modification to
parseOptions()
, allowing dictionaries to be specified of the following form:The empty string will still cause
no_force
to default to false, as it normally would. Options prefixed with!
have the special meaning that the appearance of that commandline flag sets the option tofalse
instead oftrue
. So passing the-f
flag will causeoptions.no_force
to befalse
.If someone passes in a flag like
-fn
, this will setoptions.no_force = true
, taking whichever is last, which is consistent with most core-utils.-nf
will likewise setoptions.no_force = false
.