Our great sponsors
-
WorkOS
The modern identity platform for B2B SaaS. The APIs are flexible and easy-to-use, supporting authentication, user identity, and complex enterprise features like SSO and SCIM provisioning.
-
-
-
InfluxDB
Power Real-Time Data Analytics at Scale. Get real-time insights from all types of time series data with InfluxDB. Ingest, query, and analyze billions of data points in real-time with unbounded cardinality.
-
I use mini.surround but they are others like nvim-surround
Apparently that's because I followed this step from the documentation page:
Hmm, I checked. It was planned, and was implemented, but then scrapped, except for the AST parser component of it. That's unfortunate
There is ongoing work around this. Check out https://github.com/ii14/neorepl.nvim
Sorry, but this is not true for almost anyone. That was a bug when it occurred (I believe you are referring to this: https://github.com/NixOS/nixpkgs/issues/128959) but that has been fixed and closed since 0.5 so maybe you are talking about something else. The neovim wiki links this repo https://github.com/nanotee/nvim-lua-guide which says Neovim embeds LuaJIT 2.1.0, which is compatible although distinct from 5.1. Anyone not running LuaJIT (unintentionally) should visit the issues page and see about reporting it. You are correct in that there is a build target for Lua as well as LuaJIT, but unless you specifically set some build flags to force it to prefer building Lua 5.1, it will build LuaJIT. You have to be trying hard to make it do otherwise. Without LuaJIT, Neovim's testing library doesn't even function, as is documented in the CMakeLists.txt.
Sorry, but this is not true for almost anyone. That was a bug when it occurred (I believe you are referring to this: https://github.com/NixOS/nixpkgs/issues/128959) but that has been fixed and closed since 0.5 so maybe you are talking about something else. The neovim wiki links this repo https://github.com/nanotee/nvim-lua-guide which says Neovim embeds LuaJIT 2.1.0, which is compatible although distinct from 5.1. Anyone not running LuaJIT (unintentionally) should visit the issues page and see about reporting it. You are correct in that there is a build target for Lua as well as LuaJIT, but unless you specifically set some build flags to force it to prefer building Lua 5.1, it will build LuaJIT. You have to be trying hard to make it do otherwise. Without LuaJIT, Neovim's testing library doesn't even function, as is documented in the CMakeLists.txt.
