9477f53a9c
we are now replacing the native tabs switcher into a Neovide-owned custom editor switcher. Why? The native tab overview was a temporary choice for this feature. editors should be about moving between Neovide editors without limitations, but tying it to the system tabs overview made the behavior depend on whether native tabs to be enabled, plus hacking to make it work properly not affecting separate windows. users who prefers separate-window has been forced to merge and detach windows just to present a choice to switcher windows easier which made the single-window case fall back to pinned-window toggling. That was a known gap. now with a Neovide-owned custom switcher it gives both modes the outcome. NOTE: behavior-wise shouldn't change, besides the switcher appearing now even for separate-window mode. |
||
|---|---|---|
| .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.