de570a0b84
It's acceptable for “git describe --tags --exact-match …” to fail, since all runtime updates commits are untagged. All that matters is that we get a tag when one exists. Therefore, ignore the failure status of the git describe call, relying on the captured output instead. |
||
|---|---|---|
| .ci | ||
| cmake | ||
| config | ||
| contrib | ||
| man | ||
| runtime | ||
| scripts | ||
| src | ||
| test | ||
| third-party | ||
| unicode | ||
| .asan-blacklist | ||
| .editorconfig | ||
| .gitignore | ||
| .travis.yml | ||
| .valgrind.supp | ||
| appveyor.yml | ||
| BACKERS.md | ||
| clint.py | ||
| CMakeLists.txt | ||
| CONTRIBUTING.md | ||
| Doxyfile | ||
| ISSUE_TEMPLATE.md | ||
| LICENSE | ||
| Makefile | ||
| neovim.rb | ||
| README.md | ||
Website | Community | Wiki | Documentation | Mailing List | Twitter | Bountysource
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 the implementation of new/modern user interfaces without any modifications to the core source
- Improve extensibility with a new plugin architecture
For lots more details, see the wiki!
What's been done so far
- Automatic history merge between multiple editor instances
- XDG-compliant configuration
- Embedded terminal emulator
- Asynchronous job control
- MessagePack remote API
- Pushdown automaton for state transitions
See the progress page for a comprehensive list.
What's being worked on now
- Port all IO to libuv
- Convert legacy tests to Lua tests
- VimL => Lua translator
How do I get it?
There is a formula for OSX/homebrew, a PKGBUILD for Arch Linux, RPM, deb, and more. See the wiki!
Contributing
...would be awesome! See the wiki for more details.
License
Neovim is licensed under the terms of the Apache 2.0 license, except for parts that were contributed under the Vim license.
-
Contributions committed before b17d96 remain under the Vim license.
-
Contributions committed after b17d96 are licensed under Apache 2.0 unless those contributions were copied from Vim (identified in the commit logs by the
vim-patchtoken).
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.