d/freebsd-skq
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update SYNOPSIS section to be consistent regarding -u, -i, and -I.

Browse Source 
Apparently, when the -u, -i and -I options where added to sed(1), it was
forgotten to add them to both lines in the SYNOPSIS section. They were only
added to the second line, although they apply to both.

With the updated SYNOPSIS, it is now allowed (and consistent) to run:

sed -i BAK s/foo/bar/g some_file

PR:		240556
Submitted by:	Oliver Fromme
MFC after:	5 days
This commit is contained in:
Benedict Reuschling 2020-05-19 09:17:20 +00:00
parent eda697d2ef
commit 8655a965fd
1 changed files with 6 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

9
usr.bin/sed/sed.1
View File

@ -31,7 +31,7 @@
.\" @(#)sed.1 8.2 (Berkeley) 12/30/93 .\" @(#)sed.1 8.2 (Berkeley) 12/30/93
.\" $FreeBSD$ .\" $FreeBSD$
.\" .\"
.Dd March 27, 2017 .Dd May 19, 2020
.Dt SED 1 .Dt SED 1
.Os .Os
.Sh NAME .Sh NAME
@ -41,9 +41,11 @@
.Nm .Nm
.Op Fl Ealnru .Op Fl Ealnru
.Ar command .Ar command
.Op Fl I Ar extension
.Op Fl i Ar extension
.Op Ar .Op Ar
.Nm .Nm
.Op Fl Ealnr .Op Fl Ealnru
.Op Fl e Ar command .Op Fl e Ar command
.Op Fl f Ar command_file .Op Fl f Ar command_file
.Op Fl I Ar extension .Op Fl I Ar extension
@ -197,7 +199,8 @@ option was specified);
.It .It
a context address a context address
that consists of a regular expression preceded and followed by a that consists of a regular expression preceded and followed by a
delimiter. The closing delimiter can also optionally be followed by the delimiter.
The closing delimiter can also optionally be followed by the
.Dq I .Dq I
character, to indicate that the regular expression is to be matched character, to indicate that the regular expression is to be matched
in a case-insensitive way. in a case-insensitive way.