How vim/vim-win32-installer works
This repository builds and distributes Windows Vim snapshots, rather than implementing the Vim editor itself. The documented workflow is automated builds, optional patch application, packaging as installers and architecture-specific archives, then release distribution; nightly builds also go to WinGet. README capabilities include signed builds and optional interpreter and terminal/encryption support in the binaries. Workflow and packaging source was not sampled, so links are limited to relationships documented in the README or evident in the launcher source.
Main entry points: package Package contents · workflows Build automation · gvim.nsi NSIS installer · vim-launcher.c Vim launcher
Components 14
Build inputs
- Vim source
- Custom patches
patch - Build automation
.github/workflows
Windows packaging
- Package contents
package - NSIS installer
nsis/gvim.nsi
Release distribution
- Release artifacts
- WinGet repository
- Signing service
Bundled runtime
- Vim launcher
vim-launcher/vim-launcher.c - Interpreter interfaces
- Terminal support
- Encryption support
Other components
- Build maintainer
- Vim user
Connections 15
- Build maintainer → Build automation: starts builds
- Custom patches → Build automation: applied before build
- Vim source → Build automation: builds from
- Build automation → Package contents: produces binaries
- Package contents → NSIS installer: installer contents
- Package contents → Release artifacts: archives binaries
- NSIS installer → Release artifacts: installer output
- Release artifacts → Vim user: downloaded by
- Build automation → WinGet repository: submits nightly builds
- Release artifacts → Signing service: occasionally signed
- Vim user → Vim launcher: runs
- Vim launcher → Package contents: locates Vim executable
- Package contents → Interpreter interfaces: supports optional interfaces
- Package contents → Terminal support: includes winpty
- Package contents → Encryption support: includes libsodium