From: Martin Steigerwald <martin@lichtvoll.de>
To: Karel Zak <kzak@redhat.com>
Cc: util-linux@vger.kernel.org,
"Rick van Rein" <rick@openfortress.nl>,
"Asbjørn Sloth Tønnesen" <asbjorn@asbjorn.st>
Subject: Re: script(1) plans
Date: Mon, 18 Mar 2019 22:10:29 +0100 [thread overview]
Message-ID: <2845909.CbUA7ZE4ZZ@merkaba> (raw)
In-Reply-To: <20190318125322.4obb27vwtxfuwuie@ws.net.home>
Hi Karel.
Karel Zak - 18.03.19, 13:53:
> I'd like to improve script(1) to be more flexible and support more
> streams. The current version allow to log only output, but I'd like to
> add possibility to log input, signals and more details about the
> session.
>
> The idea is to introduce a new timing file format; and use it in case
> a new features are requested by user on script(1) command line. The
> new format will be still based on text and easy to convert to the old
> version.
[…]
> The target release will be probably v2.35 and I'm going to start work
> on it ASAP (probably this or next week).
>
> Comments & objections?
Epic. I am no expert regarding what would be good for "script" command,
but I love the ideas you share here. They extend the possibilities of
what can be done with the command quite a bit.
Seems finally time to include the script command somewhere in my Linux
training slides. Like "watch", which I often show to participants I
still have no slide for it. About time, I'd say.
THanks,
--
Martin
next prev parent reply other threads:[~2019-03-18 21:16 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-18 12:53 script(1) plans Karel Zak
2019-03-18 21:10 ` Martin Steigerwald [this message]
2019-03-19 7:30 ` Fabian.Kirsch
2019-03-19 7:53 ` Rick van Rein
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=2845909.CbUA7ZE4ZZ@merkaba \
--to=martin@lichtvoll.de \
--cc=asbjorn@asbjorn.st \
--cc=kzak@redhat.com \
--cc=rick@openfortress.nl \
--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).