The way to “win” at open source is to be consistent and steady.
Welcome to the fourth newsletter for Neovim, the project that aims to overhaul the Vim code base. It also hopes to provide out of the box features yet a more powerful interface for extending the editor.
Unixstickers will be donating a portion of the profits to ICCF Holland in support of Bram Moolenar’s work on Vim.
The last newsletter detailed how Neovim reached 1,000 issues/pull requests on its GitHub repository.
Floobits, a service that integrates with editors to make it easier to write code together, has deprecated its Vim plugin in favor of a plugin for Neovim.
Already Floobits says that the new plugin “has fewer bugs and performs better” than their previous plugin. Read their entire write up to learn more about their thoughts or view the repository to see the code.
@tarruda finished his pull request that did two things. It gave the
initial implementation of remote plugins which are going to be plugins that
run in external processes and communicate to Nvim through msgpack-rpc. Details
can be found in
The second change is an improvement to the existing provider infrastructure to
allow providers to be implemented in VimScript. This gives more flexibility as
previously providers needed to be implemented using msgpack. More details for
this can be found in the
If you run into issues with this new plugin system, it might be caused by stale files from old builds and/or old configurations.
iconv is a library “for use on systems which don’t have one, or whose implementation cannot convert from/to Unicode.”
During the migration to CMake, the macro
USE_ICONV was missed which was used
to indicate such a system. Thus Neovim never triggered specific encoding
conversions when needed.
@aktau has an excellent write up called Neovim: input encoding and you which discusses input encoding in detail and as well as how he discovered this issue. He created a pull request which fixed this and it has been merged into the master branch.
Since the last newsletter, a great number of Vim patches have been merged into Neovim.
You can view the complete status of the Vim patches within the autogenerated Vim Patch Report on the Neovim website.
After @tarruda opened up a master issue discussing legacy test migration, the first legacy test was migrated over by @nate00. @rainerborene then followed up with a batch of conversions and is already working on the next batch.
Previously the legacy tests were ran by launching an instance of
Vim with the flag
-s <test file> which enables silent mode.
This mode reads the lines as if you had typed them. The tests can be ran on
nvim by running
@splinterofchaos happened to come across a bug in which a job
activity’s output may become corrupted. The rstream structure
could contain incomplete lines if the buffer fills up before reaching a
To remedy this @splinterofchaos added logic at the API level to find a
new-line character and return it as well. The end result is that a job’s
activity is now storing
stdout in a list instead of a string. If your code is
utilizing a job, you might want to address this.
The sign feature can be used to place an indicator on a given line of a buffer. It will show up on the left side of the editor window. This is used for debuggers, syntax linters, and various other plugins.
The bug caused nvim to not remove signs placed across multiple buffers when
:sign unplace command.
Neovim has moved its homebrew formula into its own repository in the organization to make it easy to install using a tap instead of just a formula. You can install it now with the following:
These improvements include:
If you’d like to help support development, you may donate using Bitcoins here:
1Evu6wPrzjsjrNPdCYbHy3HT6ry2EzXFyQ or back the team on the Neovim
There are plenty of opportunities to help out and plenty of things to do.
Do you have any feedback or suggestions regarding this newsletter? Feel free to reach out through the Neovim Twitter.
This newsletter cannot cover all of the contributions and support of the community. Thanks to all of the other contributors that have helped in some way during the last two months.
Be sure to subscribe to the RSS feed to stay up-to-date on what is happening in the Neovim world. The next newsletter will be released in roughly two months near the beginning months of the next year.
Until next time.