From: "Michael Kerrisk (man-pages)" <mtk.manpages@gmail.com>
To: mtk.manpages@gmail.com, Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org
Subject: [PATCH 2/3] Manual pages: scriptlive.1: Miscellaneous wording, grammar, and formatting fixes
Date: Wed, 15 Jul 2020 10:15:45 +0200 [thread overview]
Message-ID: <20200715081546.112933-2-mtk.manpages@gmail.com> (raw)
In-Reply-To: <20200715081546.112933-1-mtk.manpages@gmail.com>
Nothing too contentious here, I think, so I'm rolling all
of the edits into one patch.
Signed-off-by: Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>
---
term-utils/scriptlive.1 | 19 +++++++++++++------
1 file changed, 13 insertions(+), 6 deletions(-)
diff --git a/term-utils/scriptlive.1 b/term-utils/scriptlive.1
index 236868b8f..fd553ad01 100644
--- a/term-utils/scriptlive.1
+++ b/term-utils/scriptlive.1
@@ -9,17 +9,23 @@ scriptlive \- re-run session typescripts, using timing information
.RB [ \-I|\-B ]
.I typescript
.SH DESCRIPTION
-This program re-run a typescript, using stdin typescript and timing information to ensure that
+This program re-runs a typescript,
+using stdin typescript and timing information to ensure that
input happens in the same rhythm as it originally appeared when the script
was recorded.
.PP
-The \fBsession is executed\fR in newly created pseudo terminal with user's $SHELL
+The \fBsession is executed\fR in a newly created pseudoterminal with
+the user's $SHELL
(or defaults to /bin/bash).
.PP
.B Be careful!
Do not forget that the typescript may contains arbitrary commands.
It is recommended to use \fB"scriptreplay \-\-stream in \-\-log\-in typescript"\fR
-(or with --log-io instead of --log-in) to verify the typescript before it is executed by
+(or with
+.B \-\-log\-io
+instead of
+.BR \-\-log\-in\)
+to verify the typescript before it is executed by
.BR scriptlive (1).
.PP
The timing information is what
@@ -47,17 +53,18 @@ File containing \fBscript\fR's timing output. This option overrides old-style a
.BR \-T , " \-\-log\-timing " \fIfile\fR
Aliased to \fB\-t\fR, maintained for compatibility with
.BR script (1)
-command line options.
+command-line options.
+.TP
.BR \-d , " \-\-divisor " \fInumber\fR
Speed up the replay displaying this
.I number
-of times. The argument is a floating point number. It's called divisor
+of times. The argument is a floating-point number. It's called divisor
because it divides the timings by this factor. This option overrides old-style arguments.
.TP
.BR \-m , " \-\-maxdelay " \fInumber\fR
Set the maximum delay between updates to
.I number
-of seconds. The argument is a floating point number. This can be used to
+of seconds. The argument is a floating-point number. This can be used to
avoid long pauses in the typescript replay.
.TP
.BR \-V , " \-\-version"
--
2.26.2
next prev parent reply other threads:[~2020-07-15 8:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-15 8:15 [PATCH 1/3] Manual pages: script.1: Miscellaneous wording, grammar, and formatting fixes Michael Kerrisk (man-pages)
2020-07-15 8:15 ` Michael Kerrisk (man-pages) [this message]
2020-07-15 8:15 ` [PATCH 3/3] Manual pages: scriptreplay.1: " Michael Kerrisk (man-pages)
2020-07-20 8:36 ` [PATCH 1/3] Manual pages: script.1: " Karel Zak
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200715081546.112933-2-mtk.manpages@gmail.com \
--to=mtk.manpages@gmail.com \
--cc=kzak@redhat.com \
--cc=util-linux@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).