From: Gottfried <gottfried@posteo.de>
To: Tobias Geerinckx-Rice <me@tobias.gr>, help-guix@gnu.org
Subject: Re: how can I find the terminal output
Date: Fri, 6 May 2022 20:18:40 +0000 [thread overview]
Message-ID: <72a9c190-6917-6aea-98b7-cd7668c85d9c@posteo.de> (raw)
In-Reply-To: <A65BBB86-C5AD-44EA-80F1-C7DAE789A516@tobias.gr>
[-- Attachment #1.1.1: Type: text/plain, Size: 943 bytes --]
Hello,
Don't mind if I am asking simple questions because I have to learn the
basics.
How do I have to use "script"?
Do I have to enter "script" in the terminal before I start other
commands, so that it will start to log my shell?
or can I, after a command with output, enter "script" and it will log my
output in a file typescript?
I tried several times, but it didn't work. It didn't record anything,
when I opened the file typescript.
So can you show me an example how to use it?
What Options are useful?
Gottfried
Am 02.05.22 um 14:53 schrieb Tobias Geerinckx-Rice:
> Gottfried,
>
> script(1) is the classic way to log your shell (or any) session to a text file.
>
> See <https://www.man7.org/linux/man-pages/man1/script.1.html>.
>
> There's more fancy stuff like asciinema but that seems like overkill here.
>
> Kind regards,
>
> T G-R
>
> Sent on the go. Excuse or enjoy my brevity.
[-- Attachment #1.1.2: OpenPGP public key --]
[-- Type: application/pgp-keys, Size: 3191 bytes --]
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 840 bytes --]
next prev parent reply other threads:[~2022-05-06 20:19 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 20:15 how can I find the terminal output Gottfried
2022-04-30 9:06 ` zimoun
2022-04-30 18:07 ` Gottfried
2022-05-02 8:54 ` zimoun
2022-05-02 12:53 ` Tobias Geerinckx-Rice
2022-05-06 20:18 ` Gottfried [this message]
2022-05-07 15:42 ` zimoun
2022-05-09 11:42 ` Kyle
2022-05-09 16:21 ` Gottfried
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=72a9c190-6917-6aea-98b7-cd7668c85d9c@posteo.de \
--to=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=me@tobias.gr \
/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 read-only IMAP folder(s) and NNTP newsgroup(s).