Vim-fork focused on extensibility and usability
Go to file
Eliseo Martínez 3b523ec699 Introduce nvim namespace: Fix localization.
- Fix executable path.
- Make po file title similar as others.
2014-05-15 20:46:02 +02:00
cmake Generate a lua module to help pass build-related settings. 2014-05-03 10:36:54 -04:00
config Introduce nvim namespace: Fix build process. 2014-05-15 20:46:01 +02:00
contrib add .vimrc and src/.ycm_extra_conf.py 2014-03-14 20:37:03 -03:00
scripts Introduce nvim namespace: Fix build process. 2014-05-15 20:46:01 +02:00
src/nvim Introduce nvim namespace: Fix localization. 2014-05-15 20:46:02 +02:00
test Introduce nvim namespace: Fix unit tests. 2014-05-15 20:46:02 +02:00
third-party Add --with-pic flag to msgpack configuration 2014-05-12 17:06:54 -03:00
.gitignore Introduce nvim namespace: Fix localization. 2014-05-15 20:46:02 +02:00
.travis.yml Configure travis to perform a 32-bit build 2014-04-22 21:55:59 -03:00
.valgrind.supp Add helpers for debugging with valgrind 2014-04-05 11:05:31 -03:00
BACKERS.md I donated > 50 $, should be with URL 2014-04-20 10:35:18 -03:00
clint-files.txt Introduce nvim namespace: Fix clint. 2014-05-15 20:46:02 +02:00
clint.py Introduce nvim namespace: Fix clint. 2014-05-15 20:46:02 +02:00
CMakeLists.txt Introduce nvim namespace: Fix build process. 2014-05-15 20:46:01 +02:00
CONTRIBUTING.md Update CONTRIBUTING.md with current info 2014-05-08 16:58:15 -05:00
Doxyfile Add basic Doxyfile. 2014-03-31 07:36:00 -03:00
Makefile Introduce nvim namespace: Fix build process. 2014-05-15 20:46:01 +02:00
neovim.rb Homebrew formula builds dependencies through make 2014-03-19 08:00:15 -03:00
README.md Update README: progress section 2014-05-02 15:59:52 -03:00
uncrustify.cfg Issue #311 - Clean up blowfish.c/h, charset.c/h, diff.c/h, digraph.c/h, garray.c/h, hashtab.c/h, popupmnu.c/h, sha256.c/h, version.c/h. Update uncrustify to move logical operators to the beginning of the line when splitting. Also, clean up arabic.c/h and farsi.c/h 2014-03-16 12:00:41 -03:00
vim-license.txt include a copy of the Vim License 2014-02-22 11:57:44 +00:00

Neovim

Website | Google Group | Twitter | Bountysource

Build Status Stories in Ready Coverage Status

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

  • Cleaned up source tree, leaving only core files
  • Removed support for legacy systems and moved to C99
    • Removed tons of FEAT_* macros with unifdef
    • Reduced C code from 300k lines to 170k
  • Enabled modern compiler features and optimizations
  • Formatted entire source with uncrustify
  • Replaced autotools build system with CMake
  • Implemented continuous integration and test coverage
  • Wrote 100+ new unit tests
  • Split large, monolithic files (misc1.c) into logical units (path.c, indent.c, garray.c, keymap.c, ...)
  • Implemented job control ("async")
  • Reworked out-of-memory handling resulting in greatly simplified control flow
  • Merged 50+ upstream patches (nearly caught up with upstream)
  • Removed 8.3 filename support
  • Changed to portable format specifiers (first step towards building on Windows)

What's being worked on now

  • Porting all IO to libuv
  • Lots of refactoring
  • A VimL => Lua transpiler
  • Formatting with clint.py
  • msg-pack remote API

How do I get it?

There is a formula for OSX/homebrew, a PKGBUILD for Arch Linux, and detailed instructions for building on other OSes.

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

Vim itself is distributed under the terms of the Vim License. See vim-license.txt for details.

Vim also includes this message:

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.