Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feature request: -U to unbury entire last command #70

Open
ibarland opened this issue Dec 18, 2024 · 1 comment
Open

feature request: -U to unbury entire last command #70

ibarland opened this issue Dec 18, 2024 · 1 comment

Comments

@ibarland
Copy link

When using rip with wildcards, it'd be nice to have a way to unbury the entire last invocation of rip.

(I realize this'd mean an extra field "invocation-id" kept in .record, since even the millisecond timestamp may not work when somebody is calling rip from a script. …though I guess just a single sentinel-character at the start of lines that were part of the most recent invocation would be fine too, if you're willing to frequently re-over-write the tail of the file.)

——
Btw, thanks for the awesome product! I'd previously been using my own dumb little shell-script to get this affect, but it suffered from multiple flaws, one of which in particular kept annoying me. I heard about rip/rip2 on a reddit thread a couple days ago.

@MilesCranmer
Copy link
Owner

Good idea. I think the implementation sounds right too. Not sure the right long version though: --unbury-all seems like it would suggest unburying the entire graveyard.

This would be a breaking change due to the extra field; maybe we can make a function to automatically update the .record if needed (just assuming all lines have unique invocation-id or something). But probably a bit complex to start tracking that code around.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants