4 ms·
I still use the ancient bash on macOS. And the jq that happens to be there, which I think was new in macOS 26? (WWDC hinted it would be in macOS 15, but IIRC it
by badc0ffee 8mo ago
I still use the ancient bash on macOS. And the jq that happens to be there, which I think was new in macOS 26? (WWDC hinted it would be in macOS 15, but IIRC it wasn't)
I honestly had no idea that emacs ever shipped with it.
This is probably as good a place as any to ask: why does the macOS vi return a nonzero exit code when I make any error at all? Like if I search for text that doesn't exist in the file, or mistype at the : prompt, and then (successfully) save and quit, it returns 1. This is bad when I'm using it as the editor for something like git commit, which will fail if $EDITOR returns nonzero. No other vi/vim seems to behave this way.
- nwellnhof 8mo ago> This is bad when I'm using it as the editor for something like git commit, which will fail if $EDITOR returns nonzero. I got hit by this so often and never knew the reason. At least I know who's to blame now.
- dwaite 8mo agohttps://stackoverflow.com/questions/66283714/how-can-i-force-vi-vim-to-exit-cleanly-with-status-0#answer-69735583 https://stackoverflow.com/questions/66283714/how-can-i-force... explicitly using vim (rather than the vi alias) is supposed to give the return code behavior you prefer.
- badc0ffee 8mo agoThank you! That actually explains everything.