Update SYNOPSIS section to be consistent regarding -u, -i, and -I.
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:
parent
eda697d2ef
commit
8655a965fd
@ -31,7 +31,7 @@
|
||||
.\" @(#)sed.1 8.2 (Berkeley) 12/30/93
|
||||
.\" $FreeBSD$
|
||||
.\"
|
||||
.Dd March 27, 2017
|
||||
.Dd May 19, 2020
|
||||
.Dt SED 1
|
||||
.Os
|
||||
.Sh NAME
|
||||
@ -41,9 +41,11 @@
|
||||
.Nm
|
||||
.Op Fl Ealnru
|
||||
.Ar command
|
||||
.Op Fl I Ar extension
|
||||
.Op Fl i Ar extension
|
||||
.Op Ar
|
||||
.Nm
|
||||
.Op Fl Ealnr
|
||||
.Op Fl Ealnru
|
||||
.Op Fl e Ar command
|
||||
.Op Fl f Ar command_file
|
||||
.Op Fl I Ar extension
|
||||
@ -197,7 +199,8 @@ option was specified);
|
||||
.It
|
||||
a context address
|
||||
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
|
||||
character, to indicate that the regular expression is to be matched
|
||||
in a case-insensitive way.
|
||||
|
Loading…
Reference in New Issue
Block a user