Show HN: Wut – a CLI that explains the output of your last command with an LLM

Re:Show HN: Wut – a CLI that explains the output of your las... by jshobrook on Sunday January 05, 2025 @12:24AM (#42599970)

Unfortunately, I don't see a way around it. There's no other way to capture the output buffer.

[ Parent | on HN ]

Re:Show HN: Wut – a CLI that explains the output of your las... by jas39 on Friday January 10, 2025 @02:23PM (#42659052)

Of course there is; tmux does it. Try redirecting the file descriptor so that you can capture stdout. For bash, something like: 'exec > >(tee -a "$LOG_FILE") 2>&1'.

This could be injected in .bashrc, and activated by default or by a bash function. The >(...) syntax is called process substitution.

[ Parent | on HN ]