I dream of applications that expose sufficient metadata about their outputs such that the OS can know if rerunning is necessary without me needing to specify.
I wish this worked without prefixing the commands with "once". Especially if I ran a command with verbose output and afterwards decided I wanted to grep something from it. Terminals have the output in their scrollback buffer and maybe it's just a matter of writing an "output" command that lets me run:
$ cmake ..
$ output | grep "libssl version"I've always wanted to deal with cache invalidation in my terminal.
> The typical use case: reading secrets from 1Password without approving every single read with your fingerprint.
Uh I dont know about that one chief.
I just use tmux buffers
But I'm not running agents, I have different needs
This looks awesome. Thanks for making this.
Been using this, for similar cli output catching. https://github.com/dimo414/bkt
Wondering what you think about the two, and what are the good reasons to use one vs the other? (Maybe: once is more actively developed? bkt hasn't been active for a year).
Seems well-designed, but what’s the use case? I’m trying to think of them but my creativity is failing me.
Do you have CLI calls that you want to cache? Here you go!
Congratulations. What is Word Error Rate? We have a few use cases for something like that at newcare.app
[flagged]
These kinds of tools are very useful. I have my own called memo (which is just a shell script: https://github.com/aktau/dotfiles/blob/master/bin/memo).
It was discussed in https://news.ycombinator.com/item?id=45670052 and others chimed in with their own (like bkt(1) and up(1)).
The main differences I see: