07e569a25d
This is how Nvim behaves when the "abstract_ui" termcap is activated: - No data is written/read to stdout/stdin by default. - Instead of sending data to stdout, ui_write will parse the termcap codes and invoke dispatch functions in the ui.c module. - The dispatch functions will forward the calls to all attached UI instances(each UI instance is an implementation of the UI layer and is registered with ui_attach). - Like with the "builtin_gui" termcap, "abstract_ui" does not contain any key sequences. Instead, vim key strings(<cr>, <esc>, etc) are parsed directly by input_enqueue and the translated strings are pushed to the input buffer. With this new input model, its not possible to send mouse events yet. Thats because mouse sequence parsing happens in term.c/check_termcodes which must return early when "abstract_ui" is activated. |
||
---|---|---|
.ci | ||
cmake | ||
config | ||
contrib | ||
runtime | ||
scripts | ||
src/nvim | ||
test | ||
third-party | ||
.gitignore | ||
.travis.yml | ||
.valgrind.supp | ||
BACKERS.md | ||
clint-files.txt | ||
clint.py | ||
CMakeLists.txt | ||
CONTRIBUTING.md | ||
Doxyfile | ||
LICENSE | ||
Makefile | ||
neovim.rb | ||
README.md | ||
uncrustify.cfg |
Website | Wiki | Documentation | Mailing List | Twitter | Reddit | 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
- Job control (work with processes asynchronously)
- msgpack remote API
- Performance, reliability, and portability improvements
- See the progress page for a comprehensive list.
What's being worked on now
- Port all IO to libuv
- Lots of refactoring
- A VimL => Lua transpiler
How do I get it?
There is a formula for OSX/homebrew, a PKGBUILD for Arch Linux, RPM, deb, and more. See the wiki!
Community
Join the community on IRC in #neovim on Freenode or the mailing list
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 by authors who did not sign the Contributor License Agreement (CLA) 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-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.