wow, our brains work differently, how can you smile in that circumstance? :) It's a terrible idea of fish not to save errors in history (even if the way bash d

wow, our brains work differently, how can you smile in that circumstance? :) It's a terrible idea of fish not to save errors in history (even if the way bash does it is not optimal, ignoring/obliterating the error return fact) because running a command to look up the state of something can easily return the state you are checking along with an error code. "What was that awesome three letter TLD I looked up yesterday that was available? damn, not a valid domain is an error code" and just like that SEX.COM slips through your grasp, and your only recourse would be to hijack it. but it's compoundedly worse to feel like the problem is solved by autocorrect further polluting your history. I would not want to be fixing things downstream of you, where you would be perfectly happy downstream of me.