cm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agoLinux Usersimagemessage-square133linkfedilinkarrow-up11.26Karrow-down121cross-posted to: programmerhumor@lemmy.ml
arrow-up11.24Karrow-down1imageLinux Userscm0002@lemmy.world to Programmer Humor@programming.dev · 2 days agomessage-square133linkfedilinkcross-posted to: programmerhumor@lemmy.ml
minus-squareiamdefinitelyoverthirteen@lemmy.worldlinkfedilinkarrow-up42·2 days ago…until you press up one too many times and enter the same command but with a typo. Again.
minus-squarelayzerjeyt@lemmy.dbzer0.comlinkfedilinkarrow-up5·1 day agoThere is an option you can set in .zshrc or .bashrc which only includes lines that exit 0 (success)
minus-squareantimidas@sopuli.xyzlinkfedilinkarrow-up5·1 day 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.
minus-squareulterno@programming.devlinkfedilinkEnglisharrow-up1·21 hours agoOh, stuff like git diff and git log will end up being omitted pretty often. And a lot of times, the commands that end with piping into less
…until you press up one too many times and enter the same command but with a typo. Again.
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.
Oh, stuff like
git diffandgit logwill end up being omitted pretty often.And a lot of times, the commands that end with piping into
lessBeen there, done that.