Busted should run under the same interpreter it was installed with.

[jszakmeister]

Right now, the main busted script is a shell script that expects to find a suitable interpreter on the path. Unfortunately, when using a custom tree for only a specific purpose, such as unit testing in Neovim, you have to add our custom tree to your path or specify it with the -l option. It'd be nice to just run the busted script, and have it use the same interpreter that was used to install it.

FWIW, it seems that both luarocks and moonscript work well in this regard. Maybe the could serve as an example of what busted needs to do?

[Tieske]

I'm not sure this can be accomplished easily. LuaRocks has an extensive install script that handles this. Where Busted is installed using LuaRocks, and installing through a rockspec doesn't allow you to catch that information and write it into some busted config file.

That said, LuaRocks will wrap any Lua scripts in the BIN directory in a shell wrapper script that handles the correct Lua environment. So to make that work, I think the shell script should be rewritten as a Lua script.

This is an example (Windows) from LuaxPL, for the xpllogger Lua script

@echo off
"C:\Program Files (x86)\Lua\5.1\bin\lua.exe" -e "package.path=\"C:\\Program Files (x86)\\LuaRocks\\systree/share/lua/5.1/?.lua;C:\\Program Files (x86)\\LuaRocks\\systree/share/lua/5.1/?/init.lua;C:\\Users\\Thijs\\AppData\\Roaming/luarocks/share/lua/5.1/?.lua;C:\\Users\\Thijs\\AppData\\Roaming/luarocks/share/lua/5.1/?/init.lua;C:\\Program Files (x86)\\LuaRocks\\2.1\\lua\\?.lua;\"..package.path; package.cpath=\"C:\\Program Files (x86)\\LuaRocks\\systree/lib/lua/5.1/?.dll;C:\\Users\\Thijs\\AppData\\Roaming/luarocks/lib/lua/5.1/?.dll;\"..package.cpath" -e "local k,l,_=pcall(require,\"luarocks.loader\") _=k and l.add_context(\"luaxpl\",\"0.2.0-1\")" "C:\Program Files (x86)\LuaRocks\systree\lib\luarocks\rocks\luaxpl\0.2.0-1\bin\xpllogger" %*

Would that satisfy your request?

[jszakmeister]

@Tieske Yes, I believe it would. Unfortunately, my lua-fu is pretty low right now, so I can't say for certain if it's the right approach.

[jszakmeister]

Can we open this issue back up since it's now no longer fixed?

[aktau]

Hey guys, as you might've noticed (or not), a recent LuaRocks upgrade broke some things for us. (I) think this is because something changed on the Busted side. Could you advise? Reference: neovim/neovim#1031

EDIT: could you please re-open if found to be a valid issue?