-
Notifications
You must be signed in to change notification settings - Fork 202
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
docs: Add troubleshooting Help for M1 Macs #140
base: master
Are you sure you want to change the base?
docs: Add troubleshooting Help for M1 Macs #140
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I like the idea of the page, so let's make some group effort to get all the correct information in it.
Lunarvim does not support M1 mac natively. This can be fixed by installing | ||
homebrew and neovim through the x86_64 architecture platfomr location | ||
`/usr/local`. Doing so will run neovim and homebrew through the x86_64 | ||
architecture. This only works provided you have Rosetta installed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just got it confirmed on discord that you can have a native mac-o
installation of Neovim through macports, so this not completely accurate.
Lunarvim does not support M1 mac natively. This can be fixed by installing | |
homebrew and neovim through the x86_64 architecture platfomr location | |
`/usr/local`. Doing so will run neovim and homebrew through the x86_64 | |
architecture. This only works provided you have Rosetta installed. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ok, do you mind detailing here how those individuals did that? I tried mostly everything I could to install brew
and neovim
and its dependencies through /opt/homebrew
but it always led to the issue linked above.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I just used macports which installed neovim as a native M1 application without any tweaks.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would suggest these changes. Otherwise it looks good to me.
No idea if it works though since I dont have a mac and therefore cant test it.
``` | ||
|
||
Lunarvim does not support M1 mac natively. This can be fixed by installing | ||
homebrew and neovim through the x86_64 architecture platfomr location |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
homebrew and neovim through the x86_64 architecture platfomr location | |
homebrew and neovim through the x86_64 architecture platform location |
Fix typo
@@ -72,3 +72,19 @@ If they are then you are using the syntax prior to [LunarVim#1813](https://githu | |||
-- this is the correct syntax since 3dd60bd | |||
vim.list_extend(lvim.lsp.override, { "jsonls" }) | |||
``` | |||
|
|||
## Running LunarVim on M1 mac reports error `mach-o, but wrong architecture` |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
## Running LunarVim on M1 mac reports error `mach-o, but wrong architecture` | |
## Errors with `mach-o` on startup |
Sounds better considering the headers of the other troubleshoot helps
This PR address the issue raised in this issue LunarVim/LunarVim#809