Hi,

Here's neovim.

Notes:

 * We can't run the full test suite until "busted" is ported.

 * The other tests have issues, but only when run under the ports
   tree. I *think* this is because the ports tree is running the tests
   under some terminal configuration that the suite doesn't expect. When
   run under ports, the terminal is confined to what looks like 80x25,
   yet if I run the tests outside of ports, the output uses the whole
   terminal. Weird. Any ideas?

 * No attempt to use LuaJIT for now, just plain Lua.

 * I've not ported any language plugin modules. You can get the Python
   helpers from pip for now. Lua is built in.

 * Needs uncommitted ports: lubuv, libvterm, lua-bitop. All submitted.

If you have never used neovim, the config dir is ~/.config/nvim, and the
config file is ~/.config/nvim/init.vim. You can symlink your existing
vim config and directory, and this will work. Once in nvim, run
':CheckHealth' to see what else you might need to do.

Please also read the README if you want to use this in tmux.

I've been using manual source builds of nvim for a few months now, and
I've had very few problems. However, there is a bug where nvim crashes
when the window size changes under xfce terminal
(https://github.com/neovim/neovim/issues/5692). (I'll add that the the
README on the next iteration actually).

I'll test this for the duration of next week to iron out problems.

P.S. Whilst debugging the tests, I was searching for TERM in
bsd.port.mk. Around line 1956, we have:

   ${SUDO} ${SETENV} ${_TERM_ ENV} ...

Which I suspect should be:

   ${SUDO} ${SETENV} ${_TERM_ENV} ...

Right?

-- 
Best Regards
Edd Barrett

http://www.theunixzoo.co.uk

Attachment: neovim1.tgz
Description: application/tar-gz

Reply via email to