multisn8
multisn8
I suppose you could launch Neovide from the actual environment by running the binary rather than from the .app bundle. Oh wait, is it possible that the macOS specific logic...
Thanks for reporting! What GPU and which driver version do you run on?
That's unfortunately still quite a large range of possible GPUs; would you mind mentioning the exact CPU?
> I had issues as well, but I was able to cobble together a cheap fix. Admittedly I didn't look into glutin to know why it's happening, I'm just happy...
All users who are affected by this issue, could you please test out PR #1523 and report back? Maybe you also need to pass `--nosrgb` to Neovide.
Alright, thank you! I'll merge it (after preparing some other things).
@younes-ghorbany For the last issue: See the option `autochdir` through `:h 'autochdir'`. That'll autonavigate NeoVim inside of Neovide to the folder of the currently opened file. But that has nothing...
Thanks for reporting! Is it possible that you've switched keyboard layouts in-between? Also, are you running GNOME in a X11 or Wayland session (does `echo $WAYLAND_DISPLAY` in a terminal yield...
Thanks for the suggestion! Not sure how this could be meaningfully exposed to Neovim. Everything Neovim has are the "modifiers" `S`, `C`, `M`/`A` and `D`, Neovide cannot randomly add new...
That seems to be about exposing a function for determining whether caps lock is enabled at the moment to plugins and the like, not about detecting newly pressed caps lock.