Has error reporting changed?

[danielo515]

Hello.
I think it is very nice that luasnips validates the snippets when you save the file.
Previously, if I forgot to "consume" a placeholder in a fmt string, I got an error telling me there were one unused placeholder (happens to me more commonly than I want to admit).
However, recently I started to get errors that tell me nothing about why they are failing. Has this changed? Or is it something related to how my neovim instance shows me the errors?

[L3MON4D3]

You mean lua-loaded snippets, right?
The error messages were changed to say something like "loading the file failed: ", but the original error should still be propagated (through ). Does this not happen?

[danielo515]

Yes, sorry if I was not specific enough. I mean the automatic reload of Lua snippets when you save the file. I used to get a concrete error telling me that one placeholder was not con consumed, and that is no longer the case. Also I have noticed the autocommand is setup for *, why not limit it to Lua files? El vie., 18 nov. 2022 8:26, L3MON4D3 ***@***.***> escribió:

…

You mean lua-loaded snippets, right? The error messages were changed to say something like "loading the file failed: ", but the original error should still be propagated (through ). Does this not happen? — Reply to this email directly, view it on GitHub <#660 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARKJWKHATJOCO7PVLJKXIDWI4VQZANCNFSM6AAAAAASEE72MI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[L3MON4D3]

Mhmmm, I'm still getting the full error.

I guess something else is up, what does your error look like?
Regarding the autocommand, (I'm assuming this one), it handles snipmate, vscode, and lua-files. And then it's just easier to do that check whenever a file is saved, than doing it separately for all.

[danielo515]

This is how my error looks like. Very similar to yours, but with subtle details are different, like the line numbers it references (mine is 43 while yours is 63). The only thing missing is the fmt.lua:88 message...

[L3MON4D3]

Ahh, you're on an older version of luasnip. There was a period where we had this shorter error, but it's reinstated now.
(not released though, you'd have to check out master for a bit)

[danielo515]

So, just to be clear, this was previously present (because I saw it on the past) then removed (my current version) and then readded (latest version). Is that right? El dom., 20 nov. 2022 10:20, L3MON4D3 ***@***.***> escribió:

…

Ahh, you're on an older version of luasnip. There was a period where we had this shorter error, but it's reinstated now. (not released though, you'd have to check out master for a bit) — Reply to this email directly, view it on GitHub <#660 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AARKJWMXV6Z4GXH2B7SRKBDWJHUPXANCNFSM6AAAAAASEE72MI> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[L3MON4D3]

Yes: just pass the error through -> specify that the error occured while trying to load one of these files (omitting the specific error) -> also printing the error