fredizzimo

> The actual problem here is bringing the correct flags for every specific shell which is not clever from our perspective, but just executing the login using zsh will force...

The latest executables can be found at the bottom of this page https://github.com/neovide/neovide/actions/runs/12611813099

Ah, that's one thing that I forgot to mention, I noticed that we have a similar bug on wsl as well, but only macOS is fixed here.

Hm @ngpong, did you get the same message as the OP? I think that you should have received something like`ERROR: Unexpected output from neovim binary` if parts of you fish...

Hm, that still looks strange, and it looks like we have some problems with the error reporting, but I'm unable to investigate myself for some time, I'm on vaccation and...

For the homebrew/linuxbrew issue, see this https://github.com/neovide/neovide/issues/2741

It looks like you are using a very old version of Neovide, we fixed this bug in version 0.11.2 https://github.com/neovide/neovide/releases/tag/0.11.2 > Fix disappearing characters on Neovim 0.9.2 and greater

I use it to load project specific configuration for LSPs that don't have their own configuration files. Something like this ```lua local function load_config(root_dir) local path = Path:new(root_dir, ".nvimlsp") if...

One simple concrete example. The ccls language server can only be configured through `init_options`, so making changes in `on_attach` is to late. Different projects output `compile_commands.json` in different locations. So...

I haven't looked closer at this, but it looks like it tries to detect the buffer format here: https://github.com/neovide/neovide/blob/3960baad20d19e10c0857e07f87ddd0c65e27177/src/bridge/handler.rs#L50-L57 And somehow that either fails, or the wrong assumption was made...