Welcome to the second monthly newsletter for Neovim, the project that dreams to be the next text editor that we’ll all love.
It was decided that a new colorscheme would be great for Neovim. To do this, the Neovim collaborators will create a contest that will allow submissions of colorschemes. After some time, the submissions will close and then a new Poll will be started to let the community pick the winner.
The winner(s) will be awarded the prize money and their colorschemes will forever be enshrined in distributions of Neovim.
Stay tuned to the Neovim Twitter for when the submission guidelines and process are announced.
This means that if you’ve contributed code before the switch to Apache 2.0, your code is still under the old Vim license. It won’t become part of Apache 2.0 unless you sign the CLA.
As @tarruda notes, the code runs in another process, blocks until the client responds, has a 3 second timeout and has a call stack limit of 20.
@tarruda opened a pull request that proposed various fixes and improvements to some of his past work. The changes targeted the jobs API, streams API and lastly the events API. All of these past features were discussed in last month’s newsletter.
These changes included the ability to send large amounts of data through streams, added code for msgpack parsing failures, and an ability to lock onto a set of event sources.
For help building on other platforms, be sure to check out the newly minted Building Neovim page on the Wiki for all things related to compiling.
A function called
mch_libcall() was temporarily removed during some of the
cleanup. It is called in Vim by using the
and is used by some plugins.
Discussion started around its temporary removal and how to re-add it to retain compatibility with Vim. @aktau proposed a solution and then created a pull request with the new changes which have since been merged.
Contributors to Neovim live in countries all over the world. Many native speakers have been busy updating the translations in their native languages.
String handling is really important in a text editor and the current codebase doesn’t have good abstractions for string handling (even though we’ve been slowly improving it). It’s a miracle how much can be accomplished with so little abstraction (and a lot of low level code).
In addition to that, the user documentation for Neovim is being moved there as well.
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 second newsletter? Feel free to reach out through the Neovim Twitter.
Also 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 around the first Friday of August.
Until next time.