From: gbrlsnchs <gbrlsnchs@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: neovim: update to 0.7.0.
Date: Wed, 20 Apr 2022 20:27:19 +0200 [thread overview]
Message-ID: <20220420182719.SfLKVTQW5xDyz2mCzcAI6iYgb6XfUZWONE7DVX9nAgY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36704@inbox.vuxu.org>
[-- Attachment #1: Type: text/plain, Size: 567 bytes --]
New comment by gbrlsnchs on void-packages repository
https://github.com/void-linux/void-packages/pull/36704#issuecomment-1104286148
Comment:
> @gbrlsnchs can you confirm that after compiling with `-DCOMPILE_LUA=OFF`, neovim actually works on arm64 or not? I don't the hardware to test it.
I'm also unable to test it right now, unfortunately. I just had it compiled for future usage.
Still, I don't think that breaks anything; it seems to turn off a Lua optimization where Neovim's Lua API code is compiled ahead of time instead of interpreted during runtime.
next prev parent reply other threads:[~2022-04-20 18:27 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-15 12:48 [PR PATCH] " kartikynwa
2022-04-15 13:19 ` kartikynwa
2022-04-15 13:20 ` [PR PATCH] [Updated] " kartikynwa
2022-04-15 13:23 ` kartikynwa
2022-04-15 16:22 ` kartikynwa
2022-04-15 16:22 ` kartikynwa
2022-04-17 17:04 ` [PR PATCH] [Closed]: " kartikynwa
2022-04-17 18:00 ` kartikynwa
2022-04-18 4:32 ` kartikynwa
2022-04-18 8:54 ` Johnnynator
2022-04-18 9:47 ` kartikdc
2022-04-18 9:48 ` kartikdc
2022-04-18 11:13 ` kartikynwa
2022-04-18 11:17 ` kartikynwa
2022-04-18 19:22 ` gbrlsnchs
2022-04-20 4:01 ` kartikynwa
2022-04-20 15:30 ` LinArcX
2022-04-20 16:12 ` kartikynwa
2022-04-20 18:27 ` gbrlsnchs [this message]
2022-04-21 0:50 ` CameronNemo
2022-04-23 12:03 ` LinArcX
2022-04-23 12:04 ` LinArcX
2022-04-21 15:44 [PR PATCH] " siduck
2022-04-21 15:47 ` Chocimier
2022-04-21 15:55 ` siduck
2022-04-22 19:08 ` ram02z
2022-04-23 2:44 [PR PATCH] " thatboyjake
2022-04-23 2:49 ` classabbyamp
2022-04-23 3:12 ` thatboyjake
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20220420182719.SfLKVTQW5xDyz2mCzcAI6iYgb6XfUZWONE7DVX9nAgY@z \
--to=gbrlsnchs@users.noreply.github.com \
--cc=ml@inbox.vuxu.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.
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 NNTP newsgroup(s).