Add --blocks, --bytes, and --lines long options for -b, -c, and -n respectively. This improves tail(1)'s compatibility with its GNU counterpart in a straightforward way.
Details
Details
Diff Detail
Diff Detail
- Repository
- rS FreeBSD src repository - subversion
- Lint
Lint Skipped - Unit
Tests Skipped - Build Status
Buildable 14688
Event Timeline
| tail/tail.c | ||
|---|---|---|
| 67 | don't forget to update usage too | |
| tail/tail.1 | ||
|---|---|---|
| 76 | For what it's worth, I copied this convention from grep(1), so I wasn't trying to go completely off the reservation. We should probably make a pass and address a lot of this so we're consistent. | |
| tail/tail.c | ||
| 67 | I didn't update usage because we don't tend to document long option alternatives to existing flags, from what I can tell. I use both sed and grep here as examples. | |
| tail/tail.1 | ||
|---|---|---|
| 76 | If we're taking a poll, I'm used to `.Fl -blocks``` for long options. | |
Comment Actions
Switch to Fl -longopt instead of Fl Fl longopt; the former looks cleaner and is a much nicer convention
I've still left these out of usage for the time being, because I'm still not entirely sure it needs updated- I'm still (slightly) searching for an example where we actually document the long option alternative to a short option in usage. Everything I've found so far never documents both in usage, and it prefers the short option when possible.