-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
stty: columns env support and integration testing #9490
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
base: main
Are you sure you want to change the base?
Conversation
Do the same as GNU stty when it has to prints the parameter, doing proper text wrapping
3e6051f to
96937d3
Compare
CodSpeed Performance ReportMerging #9490 will not alter performanceComparing Summary
Footnotes
|
|
GNU testsuite comparison: |
53628a6 to
bf1f813
Compare
|
GNU testsuite comparison: |
bf1f813 to
0ed9bf5
Compare
0ed9bf5 to
c3e31fd
Compare
|
GNU testsuite comparison: |
|
Am so glad that we now have the integ tests running on the CI for this binary, it spotted a bunch of stuff. |
|
GNU testsuite comparison: |
|
Moved the libc to a helper function with comments and added some comments to the main wrapped printer class |
|
The only errors are coming from this PR: #9471 |
This PR takes the commit from @3v1n0 to split it from the rest of his PR to add the feature of reading from the COLUMNS variable to determine how long the lines are in the output. This is because the changes in that PR related to the flags are separate and it might be a while until some upstream changes related to that change are merged.
I added tests that cover that when printing, ideally once we expect the output of the --all command to be matching we should be able to add GNU matching testing to the COLUMNS tests. These integ tests match how the GNU integ tests validate that this env variable is working properly
#9432 this is the PR where the COLUMNS support is added from
When reviewing this, an important thing to note is that the COLUMNS environment variable is only used when piping output.