You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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.
When using
rip
with wildcards, it'd be nice to have a way to unbury the entire last invocation ofrip
.(I realize this'd mean an extra field "invocation-id" kept in
.record
, since even the millisecond timestamp may not work when somebody is callingrip
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.The text was updated successfully, but these errors were encountered: