mirror of https://github.com/bfredl/nvim-luadev
You cannot select more than 25 topics
Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
b1f8e58ea5
coroutine.yield() -> schedule coroutine.yield("blaa") -> print + schedule coroutine.yield(function(thunk) dolater(thunk) end) -> resume later |
1 year ago | |
---|---|---|
lua | 1 year ago | |
plugin | 2 years ago | |
LICENSE | 6 years ago | |
README.md | 3 years ago |
README.md
nvim-luadev
This plugins set up a REPL-like environment for developing lua plugins in Nvim.
The :Luadev
command will open an scratch window which will show output from executing lua code.
Use the folllowing mappings to execute lua code:
Binding | Action |
---|---|
<Plug>(Luadev-RunLine) |
Execute the current line |
<Plug>(Luadev-Run) |
Operator to execute lua code over a movement or text object. |
<Plug>(Luadev-RunWord) |
Eval identifier under cursor, including table.attr |
<Plug>(Luadev-Complete) |
in insert mode: complete (nested) global table fields |
If the code is a expression, it will be evaluated, and the result shown with
inspect.lua
. Otherwise it will be executed as a block of code. A top-level
return
will cause the returned value to be inspected. A bare nil
will not
be shown.
Global print()
is also redirected to the output buffer, but only when executing
code via this plugin. require'luadev'.print(...)
can be used to print to the
buffer from some other context.
Planned features:
- autodetect expression vs statements
- Fix
inspect.lua
to usetostring()
on userdata (done on a local copy) - completion of global names and table attributes (WIP: basic implementation done)
- make
<Plug>(Luadev-Run)
a proper operator - solution for step-wise execution of code with
local
assignments (such as a flag to copy local values to an env) - tracebacks
- interactive debugging
- debug helpers for async callbacks (WIP)