Returning Lua errors

[titaniumtraveler]

Is there a way to return lua errors from #[nvim_oxy::plugin]?
As in one that can be catched by pcall?

I tried different combinations of returning Result::Err(), but wasn't able to find a solution.

[noib3]

You can return any value that implements the Pushable trait, which Result doesn't.

What's your use case?

[titaniumtraveler]

But yeah, even if I call it correctly it directly closes again too. (Which makes sense considering I tried some other methods too)

[fusillicode]

Hey, sorry for bothering you but I'm facing the same exact issue, i.e Neovim crashes whenever a function exposed via a [nvim_oxi::plugin] returns an error (tried with both nvim_oxi::Error and anyhow::Error) 😞

My workspace explicitly specifies panic = "unwind" under [profile.release] but apparently it does not have any effect.

Calling Rust functions that returns errors that are exposed via mlua (and invoked with pcall on Lua side) works, i.e. no panic, but with [nvim_oxi::plugin] all returned errors just crashes Neovim. I was thinking about handling all the errors on Rust side but this would require to return some default values to Lua in case of errors. Unfortunately I don't think I can find reasonable defaults in all cases.

Is there something I'm missing 😞

[titaniumtraveler]

Crashes or aborts?
Because that sounds like it just doesn't stop unwinding the stack.
Don't know why it is panicking with the Result::Errors though.

[fusillicode]

Thanks for the quick reply!

Crashes or aborts?

Good question. It seems like it's aborting 🤔
This is the output I get in the terminal when I call the functions that on Rust side returns an anyhow::Error

  1
~   thread '<unnamed>' (45894517) panicked at library/core/src/panicking.rs:225:5:
~                            panic in a function that cannot unwind
~             note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
~                                     thread caused non-unwinding panic. aborting.
~                            %   

For reference this is where I call the Rust function from Lua and this is where the Rust function is defined.

I really feel like I missed some important doc about how the integration is supposed to be implemented and how it supposed work 😞

[titaniumtraveler]

Thanks for the quick reply!

Crashes or aborts?
Good question. It seems like it's aborting 🤔
This is the output I get in the terminal when I call the functions that on Rust side returns an anyhow::Error

  1
~   thread '<unnamed>' (45894517) panicked at library/core/src/panicking.rs:225:5:
~                            panic in a function that cannot unwind
~             note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace
~                                     thread caused non-unwinding panic. aborting.
~                            %   

So both actually lol

I really feel like I missed some important doc about how the integration is supposed to be implemented and how it supposed work 😞

Yeah, no idea either.
I tried it back when I created this issue, but was never able to find a solution.
I guess the only thing I can recommend you is to macro expand the code and goto-definition until you find the actual source of the problem.

As context for what you should probably focus on:

Lua errors work by putting an arbitrary lua value onto the stack and calling lua_error() (the value is what the message is then taken from)
See :h lua-apiError, lua_error() and :h luaL_error().
(Having the official lua reference in neovim was the best idea the devs ever had!)