Skip to content

0.11.0

Compare
Choose a tag to compare
@fredizzimo fredizzimo released this 07 Aug 14:58
· 191 commits to main since this release
cb9bbe2

First of all, we'd like to formally and enthusiastically thank the winit team over at https://github.com/rust-windowing/winit for developing, providing and stabilizing a new, neat and nice keyboard API over the course of several years. Without them and their monstrous efforts, Neovide would have its Wayland support still broken and subject to even more input issues.

Breaking Changes

  • The environment variable WINIT_UNIX_BACKEND=x11 is no longer supported. It's preferred to run in native Wayland. But if you absolutely want to run in XWayland, you can run env -u WAYLAND_DISPLAY neovide instead.
  • The keyboard mappings can work slightly differently, and due to the issues on macOS, you might want to stay on an older release if those cause problems for you.
    • CMD + SHIFT works as CMD only
    • fails to interprets in Macos. I set neovide_input_macos_alt_is_meta
    • Make sure that you map the actual character produced and don't include shift in your mappings. There are two exceptions to this:
      • Mappings of special keys like <Space>, <Enter>, <Tab>, <F1> and so on. You can use <S-Space> to map shift combined with space.
      • Mappings involving CTRL and normal alphabetic characters, due to the way Neovim deals with them:

        CTRL-{char} {char} typed as a control character; that is, typing {char}
        while holding the CTRL key down. The case of {char} is
        ignored; thus CTRL-A and CTRL-a are equivalent. But in
        some terminals and environments, using the SHIFT key will
        produce a distinct code (e.g. CTRL-SHIFT-a); in these
        environments using the SHIFT key will not trigger commands
        such as CTRL-A.

Features

Bug Fixes

Other changes

New Contributors

Full Changelog: 0.10.4...0.11.0