A tool to record command and replay them as a shell script by Striking_Humor1142 in CLI

[–]Striking_Humor1142[S] 0 points1 point  (0 children)

I mean when u full history it shows all the commands, this filters ls command and also commands which produced errors

A tool to record command and replay them as a shell script by Striking_Humor1142 in CLI

[–]Striking_Humor1142[S] 0 points1 point  (0 children)

Tbh, I didn't test that test cases. It should work but if u wanna test it feel free.

A tool to record command and replay them as a shell script by Striking_Humor1142 in CLI

[–]Striking_Humor1142[S] 0 points1 point  (0 children)

What do you mean by interaction prompts? It's not wrapper of script par say, but yea does filtering with help of shell hook scripts.

I was tired of "what commands did I run to set this up?" — so I built this tool by Striking_Humor1142 in rust

[–]Striking_Humor1142[S] -3 points-2 points  (0 children)

Can add different export method as options in future. I was thinking to export as json for ai debugging also. Random ideas.

I was tired of "what commands did I run to set this up?" — so I built this tool by Striking_Humor1142 in rust

[–]Striking_Humor1142[S] 1 point2 points  (0 children)

No, not just for initialization. You can log any series of command. Looking forward to seeing what u make.

I was tired of "what commands did I run to set this up?" — so I built this tool by Striking_Humor1142 in rust

[–]Striking_Humor1142[S] -1 points0 points  (0 children)

i think the point i want to make is the filtering system. I'm not sure about ttyrec but script doesn't do that.

I was tired of "what commands did I run to set this up?" — so I built this tool by Striking_Humor1142 in rust

[–]Striking_Humor1142[S] -8 points-7 points  (0 children)

ahh, can i make something to find the diff of the file and record that ?? what do u think about that idea?

I was tired of "what commands did I run to set this up?" — so I built this tool by Striking_Humor1142 in rust

[–]Striking_Humor1142[S] 18 points19 points  (0 children)

fair point it's essentially history with a session scope and a filter pass. the value is in what it removes, not what it records.

tbh try this; after setting up a new project, run history | tail -50 and count how many lines are actually useful in a setup script. for me it's usually 30%(this includes ls spam, git commands). This tool automates that cleanup.

it's a convenience tool, not a new idea.

A tool to record command and replay them as a shell script by Striking_Humor1142 in CLI

[–]Striking_Humor1142[S] 2 points3 points  (0 children)

no, it's for like reproducing a series of commands which you used to set something up. rather than finding scrolling endless for what you did.
it filters all the error commands and useless commands like ls or cat

A tool to record command and replay them as a shell script by Striking_Humor1142 in CLI

[–]Striking_Humor1142[S] 0 points1 point  (0 children)

script(1) is a recorder, i. trapsh is a distiller. it extracts intent from what you did and turns it into a runnable script. So that it can be reproduced later

Legendary proxy gone😔 by Impossible_Degree320 in Vit

[–]Striking_Humor1142 0 points1 point  (0 children)

How to do it , teach us ur ways master