[src/trunk]: src/usr.bin/lam Clarify the behavior of -S further in lam(1).

[dholland <dholland%NetBSD.org@localhost>]

details:   https://anonhg.NetBSD.org/src/rev/b6ea6b3b755f
branches:  trunk
changeset: 945328:b6ea6b3b755f
user:      dholland <dholland%NetBSD.org@localhost>
date:      Mon Oct 26 04:09:32 2020 +0000

description:
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.

diffstat:

 usr.bin/lam/lam.1 |  4 +++-
 1 files changed, 3 insertions(+), 1 deletions(-)

diffs (18 lines):

diff -r 8d738d35064d -r b6ea6b3b755f usr.bin/lam/lam.1
--- a/usr.bin/lam/lam.1 Mon Oct 26 03:51:54 2020 +0000
+++ b/usr.bin/lam/lam.1 Mon Oct 26 04:09:32 2020 +0000
@@ -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 @@
 .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