From: Kyle <kyle@posteo.net>
To: help-guix@gnu.org, zimoun <zimon.toutoune@gmail.com>,
Gottfried <gottfried@posteo.de>
Subject: Re: how can I find the terminal output
Date: Mon, 09 May 2022 11:42:20 +0000 [thread overview]
Message-ID: <01ADBEFD-827A-457E-84DF-173DC00F03DD@posteo.net> (raw)
In-Reply-To: <86h7619wnv.fsf@gmail.com>
I have never used the command script, but I thought you might benefit from installing the tldr utility: whose name is short for "too long didn't read" It gives examples instead of all the unwanted details that man pages throw at you first even though they don't make a lick of sense without the right background knowledge and perspective. There are many implementations, but I like tealdeer.
guix install tealdeer
Then type:
tldr script
That produces a few examples for me.
On May 7, 2022 11:42:28 AM EDT, zimoun <zimon.toutoune@gmail.com> wrote:
>Hi,
>
>On Fri, 06 May 2022 at 20:18, Gottfried <gottfried@posteo.de> wrote:
>
>> How do I have to use "script"?
>
>Only you can answer. ;-) The question is: what is your needs? Do you
>need to record and track the output for each command?
>
>Personally, I only do that for the very rare cases when I am demoing.
>Otherwise, I only redirect the output of a command to a file using ’>’.
>
>
>> Do I have to enter "script" in the terminal before I start other
>> commands, so that it will start to log my shell?
>
>Yes.
>
>> or can I, after a command with output, enter "script" and it will log my
>> output in a file typescript?
>
>No.
>
>However, you can redo the same command to append the output to a
>previous ’typescript’. For instance, in your terminal:
>
> ls
> script
> ls
> exit
> pwd
> script -a
> cd /tmp/
> ls
> pwd
> exit
>
>Then the file ’typescript’ contains the session (input and output)
>between ’script’ and ’exit’ (included). Therefore, the first ’pwd’ will
>be not recorded.
>
>
>
>> 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?
>
>Well, have you read the manpage of ’script’? Type ’man script’.
>
>
>Hope that helps,
>simon
>
next prev parent reply other threads:[~2022-05-09 12:36 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
2022-05-07 15:42 ` zimoun
2022-05-09 11:42 ` Kyle [this message]
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=01ADBEFD-827A-457E-84DF-173DC00F03DD@posteo.net \
--to=kyle@posteo.net \
--cc=gottfried@posteo.de \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).