mirror of
https://github.com/neovim/neovim.git
synced 2026-07-14 13:20:35 +00:00
65b8232260
* vim-patch:8.2.1082: Coverity complains about ignoring dict_add() return value Problem: Coverity complains about ignoring dict_add() return value. Solution: Add (void).91639195efN/A patches for version.c: vim-patch:8.2.0210: Coverity complains about uninitialized field Problem: Coverity complains about uninitialized field. Solution: Initialize the field.eed3571fe0vim-patch:8.2.0424: checking for wrong return value Problem: Checking for wrong return value. (Tom) Solution: Invert the check and fix the test.97acfc781bvim-patch:8.2.0436: no warnings for incorrect printf arguments Problem: No warnings for incorrect printf arguments. Solution: Fix attribute in declaration. Fix uncovered mistakes. (Dominique Pelle, closes vim/vim#5834)db99f9f29avim-patch:8.2.0498: Coverity complains about uninitialized field Problem: Coverity complains about uninitialized field. Solution: Initialize the whole typval_T.4227c789ffvim-patch:8.2.0668: compiler warning for int/size_t usage Problem: Compiler warning for int/size_t usage. Solution: Change "int" to "size_t". (Mike Williams)7f6f56f43cvim-patch:8.2.1034: compiler warning for uninitialized variables Problem: Compiler warning for uninitialized variables. Solution: Add initializations. (John Marriott)38041da1c2vim-patch:8.2.1117: Coverity warns for unsing unitialized field Problem: Coverity warns for unsing unitialized field. Solution: Initialize v_lock.a9a8e5f0dcvim-patch:8.2.1148: warning for using int instead of size_t Problem: Warning for using int instead of size_t. Solution: Change "len" argument to size_t. (Mike Williams)cbb6bdcd89vim-patch:8.2.1251: Vim9: warning for pointer usage, test failure undetected Problem: Vim9: warning for pointer usage, test failure undetected. Solution: Fix pointer indirection. Give error when executing function failed for any reason. Fix instruction names.682d0a1546printable_func_name() is applicable but the vim9 changes are N/A. Compilers can detect misuse of static functions. vim-patch:8.2.1275: Vim9: compiler warning for buffer size Problem: Vim9: compiler warning for buffer size. Solution: Change the offset from 10 to 15. (Dominique Pellé, closes vim/vim#6518)5a67c37a55vim-patch:8.2.1443: Vim9: crash when interrupting a nested :def function Problem: Vim9: crash when interrupting a nested :def function. Solution: Push a dummy return value onto the stack. (closes vim/vim#6701)cdd70f09a5vim-patch:8.2.1818: SE Linux: deprecation warning for security_context_t Problem: SE Linux: deprecation warning for security_context_t. Solution: Use "char *" instead. (James McCoy, closes vim/vim#7093)8956023920SELINUX support was removed in commit1de77bbcecvim-patch:8.2.2004: compiler warning for uninitialized variable Problem: Compiler warning for uninitialized variable. Solution: Initialize "ufunc". (John Marriott)b3a01946b3vim-patch:8.2.2051: Vim9: crash when aborting a user function call Problem: Vim9: crash when aborting a user function call. Solution: Do not use the return value when aboring. (closes vim/vim#7372)34c54eb6cbvim-patch:8.2.2270: warning for size_t to int conversion Problem: Warning for size_t to int conversion. (Randall W. Morris) Solution: Add a type cast.38a434f7bavim-patch:8.2.2333: Vim9: warning for uninitialized variable Problem: Vim9: warning for uninitialized variable. (Tony Mechelynck) Solution: Initialize "res".cb6cbf29e9vim-patch:8.2.2460: Coverity warns for unused value Problem: Coverity warns for unused value. Solution: Do not reset the return value to OK.fc1dafa91cvim-patch:8.2.2461: Coverity warns for unchecked return value Problem: Coverity warns for unchecked return value. Solution: Add "(void)" to avoid the warning.fef8064b54vim-patch:8.2.2557: compiler warning for shadowd variable Problem: Compiler warning for shadowd variable. Solution: Declare "p" only once.087b5ff35dvim-patch:8.2.2730: Coverity complains about not restoring character Problem: Coverity complains about not restoring character. Solution: Also restore the character in case of an error.c9605f0595vim-patch:8.2.2795: Coverity warns for not using return value Problem: Coverity warns for not using return value. Solution: Check the return value of compiling the substitute expression.169502fb0bvim-patch:8.2.2995: linker errors with dynamic Python 3.10 Problem: Linker errors with dynamic Python 3.10. Solution: Add a couple of library entries. (Zdenek Dohnal, closes vim/vim#8381, closes vim/vim#8356)90478f35a8vim-patch:8.2.3000: Vim9: warning for uninitialized variable Problem: Vim9: warning for uninitialized variable. Solution: Add initialization. (John Marriott)3b814af7e1vim-patch:8.2.3014: Coverity warns for freeing static string Problem: Coverity warns for freeing static string. Solution: Do not assign static string to pointer. (Dominique Pellé, closes vim/vim#8397)6e9695525evim-patch:8.2.3205: Coverity reports a null pointer dereference Problem: Coverity reports a null pointer dereference. Solution: Change the logic to avoid Coverity gets confused.1b862c466bvim-patch:8.2.3294: Lua: memory leak when adding dict item fails Problem: Lua: memory leak when adding dict item fails. Solution: Free the typval and the dict item.1b6acf02b7vim-patch:8.2.3302: Coverity is not run from github Problem: Coverity is not run from github. Solution: Add a coverity script. (James McCoy, closes vim/vim#8714)d57a6bd98cvim-patch:8.2.3319: Coverity action on github does not work Problem: Coverity action on github does not work. Solution: Remove undefined $SRCDIR. (James McCoy, closes vim/vim#8739)eed9616120* vim-patch:8.2.1085: Coverity complains about ignoring dict_add() return value Problem: Coverity complains about ignoring dict_add() return value. Solution: Add (void).6d90c61c5a
Documentation | Chat | Twitter
Neovim is a project that seeks to aggressively refactor Vim in order to:
- Simplify maintenance and encourage contributions
- Split the work between multiple developers
- Enable advanced UIs without modifications to the core
- Maximize extensibility
See the Introduction wiki page and Roadmap for more information.
Features
- Modern GUIs
- API access from any language including C/C++, C#, Clojure, D, Elixir, Go, Haskell, Java, JavaScript/Node.js, Julia, Lisp, Lua, Perl, Python, Racket, Ruby, Rust
- Embedded, scriptable terminal emulator
- Asynchronous job control
- Shared data (shada) among multiple editor instances
- XDG base directories support
- Compatible with most Vim plugins, including Ruby and Python plugins
See :help nvim-features for the full list!
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 the Building Neovim wiki page 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_INSTALL_PREFIX=/full/path/
make install
CMake hints for inspecting the build:
cmake --build build --target helplists all build targets.build/CMakeCache.txt(orcmake -LAH build/) contains the resolved values of all CMake variables.build/compile_commands.jsonshows the full compiler invocations for each translation unit.
Transitioning from Vim
See :help nvim-from-vim for instructions.
Project layout
├─ ci/ build automation
├─ cmake/ build scripts
├─ runtime/ user plugins/docs
├─ src/nvim/ application source code (see src/nvim/README.md)
│ ├─ api/ API subsystem
│ ├─ eval/ VimL 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
├─ third-party/ CMake subproject to build dependencies
└─ 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:
http://iccf-holland.org/
http://www.vim.org/iccf/
http://www.iccf.nl/
You can also sponsor the development of Vim. Vim sponsors can vote for
features. The money goes to Uganda anyway.