On Sat, Dec 22, 2018 at 06:53:24PM -0500, Ted Unangst wrote: > @@ -393,7 +393,7 @@ option is given). > .Ar port > can be a specified as a numeric port number, or as a service name. stray ^ article that can be zapped with this diff while here.
> Ports may be specified in a range of the form > -.Ar nn Ns - Ns Ar mm . > +.Ar nn Ns : Ns Ar mm . If you implement both, you should say so. > -The port range was specified to limit the search to ports 20 \- 30. > +The port range was specified to limit the search to ports 20 : 30. Maybe use "to" here? Reads nicer imho as it's a proper sentence already. > @@ -584,3 +584,9 @@ the > combination could be useful for communications diagnostics. > Note that the amount of UDP traffic generated may be limited either > due to hardware resources and/or configuration settings. > +.Pp > +Previous versions of the > +.Nm nc > +utility used a hyphen to separate port ranges. > +This was changed to a colon to avoid ambiguity with hyphenated service names, > +though the hyphen separator remains supported for backwards compatibility. Do you want to throw out hyphen support eventually?
