Vim-fork focused on extensibility and usability
Go to file
zeertzjq 6725565258
fix(event-loop): process input before events (#27358)
Problem:
When nvim_input is followed immediately by non-fast events on RPC, both
events and input are available after the polling done by the os_inchar()
in state_enter(), but state_enter() then chooses to process events even
if input is available, which is inconsistent with state_handle_k_event()
that stops processing events once input is available.

Solution:
Also check for available input after the os_inchar() in state_enter().
2024-02-07 12:11:22 +08:00
.github ci(release): bump mac runner version to macos-12 2024-02-06 14:57:19 +01:00
cmake
cmake.config
cmake.deps build(deps): bump luajit to HEAD - 0d313b243 2024-02-04 20:58:14 +01:00
cmake.packaging
contrib
runtime feat(treesitter): show root nodes in :InspectTree (#26944) 2024-02-06 14:51:53 -06:00
scripts fix(doc): prevent doxygen confusion 2024-02-06 15:29:01 +00:00
src fix(event-loop): process input before events (#27358) 2024-02-07 12:11:22 +08:00
test fix(event-loop): process input before events (#27358) 2024-02-07 12:11:22 +08:00
.cirrus.yml
.clang-format
.clang-tidy
.clangd
.editorconfig
.git-blame-ignore-revs docs: .git-blame-ignore-revs #26397 2024-01-28 15:03:10 -08:00
.gitattributes
.gitignore
.luacheckrc
.luacov
.luarc.json
.mailmap
.stylua.toml
.styluaignore
BSDmakefile
BUILD.md
CMakeLists.txt build: various fixes 2024-02-01 12:06:55 +01:00
CMakePresets.json
CONTRIBUTING.md docs: include backtrace for bug-crash #27065 2024-01-28 14:26:13 -08:00
INSTALL.md
LICENSE.txt
MAINTAIN.md docs: document special labels used in CI 2024-01-29 13:46:04 +01:00
Makefile build(docs): separate lint job to validate vimdoc #27227 2024-01-28 14:22:39 -08:00
README.md

Neovim

Documentation | Chat

Coverity Scan analysis Clang analysis Packages Debian CI Downloads

Neovim is a project that seeks to aggressively refactor Vim in order to:

See the Introduction wiki page and Roadmap for more information.

Features

See :help nvim-features for the full list, and :help news for noteworthy changes in the latest version!

Install from package

Pre-built packages for Windows, macOS, and Linux are found on the Releases page.

Managed packages are in Homebrew, Debian, Ubuntu, Fedora, Arch Linux, Void Linux, Gentoo, and more!

Install from source

See BUILD.md and supported platforms for details.

The build is CMake-based, but a Makefile is provided as a convenience. After installing the dependencies, run the following command.

make CMAKE_BUILD_TYPE=RelWithDebInfo
sudo make install

To install to a non-default location:

make CMAKE_BUILD_TYPE=RelWithDebInfo CMAKE_INSTALL_PREFIX=/full/path/
make install

CMake hints for inspecting the build:

  • cmake --build build --target help lists all build targets.
  • build/CMakeCache.txt (or cmake -LAH build/) contains the resolved values of all CMake variables.
  • build/compile_commands.json shows the full compiler invocations for each translation unit.

Transitioning from Vim

See :help nvim-from-vim for instructions.

Project layout

├─ cmake/           CMake utils
├─ cmake.config/    CMake defines
├─ cmake.deps/      subproject to fetch and build dependencies (optional)
├─ runtime/         plugins and docs
├─ src/nvim/        application source code (see src/nvim/README.md)
│  ├─ api/          API subsystem
│  ├─ eval/         Vimscript subsystem
│  ├─ event/        event-loop subsystem
│  ├─ generators/   code generation (pre-compilation)
│  ├─ lib/          generic data structures
│  ├─ lua/          Lua subsystem
│  ├─ msgpack_rpc/  RPC subsystem
│  ├─ os/           low-level platform code
│  └─ tui/          built-in UI
└─ test/            tests (see test/README.md)

License

Neovim contributions since b17d96 are licensed under the Apache 2.0 license, except for contributions copied from Vim (identified by the vim-patch token). See LICENSE for details.

Vim is Charityware.  You can use and copy it as much as you like, but you are
encouraged to make a donation for needy children in Uganda.  Please see the
kcc section of the vim docs or visit the ICCF web site, available at these URLs:

        https://iccf-holland.org/
        https://www.vim.org/iccf/
        https://www.iccf.nl/

You can also sponsor the development of Vim.  Vim sponsors can vote for
features.  The money goes to Uganda anyway.