Clarify the behavior of -S further in lam(1).
Seems that "lam file1 -S sep file2" does not carry the -S over past file2, even though you can also write "lam file1 file2 -[sS] sep" to give a separator string after the last file. Ride previous date bump.
This commit is contained in:
parent
c1cf0b4d59
commit
8cdbe2f01a
|
@ -1,4 +1,4 @@
|
|||
.\" $NetBSD: lam.1,v 1.13 2020/10/26 03:51:54 dholland Exp $
|
||||
.\" $NetBSD: lam.1,v 1.14 2020/10/26 04:09:32 dholland Exp $
|
||||
.\"
|
||||
.\" Copyright (c) 1993
|
||||
.\" The Regents of the University of California. All rights reserved.
|
||||
|
@ -89,6 +89,8 @@ Print
|
|||
.Ar sepstring
|
||||
before printing line fragments from the next file.
|
||||
This option may appear after the last file.
|
||||
(A capitalized version appearing before the last file is not carried
|
||||
over past the last file.)
|
||||
.It Fl t Ar c
|
||||
The input line terminator is
|
||||
.Ar c
|
||||
|
|
Loading…
Reference in New Issue