This post is in continuation with this post.

Neovim has come to be a very hackable, developer friendly version of Vim. It actually is what their website claims to be: literally the future of vim and Vim-fork focused on extensibility and usability. One of the goals of nvim is to allow UIs to set different grid-sizes for each window and receive grid-based events.

Why do we need grid-based updates and different grid-sizes than what nvim sets?

After a month and a half of working with Neovim, we have an experimental working prototype that breaks up the screen grid in per-window grids, allows UIs to set different sizes for each window grid and receive grid based events.

Although we don’t have it yet, but we expect to have it implemented in a GUI like python-gui as an example by the end of the GSoC coding period i.e. mid August. We also would encourage GUI implementers of nvim to test out the experimental API and report the inevitable bugs that have crept in. This would be a step towards finalizing the said prototype and allow easy transition of GUIs to better control of UI in their projects.

The work done so far can be found here.

Follow the gsoc tag for updates.