05e823020f
*A grid having a size is not the same thing as that grid being visible* the experimental ui2 just exposed an assumption that we were doing. See #3446 A resize tells us that a grid exists and what size it has. It does not tell us that the grid is actually visible. Those seems to be different states from neovim, and we were treating them as if they were the same. For a new non-root grid that first appeared through a resize, we would instantiate a window immediately. That construction also gave it a position, and the renderer then treated that position update as if it meant to show that window. That logic only works if every resized grid is supposed to become visible right away. hidden helper windows can be resized long before neovim decides to place or show them. which seems to be the case now on ui2. So our old behavior could restore a window that neovim still considered hidden, which is why the wrong border and stale helper window would leak on startup and again after resizing. |
||
|---|---|---|
| .config | ||
| .github | ||
| assets | ||
| extra/osx/Neovide.app/Contents | ||
| lua | ||
| macos-builder | ||
| neovide-derive | ||
| snap | ||
| src | ||
| ubuntu-builder | ||
| website | ||
| wix | ||
| .editorconfig | ||
| .gitignore | ||
| .nvim-dap.lua | ||
| build.rs | ||
| Cargo.lock | ||
| Cargo.toml | ||
| LICENSE | ||
| README.md | ||
| rustfmt.toml | ||
| stylua.toml | ||
Neovide
This is a simple graphical user interface for Neovim (an aggressively refactored and updated Vim editor). Where possible there are some graphical improvements, but functionally it should act like the terminal UI.
To checkout all the cool features, installation instructions, configuration settings and much more, head on over to neovide.dev.
Screenshot of Neovide running on Windows
Installation
Pre-built releases for macOS, Windows and Linux are published on the GitHub Releases page and each release includes signed installers or AppImage builds. For detailed package-manager commands, verification steps and build from source instructions, see the installation guide on neovide.dev
Getting help
Neovide is maintained in spare time, so please be patient when asking for support. Depending on your question:
- Use the issue tracker for reproducible bugs or crash reports.
- Open a thread in GitHub Discussions for general questions, tips, or feature ideas.
- Chat in real time on Discord or on Matrix if you want help from other community members.
Discussions and chat are better suited to questions or workflow brainstorming, while the issue tracker works best for actionable bugs.
Supporting the Project
If you use and like Neovide, please consider sponsoring the project on GitHub. Funding helps pay for code-signing certificates, cross-platform hardware and the time maintainers spend supporting users. There are tiers for individuals and teams, and one-time contributions are welcome too.
Read more about sponsoring Neovide.
License
Licensed under MIT.