From: Jack Hill <jackhill@jackhill.us>
To: guix-devel@gnu.org
Subject: neovim and luajit?
Date: Fri, 31 Jul 2020 16:26:58 -0400 (EDT) [thread overview]
Message-ID: <alpine.DEB.2.21.2007311601410.4809@marsh.hcoop.net> (raw)
Hi Guix,
I'm wondering why we use Lua 5.1 instead of LuaJIT for neovim? It seems
that upstream prefers LuaJIT given the non-default configure flag we
use[0] and their FAQ[1].
I don't have an opinion either way. I'm learning about neovim today, and
am curious how we arrived at our configuration.
[0] https://git.savannah.gnu.org/cgit/guix.git/tree/gnu/packages/vim.scm?id=96a655a77bb087397a9436391e472c36ff0a2ec2#n647
[1] https://github.com/neovim/neovim/wiki/FAQ#why-embed-lua-instead-of-x
Best,
Jack
next reply other threads:[~2020-07-31 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-31 20:26 Jack Hill [this message]
2021-04-22 5:33 ` neovim and luajit? Jack Hill
2021-04-25 7:15 ` Efraim Flashner
2021-04-25 9:23 ` HiPhish
2021-04-29 22:28 ` Jack Hill
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.2007311601410.4809@marsh.hcoop.net \
--to=jackhill@jackhill.us \
--cc=guix-devel@gnu.org \
/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).