Neovide Versions Save

No Nonsense Neovim Client in Rust

0.12.2

3 months ago

What's Changed

Breaking changes

Features

Bug fixes

New Contributors

Full Changelog: https://github.com/neovide/neovide/compare/0.12.1...0.12.2

0.12.1

4 months ago

essentially a slice of everything to round up 0.12.0 a bit

What's Changed

Features

Bug fixes

New Contributors

Full Changelog: https://github.com/neovide/neovide/compare/0.12.0...0.12.1

0.12.0

4 months ago

What's Changed

Breaking

Features

Fixes

Docs

Work behind the scenes

New Contributors

Thank you all, and also all others who contributed! :heart:

Full Changelog: https://github.com/neovide/neovide/compare/0.11.2...0.12.0

0.11.2

7 months ago

This release adds support for Neovim 0.9.2.

Features

Bug Fixes

Other changes

New Contributors

Full Changelog: https://github.com/neovide/neovide/compare/0.11.1...0.11.2

0.11.1

8 months ago

This release is essentially a tribute to the glorious work performed by Bram Moolenaar, who passed away on the 3rd of August 2023. One of the many insanely cool things he did was also supporting charity, additionally making Vim charityware, showing a message to help poor children in Uganda on startup if no file was opened. This intro screen was previously lost in Neovide due to architectural differences between the TUI and Neovide, but now in his spirit it is properly displayed in Neovide as well.

Features

Other changes

Full Changelog: https://github.com/neovide/neovide/compare/0.11.0...0.11.1

0.11.0

8 months ago

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
    • <A-n> 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: https://github.com/neovide/neovide/compare/0.10.4...0.11.0

0.10.4

1 year ago

Features

Bug Fixes

New Contributors

Full Changelog: https://github.com/neovide/neovide/compare/0.10.3...0.10.4

0.10.3

1 year ago

Changes

Bugfixes

  • Get full file paths on Windows working again
  • Properly bump version so cargo build --frozen doesn't complain anymore

0.10.2

1 year ago

Changes

Breaking

  • pumblend and winblend are respected now, see the FAQ for help on setting them. By default there's no transparency anymore due to the defaults of those being fully opaque. Added in https://github.com/neovide/neovide/pull/1199
  • (Linux) X11 and RPC clipboard mechanisms had another round of fixes again. If an older instance of Neovide has been attached to a NeoVim session and a new instance with this version connects, there be flames. Fix is to restart the NeoVim session. Added in https://github.com/neovide/neovide/pull/1540
  • Parsing of environment variables is so strict that it only accepts the value true as true now. This was not intended and will be fixed in the next release (NOT 0.13).

Bug fixes

Other

New Contributors

Full Changelog: https://github.com/neovide/neovide/compare/0.10.1...0.10.2

0.10.1

1 year ago

Changes

  • Updated lockfile for a clean build