Open sharpchen opened 2 months ago
Hmm yeah, the tomfoolery between Lua_original and Lua_nvim was originally intended to prevent unexpected failures for small snippets (trying vim.print, and trying native lua code that could behave differently in nvim).
The cause of the issue here is probably that the snippet produced an error also in the Lua_nvim interpreter, which disqualified it as a fallback, and returned the original error instead.
The solution for you is probably to add "Lua_nvim" to your configuration (the selected_interpreters
key), to force the use of Lua_nvim for every lua snippet
The solution for me is to communicate more effectively what happened when such fallbacks occur, especially when they're not successfull.
Describe the bug Same as title
To Reproduce
vim.print('foo')
just works.Screenshots
Environment:
{ machine = "x86_64", release = "5.15.153.1-microsoft-standard-WSL2", sysname = "Linux", version = "#1 SMP Fri Mar 29 23:14:13 UTC 2024" }