fredizzimo

The new Neovide API, which will be released with 0.15.1, might also help fixing the bug if nothing else works. https://neovide.dev/api.html#redraw-control

For the deprecation warning, you can model it after this: https://github.com/neovide/neovide/blob/000b75c0f3bcfb602967cc5c2e8a9d584be06a02/src/window/macos.rs#L180C12-L180C39

The macOS build failure is not your fault. Something has changed in the nightly compiler. This might fix it, but I'm not sure: * https://github.com/neovide/neovide/pull/2768

It looks like a bug in `smithay-clipboard` ``` #0 wl_map_insert_new (map=map@entry=0x5efb10fc2470, data=data@entry=0x771684001570, flags=0) at ../wayland-1.23.1/src/wayland-util.c:228 #1 0x000077168b62a2f2 in proxy_create (factory=factory@entry=0x771684001500, interface=interface@entry=0x5efae40252e8 , version=version@entry=3) at ../wayland-1.23.1/src/wayland-client.c:492 #2 0x000077168b62a475 in create_outgoing_proxy (message=0x5efae40242e8...

Wayland does not allow GUI applications as root, and even if it did you should never run Neovide or Neovim as a root. Instead use `SUDO_EDITOR=neovide sudoedit /path/to/file`

Ah, sorry, I misread the issue. The problem is likely that the config file https://neovide.dev/config-file.html#location has the wrong permissions, due to running it as root previously. And possibly also the...

`--debug` is not a valid argument to nvim, so that explains why it "crashes". Our error reporting is a bit broken currently, so it just reports that it crashed, instead...

Yes it's likely that it's Neovim that's crashing. That also explains why it works with root, since it doesn't use your config. You could try `neovide -- --clean`. And if...

You should be able to use https://neovim.io/doc/user/autocmd.html#BufEnter

@itbear-shu, you are infected by a virus, so I banned your account from here. Contact us on discord or matrix, and we can unban you when you have removed the...