-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
Stty: implemented hex and octal parsing for rows and columns #9516
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
|
I'd mentioned here do this in an utility file and re-use it in all the places we should parse such integers |
6df507e to
0e13402
Compare
|
Good idea, I added a helper in the parser folder to be able to reuse that logic |
|
GNU testsuite comparison: |
0e13402 to
7179ded
Compare
|
GNU testsuite comparison: |
2094e6a to
9da9baa
Compare
|
GNU testsuite comparison: |
|
GNU testsuite comparison: |
0a2c101 to
432d123
Compare
CodSpeed Performance ReportMerging #9516 will not alter performanceComparing Summary
Footnotes
|
|
GNU testsuite comparison: |
|
The benchmark change is unrelated, should be good for another round of reviews |
432d123 to
a42b3e4
Compare
|
GNU testsuite comparison: |
1 similar comment
|
GNU testsuite comparison: |
65f25c2 to
9f7d01a
Compare
|
GNU testsuite comparison: |
3 out of the 5 stty GNU tests are now passing and was taking a look at why the stty-row-col test was now failing. The issue was that the row and column options are able to accept hex and oct values and the parser we were using did not support the parsing of those values. This change makes the stty-row-col tests now pass.
I have modified the parser helper function and added tests that compare the output of the uutils implementation to the gnu implementation.