![]() I now know that /opt/homebrew/bin/wget is what I should use in my script.Īs I said, this is using wget, the same process can be used to investigate where vim is. Homebrew links the files relative to their install, so if we used the full path we wouldn't have caught. Notice I've used *Cellar/wget/1.16.3/bin/wget as the lname and not the full path. GUI for vim, made for macOS License: Vim Formula JSON API: /api/formula/macvim.json Formula code: macvim. ![]() I can now use find to search for where homebrew symlinked wget: $>find / -lname *Cellar/wget/1.16.3/bin/wget So for me, wget was installed into /opt/homebrew/Cellar/wget/1.16.3/bin/wget You can see the most recent version marked with an asterisk (*). First let’s find out which python vim is actually using. opt/homebrew/Cellar/wget/1.14 (8 files, 716K) brew rm vim macvim python brew install python brew install vim -override-system-vi brew install macvim -override-system-vim sudo brew linkapps macvim That fixed the issue, but let’s actually see why it fixed the issue. Since I haven't installed vim using homebrew, let me show you an example using wget: $>brew info wget You should find the newly installed vim in the bin directory under the homebrew prefix: echo `brew -prefix`/bin/vimĬertainly brew info vim will tell you what cellar brew installed vim into.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |