Hacker News
macOS No Longer Ships with Emacs
lazystar
|next
[-]
badc0ffee
|next
|previous
[-]
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
|root
|parent
[-]
I got hit by this so often and never knew the reason. At least I know who's to blame now.
dwaite
|root
|parent
[-]
explicitly using vim (rather than the vi alias) is supposed to give the return code behavior you prefer.
code_martial
|next
|previous
[-]
ethansinjin
|next
|previous
[-]
edit: found this previous HN discussion: https://news.ycombinator.com/item?id=20102640
duskwuff
|root
|parent
|next
[-]
[1]: https://support.apple.com/guide/security/signed-system-volum...
dwaite
|root
|parent
|previous
[-]
So it is possible Apple's lawyers read this section as meaning an injunction against GPLv3 code may be infeasible to solve with licensing the patent, and instead require Apple to make changes on a time-table they would not be happy with.
Sticking to GPLv2 lets Apple control the time table it has taken to license, reimplement or remove components which had moved to GPLv3.
I can't tell you why it took them until El Capitan to remove the Emacs install though.
tdy_err
|next
|previous
[-]
olivierestsage
|next
|previous
[-]
cozzyd
|next
|previous
[-]
dessimus
|root
|parent
[-]
thunderfork
|previous
[-]
Probably makes sense not to ship an old version by default anymore, though.