cm0002@lemmy.world to Programmer Humor@programming.dev · 2 months agoLinux Userslemmy.mlexternal-linkmessage-square64fedilinkarrow-up197arrow-down15
arrow-up192arrow-down1external-linkLinux Userslemmy.mlcm0002@lemmy.world to Programmer Humor@programming.dev · 2 months agomessage-square64fedilink
minus-squareiamdefinitelyoverthirteen@lemmy.worldlinkfedilinkarrow-up3·2 months ago…until you press up one too many times and enter the same command but with a typo. Again.
minus-squarelayzerjeyt@lemmy.dbzer0.comlinkfedilinkarrow-up0·2 months agoThere is an option you can set in .zshrc or .bashrc which only includes lines that exit 0 (success)
minus-squareantimidas@sopuli.xyzlinkfedilinkarrow-up1·2 months agoInfuriatingly that would omit things like unit test runners from the history in case they don’t pass. As a developer I tend to re-run failed commands quite often, not sure how widely that applies, though.
…until you press up one too many times and enter the same command but with a typo. Again.
Been there, done that.
There is an option you can set in .zshrc or .bashrc which only includes lines that exit 0 (success)
Infuriatingly that would omit things like unit test runners from the history in case they don’t pass. As a developer I tend to re-run failed commands quite often, not sure how widely that applies, though.