You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Let it be out in the open, self-promotion is a byproduct of this suggestion.
Hi, I have undertaken a holy quest to convince people to use the CLI/Linux/FOSS. In service to that quest, I have created tuterm. It's a bash program that allows you to write a transcript of commands. When you run tuterm, those commands are automatically reproduced as if a human were typing them. The user is then expected to repeat the commands.
I would love to cooperate with this repo in turning the README into a tuterm tutorial. We could also create an asciicast tutorial an put it as a gif inside the README itself, which would make it more attractive.
Using tuterm has the following benefits:
100% repeatable
The users don't have to set up an environment/directory for testing the commands themselves (this is something that irritated me when I was a beginner)
User input is error-checked before running so there is no room for mistakes
The project (tuterm) is still young, so there may be bugs.
Looking forward to your reply!
The text was updated successfully, but these errors were encountered:
Note: Let it be out in the open, self-promotion is a byproduct of this suggestion.
Hi, I have undertaken a holy quest to convince people to use the CLI/Linux/FOSS. In service to that quest, I have created tuterm. It's a bash program that allows you to write a transcript of commands. When you run tuterm, those commands are automatically reproduced as if a human were typing them. The user is then expected to repeat the commands.
I would love to cooperate with this repo in turning the README into a tuterm tutorial. We could also create an asciicast tutorial an put it as a gif inside the README itself, which would make it more attractive.
Using tuterm has the following benefits:
The project (tuterm) is still young, so there may be bugs.
Looking forward to your reply!
The text was updated successfully, but these errors were encountered: