-
Notifications
You must be signed in to change notification settings - Fork 31
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
Fixes and improvements #382
base: master
Are you sure you want to change the base?
Conversation
The CI failures don't look like they were introduced by this PR |
Looks good, thanks for tracking this down, must have been a nightmare. |
Yeah, it was tedious and unpleasant in a lot of ways. Maybe the worst part was learning about how Linux IO works on a low level and how fundamentally broken it actually is. About the second commit with the error messages, it is far from complete (it mainly contains a few sprinkled annotations that were required for me to track down the bug). I suggest merging it as-is, and strongly encouraging adding more |
This comment was marked as resolved.
This comment was marked as resolved.
friendly ping |
@andrewchambers Any chance you could take a look another look at this? |
Partially fixes andrewchambers#367
Although the examples already disambiguate this, this hopefully makes it more clear that the command is not a single argument which may need to be escaped, but a list of arguments which will be executred
The letter conflicts with --exclude, which would be much better suited for a shorthand. Unlike --exclude, --exec is only used up to once, less often, and is shorter. I didn't directly add -e back as a shorthand for --exclude, as I'm not 100% sure yet if we'd want that.
Closes andrewchambers#389. Also implements a duplicates check, therefore fixes andrewchambers#396.
Closes #378