Valentino Volonghi
Valentino Volonghi
Adding to the +1 here... Given the number of unittests that break I'll probably just go with a patched version of beaker with this changed and no particular care for...
I have submitted a PR https://github.com/bbangert/beaker/pull/186 to deal with this. A lot of tests break for unrelated reasons (like missing AES library or missing client of a particular backend) but...
Looks like all tests pass.
Anyone here?
I also have this issue but not just from brew, even when I build from source. And what is more strange is that if I run `open Neovide` from command...
 It could very well be a security approval thing, but I've already approved neovide security before, and apparently the TCCD daemon is killing neovide due to some security...
Even adding neovide to the "development tools" security policy in macOS, explicitly adding it to "Full Access" for disk, and a few more groups, I get rid of the errors...
that was it, solved it, thanks!
As a brand new user, the lack of logging related to the configuration options that I specified is confusing. For example now I'm in the position where the CHANGELOG wasn't...
Hey, you can see the auto import completion in action here: https://github.com/rust-analyzer/rust-analyzer/pull/6553 and I think the primary way to enable it is to use `textDocument/completion` with additional properties like seen...