-
-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
split -1 in
should be accepted
#5170
Conversation
GNU testsuite comparison:
|
a few comments:
|
In the issue I wrote that it should behave like |
I see ... So, basically - instead of trying to handle it all with clap::Arg , strip out the "obsolete" arguments like this one and handle it separately. Will do that. |
GNU testsuite comparison:
|
Yes, that's the best approach we found so far, but if you find a better way do let us know!
|
GNU testsuite comparison:
|
This one actually shows as FAIL in gnu-full-result.json artifact from the last GnuTests action run for this PR. |
should be all done, except some weird issue with GnuTests regression on tests/tail-2/inotify-dir-recreate ... see my other comment #5170 (comment) |
Clean up the parsing of the attributes to preserve. There are several improvements here: Preserve now uses `max` from Ord, the `max` method is now called `union` and does not mutate, the parse loop is extracted into a new function `parse_iter`, the `all` and `none` methods are replaced with const values. Finally all fields of Attributes are now public.
* Extract uucore::line_ending::LineEnding Aims to provide consistent newline/zero terminator handling. * Apply suggestions from code review Co-authored-by: Terts Diepraam <terts.diepraam@gmail.com> * cargo fmt * Use uucore::line_ending::LineEnding * Remove uucore::line_ending::LineEnding::Space * Rename LineEnding::from_zero_flag * Replace LineEnding::None with Option<LineEnding> * cargo clippy * assert_eq * cargo clippy * cargo clippy * uucore/line_ending: add more documentation --------- Co-authored-by: Terts Diepraam <terts.diepraam@gmail.com>
* fix issue 5149 * fix clippy style issue * fix spell issue * address comment * address comments * fix cspell
* Remove the author copyright notices Rational: * not maintained * does not reflect reality * don't provide any value (the info can be found in the git log) * we don't have rules to update them (ex: should you update it after one line, two lines, etc) Co-authored-by: Daniel Hofstetter <daniel.hofstetter@42dh.com>
rebased to main, looks like GnuTests are passing now |
as noted in issue #5033: |
It looks like the GNU
split -1 in
behaves assplit -l 1 in
, i.e. a shorthand for-l
or--lines
Having that, here is my take on it - using similar approach to what is done in
fold
fixes #5033