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

argbash-init fails with unhelpful error message if no parameters passed #130

Closed
felipecrs opened this issue Aug 3, 2020 · 1 comment · Fixed by #136
Closed

argbash-init fails with unhelpful error message if no parameters passed #130

felipecrs opened this issue Aug 3, 2020 · 1 comment · Fixed by #136

Comments

@felipecrs
Copy link
Contributor

image
@matejak
Copy link
Owner

matejak commented Sep 19, 2020

This is argbash-init puzzled when the output filename is an empty string, which the entrypoint script may serve to argbash-init.

matejak added a commit that referenced this issue Sep 19, 2020
@matejak
argbash-init is able to handle empty string as the only argument
ab1bec5 
It treats it as if it was given a dash.

Fixes: #130)
matejak added a commit that referenced this issue Sep 19, 2020
@matejak
argbash-init is able to handle empty string as the only argument
b30ed5c 
It treats it as if it was given a dash.

Fixes: #130
@matejak matejak mentioned this issue Sep 19, 2020
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

argbash-init is able to handle empty string as the only argument matejak/argbash
2 participants
@matejak @felipecrs