neovide: Does not start on macOS

Neovide does not start on macOS after updating to (today’s commit dd74ff). The window pops up and closes almost immediately, logs shows ERROR Neovide requires nvim version 0.4 or higher while I have 0.6.1

Old version works (from a week ago)

To Reproduce Start nevoid from command line or application

OS: macOS 12.1
Neovide Version 0.8.0
NVIM v0.6.1

LOG TRACE [neovide] Neovide version: 0.8.0 DEBUG [neovide::settings::window_geometry] Loaded window settings: Windowed { position: PhysicalPosition { x: 1280, y: 1080 }, size: Dimensions { width: 106, height: 41 } } TRACE [neovide::renderer::fonts::caching_shaper] Using font_size: 28.00px TRACE [neovide::renderer::fonts::font_loader] Loading font FontKey { bold: false, italic: false, family_name: None } TRACE [neovide::renderer::fonts::caching_shaper] Font width: 17.23px 17.36px TRACE [neovide::renderer::fonts::caching_shaper] Fudge factor: 0.99 TRACE [neovide::renderer::fonts::caching_shaper] Fudged font size: 27.63px TRACE [neovide::renderer::fonts::caching_shaper] Fudged font width: 17.00px TRACE [neovide::renderer::fonts::font_loader] Loading font FontKey { bold: false, italic: false, family_name: None } INFO [neovide::window] window created (scale_factor: 2.0000, font_dimensions: Dimensions { width: 17, height: 35 }) TRACE [neovide::redraw_scheduler] Next frame queued TRACE [neovide::redraw_scheduler] Next frame queued TRACE [neovide::renderer::fonts::caching_shaper] Shaping text: INFO [neovide::bridge::command] Starting neovim with: Command { std: “/bin/zsh” “-lc” “\x1b]1337;RemoteHost=ommited@ommited\x07\x1b]1337;CurrentDir=/Users/ommited\x07\x1b]1337;ShellIntegrationVersion=12;shell=zsh\x07/usr/local/bin/nvim --embed”, kill_on_drop: false } ERROR [neovide::bridge] Neovide requires nvim version 0.4 or higher. Download the latest version here https://github.com/neovim/neovim/wiki/Installing-Neovim

About this issue

Original URL
State: closed
Created 2 years ago
Reactions: 6
Comments: 36 (18 by maintainers)

Most upvoted comments

On a M1 Mac my issue was that neovide did not find my nvim installation in the /opt folder (due to homebrew) so I symlinked nvim ( ln -s /opt/homebrew/bin/nvim /usr/local/bin/nvim ) to not pollute my path and everything works fine now.

owittek on Dec 16, 2022

@jonsmithers worked for me to checkout to db53e94db928946a1df06c88dd68bd80ac443758 Thanks!

Gregory-Bach on Feb 5, 2022

FWIW I did a git bisect to find the commit where neovide no longer starts for me on MacOS, and it’s dd74ff42394ac2f309108ccc0f53674cfaa8525b

# git bisect bad
dd74ff42394ac2f309108ccc0f53674cfaa8525b is the first bad commit
commit dd74ff42394ac2f309108ccc0f53674cfaa8525b
...

jonsmithers on Feb 4, 2022

This helps a bunch and gives enough info for me to take a look. I’ll try to get to it tonight.

Kethku on Jan 27, 2022

@djmaxus This issue was resolved, and it’s been working for me for months. If you’re on the latest neovide, and it’s still happening, then the issue is something else.

bmulholland on Aug 30, 2022

@fredizzimo You are right, I disabled the shell integration of iTerms2 from .zshrc and .bash_profile and Neovide starts ok.

caeu on Jan 26, 2022

@caeu, The more I think about it, the more I think we should try the other approach, which does not rely on redirecting output across shells. So unless that doesn’t work, there’s no need for you to test further, and possibly mess up your system.

fredizzimo on Jan 26, 2022

I don’t think Alacritty is a good reference, since they actually want to start a real shell. In this case we just want to run a shell command from outside of it.

I think what we need is for someone to run /bin/zsh -lc 'which nvim', outside of a shell, and see what it outputs. If that’s not possible, then at least try it from within a shell and verify that it outputs just the path without any prompts as it should.

fredizzimo on Jan 26, 2022

Same when running nevoide --neovim-bin /usr/local/bin/nvim

caeu on Jan 25, 2022