How to log every input and output and write to file in Bash?
I am often on assignment and sometimes I forget to document my work.
E.g. write down output from different one-off tools.
Is there a way to automate that via .bashrc
?
So I open up a new shell, it automatically creates a new log file (like day-month-year-#
) and dumps everything in there. Also, it'd be great if I could actually see the output in the window.
Also: a lot of the output is colorized, is it possible to preserve that?
PS: disk space is not an issue ;)
linux command-line bash shell command-history
add a comment |
I am often on assignment and sometimes I forget to document my work.
E.g. write down output from different one-off tools.
Is there a way to automate that via .bashrc
?
So I open up a new shell, it automatically creates a new log file (like day-month-year-#
) and dumps everything in there. Also, it'd be great if I could actually see the output in the window.
Also: a lot of the output is colorized, is it possible to preserve that?
PS: disk space is not an issue ;)
linux command-line bash shell command-history
2
To save all terminal commands and output, in color, by runningscript
.
– John1024
Jul 20 '16 at 20:40
add a comment |
I am often on assignment and sometimes I forget to document my work.
E.g. write down output from different one-off tools.
Is there a way to automate that via .bashrc
?
So I open up a new shell, it automatically creates a new log file (like day-month-year-#
) and dumps everything in there. Also, it'd be great if I could actually see the output in the window.
Also: a lot of the output is colorized, is it possible to preserve that?
PS: disk space is not an issue ;)
linux command-line bash shell command-history
I am often on assignment and sometimes I forget to document my work.
E.g. write down output from different one-off tools.
Is there a way to automate that via .bashrc
?
So I open up a new shell, it automatically creates a new log file (like day-month-year-#
) and dumps everything in there. Also, it'd be great if I could actually see the output in the window.
Also: a lot of the output is colorized, is it possible to preserve that?
PS: disk space is not an issue ;)
linux command-line bash shell command-history
linux command-line bash shell command-history
edited Feb 22 at 14:31
kenorb
11.5k1580116
11.5k1580116
asked Jul 20 '16 at 20:31
simplex123simplex123
364
364
2
To save all terminal commands and output, in color, by runningscript
.
– John1024
Jul 20 '16 at 20:40
add a comment |
2
To save all terminal commands and output, in color, by runningscript
.
– John1024
Jul 20 '16 at 20:40
2
2
To save all terminal commands and output, in color, by running
script
.– John1024
Jul 20 '16 at 20:40
To save all terminal commands and output, in color, by running
script
.– John1024
Jul 20 '16 at 20:40
add a comment |
1 Answer
1
active
oldest
votes
If .bash_history
is not what you want, you can use asciinema
utility, a free and open source solution for recording terminal sessions.
You can integrate it to start each time when you start your session and record all inputs and outputs, then save it into the file.
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1103299%2fhow-to-log-every-input-and-output-and-write-to-file-in-bash%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
If .bash_history
is not what you want, you can use asciinema
utility, a free and open source solution for recording terminal sessions.
You can integrate it to start each time when you start your session and record all inputs and outputs, then save it into the file.
add a comment |
If .bash_history
is not what you want, you can use asciinema
utility, a free and open source solution for recording terminal sessions.
You can integrate it to start each time when you start your session and record all inputs and outputs, then save it into the file.
add a comment |
If .bash_history
is not what you want, you can use asciinema
utility, a free and open source solution for recording terminal sessions.
You can integrate it to start each time when you start your session and record all inputs and outputs, then save it into the file.
If .bash_history
is not what you want, you can use asciinema
utility, a free and open source solution for recording terminal sessions.
You can integrate it to start each time when you start your session and record all inputs and outputs, then save it into the file.
answered Feb 22 at 14:34
kenorbkenorb
11.5k1580116
11.5k1580116
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1103299%2fhow-to-log-every-input-and-output-and-write-to-file-in-bash%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
2
To save all terminal commands and output, in color, by running
script
.– John1024
Jul 20 '16 at 20:40