Top level error handling

[joaomendoncaa]

Feature Description

we should be more cognizant of error handling in autocmds. every time there's a problem with Blink's setup it explodes in your face, be it an error in installation, or a problem with some provider/source - we should be able to at least have an option to suppress these errors or make them more subtle (maybe just logs?).

especially in TextChangedI's case, neovim stays unusable - it's even hard to exit the damn thing 😄

[joaomendoncaa]

we could simply wrap all these autocmd callbacks with a pcall HOF util function, write errors to logs, and/or notify the user based on a config parameter

[itsthomashere]

we could simply wrap all these autocmd callbacks with a pcall HOF util function, write errors to logs, and/or notify the user based on a config parameter

I ran into this for quite sometime and it was really annoying too since it basically blocked neovim.

[smjonas]

I agree, trying to update my config to fix the issue was very annoying as the error appeared on every keystroke. In the code, I noticed that you're using Lua's error function. I would recommend using something like vim.notify_once instead which will only show the error once.