From: Jack Hill <jackhill@jackhill.us>
To: HiPhish <hiphish@posteo.de>
Cc: guix-devel@gnu.org
Subject: Re: neovim and luajit?
Date: Thu, 29 Apr 2021 18:28:45 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2104291825240.2109@marsh.hcoop.net> (raw)
In-Reply-To: <5704271.lOV4Wx5bFT@titan>
On Sun, 25 Apr 2021, HiPhish wrote:
> I just want to add my 2 cents to the discussion. Officially Neovim supports only
> Lua 5.1 as its extension language according to the manual (`:h lua-intro`):
>
>> The Lua 5.1 language is builtin and always available.
>
> Using LuaJIT allows the use of some extensions to Lua 5.1, but plugins relying
> on this functionality are strictly speaking non-portable because not all users
> might have them. I don't know if it is possible with Guix, but the ideal
> solution would be to use LuaJIT where available and fall back on Lua 5.1
> otherwise.
Yes, I believe that this would be possible, but based on what Efraim says
it may not even be needed.
> On Sunday, 25 April 2021 09:15:57 CEST Efraim Flashner wrote:
>>
>> Our copy of luajit supports aarch64 so I don't think that's a problem.
>> (Last I checked) Debian has a patch to replace powerpc support with
>> 64-bit ppc support. I'd go ahead with the change if that's the direction
>> that neovim is going and let the powerpc64le people decide between using
>> lua5.1 or just removing lua support on a per-architecture basis for
>> ppc64le.
That does sound promising.
Therefore, I've proposed switching to luajit in #48109
https://issues.guix.gnu.org/48109
Thanks for your replies!
Jack
prev parent reply other threads:[~2021-04-29 22:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 20:26 neovim and luajit? Jack Hill
2021-04-22 5:33 ` Jack Hill
2021-04-25 7:15 ` Efraim Flashner
2021-04-25 9:23 ` HiPhish
2021-04-29 22:28 ` Jack Hill [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.DEB.2.21.2104291825240.2109@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
--cc=hiphish@posteo.de \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).