fredizzimo
fredizzimo
@asabla `vim.g.neovide_input_macos_option_key_is_meta = 'only_left'`, or `both`, will always be needed for Neovide to interpret the key press as ``, otherwise it will be interpreted as the character macOS produces for...
I think you should be able to create similar tests as the ones in `font.rs`, that is to test the actual font config instead of the whole integration with Swash,...
@xzbdmw, sorry for taking so long with this. I'm on vaccation with only an ipad available and the CI is broken (not your fault) so I didn't merge. I'm not...
@xzbdmw, just fixing the documentation is good enough for now. Unless you also want to add a warning. To me a warning makes sense, but we have various reports of...
The CI has now finally been fixed, can you rebase on top of main?
I'm not a macOS user, but I think `open -a Neovide --args {filename}` should do it. That will pass the arguments to Neovide instead of going through the finder. Or...
When looking at a different issue, I saw this https://developer.apple.com/documentation/appkit/nsapplicationdelegate/1428385-applicationdidfinishlaunching. So, we should be able to wait for that until the list of files is passed to neovim. Or perhaps...
Yes, it looks like we really have to wait until all the open requests are handled at startup and then pass all of them to Neovim. That it turn requires...
I think it is, but it needs a bit re arranging of the code. We should be to gather all the request to the open file events and delay the...