4 ms·
No need to use Rosetta: $ file `which vim` /usr/bin/vim: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e]
by saagarjha 6y ago
No need to use Rosetta:
$ file `which vim`
/usr/bin/vim: Mach-O universal binary with 2 architectures: [x86_64:Mach-O 64-bit executable x86_64] [arm64e]
/usr/bin/vim (for architecture x86_64): Mach-O 64-bit executable x86_64
/usr/bin/vim (for architecture arm64e): Mach-O 64-bit executable arm64e
- lmedinas 6y agovim 8.2 included in MacOS is native, neovim is not yet ported :(
- mlindner 6y agoNeoVIM works fine after adding a compilation target. See: https://github.com/neovim/neovim/pull/12624 https://github.com/neovim/neovim/pull/12624 It hasn't been merged yet as some of the dependencies aren't available, one of them apparently being LuaJIT, but if you build it yourself without that it shouldn't be a problem.
- X-Istence 6y agoI install from Homebrew, specifically MacVim. The system version is usually behind on patch levels/plugins that can be loaded.
- mlindner 6y agoGluing yourself at the hip to homebrew is a bad idea IMO. It's trivial to install things yourself. It's just a matter of `./configure && make && make install` and you're done.
- ibraheemdev 6y agoWhy do a `git clone pkg && cd pkg && ./configure && make && make install` instead of just a `brew install`? The whole point of a package manager is to make installations and upgrades easier.
- X-Istence 6y ago"just" Also need to track down and install all of the dependencies, and the dependencies dependencies and all the way down, and figure out the right configure flags to pass, and what environment variables it needs and where it expects to look for header files and the like. Doing all of that from scratch takes hours and hours. Homebrew lets me not worry about that, and instead be productive.
- ant6n 6y agoIt also takes care of updates