Replies: 13 comments 8 replies
-
I did set the path to nvim using
|
Beta Was this translation helpful? Give feedback.
-
It's not ideal, but check this out #1859, there are several solutions there, but we need to come up with a better fix. |
Beta Was this translation helpful? Give feedback.
-
I read through the whole thread and the only hint is related to the system PATH. On my system (macOS Sonoma on M1), I have installed nvim with brew. Thus
Isn't the 3rd item a bug? And unfortunately it's not clear what the solution is. |
Beta Was this translation helpful? Give feedback.
-
An update: I've learned that the issue of starting Neovide 0.11.2 in macOS might actually have nothing to do with the M1 or Intel versions. I have installed Neovide using brew on an Intel macOS running 13.5.2 and the behavior is identical. This make me believe that the path might be a red herring and the root cause is somewhere else (lack of permission? etc) |
Beta Was this translation helpful? Give feedback.
-
There are a few of issues with workarounds |
Beta Was this translation helpful? Give feedback.
-
From #1373:
|
Beta Was this translation helpful? Give feedback.
-
#1479 and #1998 seem to be about the app not being signed issue. I went through the dance of right clicking, etc. |
Beta Was this translation helpful? Give feedback.
-
I put together a quick AppleScript:
Output:
Next I changed it to:
The output this time:
It looks to me that Neovide it expecting a specific kind of output and it fails to parse it.
|
Beta Was this translation helpful? Give feedback.
-
I have removed the other
|
Beta Was this translation helpful? Give feedback.
-
I can confirm that after removing my .bash_profile, Neovide app could start. It has been impossible to figure out what’s breaking Neovide though. Even the first line of my bash_profile stty -ixon would already break it. |
Beta Was this translation helpful? Give feedback.
-
The good news for me is that I got to a point where Neovide starts from the app on one of my machines. The less good news is that I haven't been able to pinpoint the issue and that means others might hit the same problem and 1) there's no clear workaround for it; 2) there's no way to make neovide's start more resilient. |
Beta Was this translation helpful? Give feedback.
-
I was wondering why you have so much stuff in your IMO, the correct approach is to follow the advice there and add if [ -r ~/.bashrc ]; then
source ~/.bashrc
fi to your And then at the top of the # If not running interactively, don't do anything
[[ $- != *i* ]] && return This way you can separate the stuff you want to run on all shells, like setting paths to This in itself won't help you pinpoint the issue, but if you only have paths (and perhaps aliases) in In |
Beta Was this translation helpful? Give feedback.
-
@al3xandru if you are able to test then #2083, should include better error messages. It ill probably be merged to main soonish, after someone has reviewed it. |
Beta Was this translation helpful? Give feedback.
-
I have installed Neovide on macOS Sonoma on a MBP M1. Starting the app by double-clicking doesn't do anything. But it does start when using
neovide
from the Terminal.I looked in Console for any error messages but I couldn't find much. Anyone knows why this is happening and how I could fix it?
thank you
Beta Was this translation helpful? Give feedback.
All reactions