Hi Stuart,
On Mon, Sep 13, 2021 at 03:57:00PM +0100, Stuart Henderson wrote:
> On 2021/09/13 12:23, Edd Barrett wrote:
> > - Therefore, Neovim upstream uses a hard-coded LuaJIT commit and
> >statically embeds.
>
> Which branch does it take this from? I had a quick look at their repo
> but I
On 2021/09/13 12:23, Edd Barrett wrote:
> - Therefore, Neovim upstream uses a hard-coded LuaJIT commit and
>statically embeds.
Which branch does it take this from? I had a quick look at their repo
but I didn't find any version of luajit either directly or via submodule,
might have missed some
On Mon, Sep 13, 2021 at 12:23:54PM +0100, Edd Barrett wrote:
> What I take away from this is that: in order to give the "expected"
> Neovim experience, we are going to need to embed the right version of
> LuaJIT into Neovim going forward.
I forgot to add. There is a LuaJIT fork (OpenResty) that ma
Hi,
On Tue, Aug 31, 2021 at 04:35:26PM +0100, Edd Barrett wrote:
> On Tue, Aug 24, 2021 at 03:06:02PM +0100, Laurence Tratt wrote:
> In case anyone is wondering why we don't just build Neovim with LuaJIT:
>
> - LuaJIT isn't as portable, although we could use it only for certain
>arches.
>
>
On Tue, Aug 24, 2021 at 03:06:02PM +0100, Laurence Tratt wrote:
> Please find attached a new port of LuaFFI:
>
> ...
>
> The main reason I've ported this (along with some help from edd@) is because
> neovim is meant to be run with LuaJIT (which includes the FFI module as
> standard) whereas we run
Please find attached a new port of LuaFFI:
This is a library for calling C functions and manipulating C types from
Lua. It is designed to be interface compatible with the FFI library in
LuaJIT (see http://luajit.org/ext_ffi.html). It can parse C function
declarations and struct definitions
