Wednesday, December 15, 2021

Re: [UPDATE] editors/neovim 0.5.1->0.6.0

On 15.12.2021 12:16, Paco Esteban wrote:
>On Tue, 14 Dec 2021, Paco Esteban wrote:
>
>> On Mon, 13 Dec 2021, Laurence Tratt wrote:
>>
>> > On Sat, Dec 11, 2021 at 07:06:46PM -0700, Evan Fiddes wrote:
>> >
>> > Hello Evan,
>> >
>> > > This bumps the neovim version to 0.6.0 the most current release. See patch
>> > > notes[0] for a detailed breakdown.
>> > >
>> > > [0] https://github.com/neovim/neovim/releases/tag/v0.6.0
>> >
>> > I had a small leading whitespace issue with your patch, which might be a
>> > MIME encoding thing. Otherwise, the update looks good, applies, and neovim
>> > 0.6.0 so far seems to be working well!
>>
>> On the port Makefile, edd@ states that the versions of LuaJIT and luv
>> have to be pinned to specific versions listed on the source code.
>>
>> This patch does not update those. I'm not sure of the consequences of
>> this, but I guess strange runtime errors would be common.
>>
>> My attempts until now hit a linker issue, I'll send a patch when I fix
>> that unless somebody beats me to it.
>
>Here's that patch.
>It depends on the update of devel/libuv that edd@ just sent.
>
>Regression tests are enabled again as they are back on the distribution
>tarball. Most of them pass, but 10 fail because they cannot create a
>swap file.
>
>Works fine for me on amd64 for general editing and some coding using the
>LSP and tree-sitter integration.
>More tests are very welcome.
>
>OK to commit ?
>

Hi Paco,

Firstly, thank you for your efforts on this, and thank you for the
explanations.

This diff fixes the disjointed partial I submitted. Make was sucessful and
neovim @ 0.6.0 is running OK here. Running treesitter, lua plugins and lsp.
also amd64.

If this is depends on libuv and that ties into several other ports; cmake
being a possible point of concern. Should this be held until devel/libuv
is merged?

Thanks!

--
Evan

No comments:

Post a Comment