cm0002@lemmy.world to Programmer Humor@programming.dev · 3 days agoLinux Usersimagemessage-square149linkfedilinkarrow-up11.3Karrow-down124
arrow-up11.28Karrow-down1imageLinux Userscm0002@lemmy.world to Programmer Humor@programming.dev · 3 days agomessage-square149linkfedilink
minus-squareiamdefinitelyoverthirteen@lemmy.worldlinkfedilinkarrow-up44·3 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·3 days agoThere is an option you can set in .zshrc or .bashrc which only includes lines that exit 0 (success)
minus-squareantimidas@sopuli.xyzlinkfedilinkarrow-up5·2 days 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·2 days 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.
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.
Oh, stuff like
git diffandgit logwill end up being omitted pretty often.And a lot of times, the commands that end with piping into
less