Looks nice. Would be way more convenient to use if I could just do `?` in the command line after a failed command. I suppose one could create an alias.
Regarding your README, I would add a text version of the example in the demo.
Regarding your README, I would add a text version of the example in the demo.
At the very least, it’s a wildcard. I think you’re not wrong about setting an alias (I have an alias for `??` to link as `$?`, for example). I just think the single character usage will create conflicts and unexpected outcomes.
Cool tool, OP. I’ve marked it to check out when I’m at my computer at home.
As @alsetmusic already mentioned, I think an alias might be the best way for the moment.
One thing that could be challenging is figuring out how to access the stdout/stderr contents for a program that was previously run. With the current implementation, these pipes are routed to hank although I'm not immediately too sure how one could access this post-execution. Feel free to write or implement any ideas onto the repo!
What luck that I still had this on my to-do list after seeing a couple of posts that coincide with this notion the other day:
https://news.ycombinator.com/item?id=45682219 https://news.ycombinator.com/item?id=45679839
TLDR: capture output for reuse / run commands on output without regenerating it.