Sibi Prabakaran

@condy0919 Thanks, I checked `no-byte-compile` and it's already set `nil` for me. I did what you mentioned and this is the error message I'm getting: ``` Company backend ’company-clang’ could...

> Install clang or open an elisp file since lsp is in prog-mode-hook. Sure, I installed `clangd` and nothing happened. This is what I saw in my messages buffer: ```...

> I'm not understanding what "clean install" means, I don't think this is true. I have seen others cleaning it up like this which made it work: `rm -rf ~/.emacs.d`...

If someone wants to send a patch using `lsp-get`, I would be happy to review. I don't use doom emacs, so probably I could be mis-understanding how things work there...

@JacobJanzen Is that bug reproducible to you when you do lsp-start-plain ? > I'll open an issue with Doom Emacs to update lsp-mode. Changing the pin to the latest version...

I think there are two types of generators we have: - Yaml based ones which is self contained. - Third party one which relies on some web service. Faker developers...

> I don't know if it make any sence to try to eager load and parse all yaml files if the gem is eager loaded. The alternative is to parse...

I have written some details on how I made the Haskell fakedata (which uses the same yaml file) faster here: https://psibi.in/posts/2019-09-23-fakedata-perf.html IIRC, the overhead involved was in parsing the yaml...

This behavior is also reproducible with the emacs's lsp-mode.

I have just downgraded to 1.11.0 as an workaround currently.