emacs-lsp-booster icon indicating copy to clipboard operation
emacs-lsp-booster copied to clipboard

Emacs LSP performance booster

Results 20 emacs-lsp-booster issues
Sort by recently updated
recently updated
newest added

Have you ever considered moving the advice content to a package for easy install/setup? that would make simpler to configured in lsp-mode and maybe we could ship it in doom-emacs...

LSP booster works great for me locally. I am wondering if there are any plans to get this working over tramp, specifically over SSH or into a docker container. If...

I tested serde_json, sonic_rs and simd_json in the benchmark, and simd_json outperformed the other two. Therefore I will submit a new PR and close #26

Fixes https://github.com/blahgeek/emacs-lsp-booster/issues/31 This adds experimental support for TCP transport. It connects to language server using TCP, do the translation, and also serve from TCP itself. Using this mode with lsp-mode...

Thanks for this awesome package @blahgeek I've noticed that it doesn't apply to GDScript since it doesn't use the `stdio` ```elisp (lsp-register-client (make-lsp-client :new-connection (lsp-gdscript-tcp-connect-to-port) :activation-fn (lsp-activate-on "gdscript") :server-id 'gdscript))...

UTF-8 characters are improperly handled, resulting in raw bytes being sent to Eldoc buffers. See the discussion [here](https://www.reddit.com/r/emacs/comments/1p0x92h/comment/npp1oba/) for more information. This issue is not specific to any particular language...

There are more things that could be improved here, as per `cargo clippy`.

This ought to be a bit faster. Further progress might be possible by using borrowed strings in `LispObject`. (Or using `ordered_float` instead of allocating strings for floats.)

This link in the README doesn't work: https://github.com/blahgeek/emacs-lsp-booster/actions/runs/7416840025/job/20182439682#step:5:142 I get a 404

I think `lsp-booster--advice-json-parse` in README is potentially problematic, particularly: `(funcall bytecode)`. Advising every call of `json-read` or `json-parse-buffer` may lead to unwanted code execution that way. **Server side:** For example...