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

Commandline parsing should be as order-agnostic as reasonably possible #70

Open
bradenbest opened this issue May 26, 2024 · 1 comment · May be fixed by #71
Open

Commandline parsing should be as order-agnostic as reasonably possible #70

bradenbest opened this issue May 26, 2024 · 1 comment · May be fixed by #71

Comments

@bradenbest
Copy link

hexedit filename -l 16 is not valid and results in a usage exit, but hexedit -l 16 filename is valid. I can see in the manpage and usage printout as well that the program expects the filename to come last, and it doesn't have to be this way.

I'll see if I can't fix these issues myself. I'd frankly like to rewrite the whole arg parser loop (no disrespect), but let's address one thing at a time.
@bradenbest bradenbest linked a pull request May 26, 2024 that will close this issue
Open
@bradenbest
Copy link
Author

I'd frankly like to rewrite the whole arg parser loop

I ended up doing exactly that. If you decide to merge #71 it should automatically close this issue 👍

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.

1.7 - Better arg parsing bradenbest/hexedit
1 participant
@bradenbest