a4fad9d89e
we introduce NEOVIDE_BUILD_VERSION in build.rs from `git describe` so tagged builds keep the package version and non-tagged builds report `nightly-<count>+g<sha>` with `-dirty` preserved when applicable. we kinda of follow the neovim pattern for nightly versions since the target users are used to it. we also add cargo rerun tracking for git metadata and tracked files, and use the generated version for the CLI `--version` output, startup version logging and `g:neovide_version` consecutively. note: bundles will not be affected since they have its own limited versioning scheme. |
||
|---|---|---|
| .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.