Re: Introducing luavm - Lua Version Manager
[
Date Prev][
Date Next][
Thread Prev][
Thread Next]
[
Date Index]
[
Thread Index]
- Subject: Re: Introducing luavm - Lua Version Manager
- From: Andrew Starks <andrew@...>
- Date: 2016年6月06日 22:16:39 +0000
Yes. It would be much clearer to have Lua-env, which will be super easy to distinguish from luaenv. ;) sarcastic comments are mean but I hope you take my point anyway
You got 4 votes for uselua and you are free to name it what you wish. This goes from something universally confusing to very confusing, at least from a search perspective.
-Andrew
Hello everyone!
So in the past few days I've made some changes:
- Removed the BIN directory, luavm no longer plays with links
- luavm exists as a function instead of a script: Multiple sessions can have different environments configured
- Environment maintained through environment variables
- LUA_PATH and LUAC_PATH set after using a particular version of luarocks
-
Added functionality to set/unset default versions of Lua, LuaJIT and
Luarocks. Default versions will automatically be set in a fresh terminal
session. See the README for details.
TODO:
- Testing - Very much needed!
- Change name from 'luavm' to 'lua-env'
-
Update all function names inside luavm and bind them to a particular
namespace, like lua-env_<func>: This is because the entire script
is loaded in bash and its functions will be present and overwrite
existing ones.
And I find luaenv much better. There's already a project by this name so probably I will be shifting to lua-env.
Comments and suggestions are appreciated.
Thanks!
On Fri, May 27, 2016 at 4:07 PM, Peter Hickman
<peterhickman386@googlemail.com> wrote:
Perhaps luame (as in "Lua Me") for Lua machine environment, additionally "le" is not a standard unix command so we can save ourselves much typing :)