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.

Sign up for GitHub

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

Jump to bottom

Argument -n in force-level1-csd not working properly #80

Closed
davidfrantz opened this issue Apr 12, 2021 · 1 comment · Fixed by #82
Closed

Argument -n in force-level1-csd not working properly #80

davidfrantz opened this issue Apr 12, 2021 · 1 comment · Fixed by #82
Assignees
@ernstste
Labels
help wanted Extra attention is needed unexpected behaviour This shouldn't happen, but is not a bug, the user probably did something unexpected

Comments

@davidfrantz
Copy link
Owner

Issue as discussed by @corneliussenf and others in #77_

The option -n in force-level1-csd does not work as expected when used as 1st argument.

As @ernstste suggested, there are currently two ways to work around this:

  • do not use -n as first argument, but after other arguments
  • use the long option --no-act instead

Unfortunately, we do not have any clue why this happens.
Help wanted!
We are using the getopt utility for this, see https://github.com/davidfrantz/force/blob/develop/bash/force-level1-csd.sh

Best,
David
@davidfrantz davidfrantz added help wanted Extra attention is needed unexpected behaviour This shouldn't happen, but is not a bug, the user probably did something unexpected labels Apr 12, 2021
@ernstste ernstste self-assigned this Apr 14, 2021
@ernstste ernstste mentioned this issue Apr 14, 2021
Merged
@ernstste ernstste linked a pull request Apr 14, 2021 that will close this issue
Fix error when using -n as first option #82
Merged
@ernstste
Copy link
Collaborator

Fixed in commit 38a04e6

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

@ernstste ernstste

Labels
help wanted Extra attention is needed unexpected behaviour This shouldn't happen, but is not a bug, the user probably did something unexpected
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix error when using -n as first option ernstste/force
2 participants
@ernstste @davidfrantz