fredizzimo

It looks like someone made the wrong assumption when writing that code or something. The `win32yank.exe` implementation in Neovim unconditionally changes the line endings to windows on yank, and linux...

This was fixed by * https://github.com/neovide/neovide/pull/2869

Strange, the path looks correct, and at least forward slashes should work, I'm currently using `neovim-bin = "f:/proj/neovim/composed/bin/nvim"` on Windows 11. Are you sure you don't have the environment variable...

We use this to get the path to the folder, https://codeberg.org/dirs/dirs-rs and I checked that it internally uses https://learn.microsoft.com/en-us/windows/win32/shell/knownfolderid I'm not sure if those can be customized and where you...

Closing this as not a bug

@falcucci, is there a reason why the blur is not unconditionally independet of transparency is used or not. You added the condition with the initial support here https://github.com/neovide/neovide/pull/2273

The name `neovide_normal_opacity`, is fine and will be consistent when we name rename `neovide_transparency` to `neovide_opacity`. But that's not the only otherway to add transparency, blend on a highlight group...

We don't need any terminal protocol for this, we need support from Neovim See my reply here https://github.com/neovim/neovim/issues/32539#issuecomment-2684181079

https://wayland.app/protocols/ext-background-effect-v1 has been merged, but as far as I know there's no compositor support yet.

I'm not sure how useful the Kitty protocol is for non-terminal UIs, like Neovide. While we haven't done anything yet, I have been looking at different ways of implementing image...