-
-
Notifications
You must be signed in to change notification settings - Fork 1.5k
pr: Doesn't allow for omitted optional argument to -n
#3109
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
Labels
Comments
I'm unable to reproduce this issue using Rust 1.58 on Archlinux. |
Hm, same here.
|
Nvm, the issue went away since I last tested :) |
Nevermind, it seems to only happen with certain filenames, e.g., |
Yes, now I'm able to reproduce it. |
tertsdiepraam
added a commit
to tertsdiepraam/coreutils
that referenced
this issue
Feb 23, 2022
tertsdiepraam
added a commit
to tertsdiepraam/coreutils
that referenced
this issue
Feb 23, 2022
tertsdiepraam
added a commit
to tertsdiepraam/coreutils
that referenced
this issue
Feb 24, 2022
tertsdiepraam
added a commit
to tertsdiepraam/coreutils
that referenced
this issue
Feb 26, 2022
sylvestre
pushed a commit
that referenced
this issue
Mar 5, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Test case:
The POSIX manpages specifies that the arguments to
-n
are to directly follow this option, as far as I can see, i.e.,-n1
would be allowed, while-n 1
would be seen as "number lines, input file '1'". That's how GNU handles it as well.The text was updated successfully, but these errors were encountered: