-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Remove clap for echo #7603
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
Merged
Merged
Remove clap for echo #7603
Changes from all commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
ca07881
Parsing echo flags manually without clap as clap introduced various p…
cerdelen 2ead244
fixed error where multiple flags would parse wrong
cerdelen 2f1a9d1
Spelling & formatting fixes
cerdelen c1c127e
docu for EchoFlag struct
cerdelen 79a90fd
Merge branch 'main' into remove_clap_for_echo
cerdelen ab95cf8
more extensive comment/documentation
cerdelen fcca66a
revert POSIXLY_CORRECT check to only check if it is set
cerdelen 5fc2c34
Fixed problem of overwriting flags. Added test for same issue
cerdelen bb16513
cargo fmt
cerdelen 17c6c21
cspell
cerdelen e8c3e42
Update src/uu/echo/src/echo.rs
cerdelen File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There is a subtle change in behavior here:
POSIXLY_CORRECT=<non-utf8-sequence>is now interpreted astrue, whereas before it was interpreted asfalse. I assume this is a correct change. (I can't test GNU easily right now.)Nitpick: If you fix subtleties like this, it would be extra awesome if you also add a test, so that we don't lose it later :)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I suggested that change upthread when I saw this code at the edge of a diff 😅
The following test (in
test_echo.rsinsidemod posixly_correct {}) should do the trick:(I can confirm that this matches GNU, GNU activates POSIX mode regardless of whether the variable's value is
1or0or empty string or\xFF.)There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Awesome! But I would argue that if you change the behavior, then an old test cannot possibly correctly test for the new behavior :D
In particular, this test only tests whether
-eis interpreted or considered as part of the output. It does not test whether escape sequences are interpreted or taken literally, i.e. whether "escape mode" is initially set or not.Like I said, it's not a major thing, and doesn't block this PR.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's not an old test, I meant that was where I'd put it. It fails if
env::var(...).is_ok()is used.