I've found that I can really never use sw stash pop, because I'm never sure that something won't go wrong (e.g. the printer somehow doesn't work) that wouldn't cause me to need to view the same protocol again. So instead I only use peek, and end up with the stash being filled with protocols I've already done.
The pop command is really meant to communicate that, "I'm doing this protocol now, no need to show it in the stash anymore". I think a better/safer way to achieve this is to have pop hide the protocol rather than delete it. After being popped, the protocol would keep its id and could still be referenced by commands like peek and pop, it just wouldn't be displayed by default.
Some related changes:
Add a restore command. This is basically the inverse of pop.
Add a purge command. This would actually delete any "popped" protocols, and reset the id numbering.
Add an --all option to stash list, to show include the popped protocols.
kalekundert
commented
4 years ago
I've found that I can really never use
sw stash pop, because I'm never sure that something won't go wrong (e.g. the printer somehow doesn't work) that wouldn't cause me to need to view the same protocol again. So instead I only use peek, and end up with the stash being filled with protocols I've already done.The
popcommand is really meant to communicate that, "I'm doing this protocol now, no need to show it in the stash anymore". I think a better/safer way to achieve this is to havepophide the protocol rather than delete it. After being popped, the protocol would keep its id and could still be referenced by commands like peek and pop, it just wouldn't be displayed by default.Some related changes:
restorecommand. This is basically the inverse of pop.purgecommand. This would actually delete any "popped" protocols, and reset the id numbering.--alloption tostash list, to show include the popped protocols.