Skip to content
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

Fix documentation for --lines #166

Closed
hoelzro opened this issue Oct 31, 2018 · 2 comments
Closed

Fix documentation for --lines #166

hoelzro opened this issue Oct 31, 2018 · 2 comments
Milestone

Comments

@hoelzro
Copy link

hoelzro commented Oct 31, 2018

The documentation for --lines currently says:

  --lines=NUM                   Only print line(s) NUM of each file.  No
                                pattern is matched.

--lines=NUM implies only a single number may be specified, but line(s) NUM implies one may supply several. Not only is this inconsistent, but it doesn't explain how one would specify multiple lines if they desired.

For reference, you can specify a comma-separated list of expressions, each of which is a single integer line number, or a dash-separated start-end range, which matches all lines between start and end, inclusive.

@hoelzro
Copy link
Author

hoelzro commented Oct 31, 2018

Not really needed if we do #167

@petdance petdance added this to the 3.0.0 milestone May 13, 2019
@petdance
Copy link
Collaborator

The --lines option no longer exists.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants