Closed zino23 closed 4 days ago
Thanks for your report and PR.
By the way, do you use a .rustfmt.toml locally? The code is not formatted by rustfmt, so when I save the file and the auto-formatting tool is run, the changes are all over the place. Just my opinion that if the code is correctly formatted, it will be easier for others to contribute to this project :). Do you mind formatting the code or accepting a PR that does the formatting? I am ok to create such a PR :).
Thanks you for your offer. No I didn't use rustfmt locally. Personally I'm not a big fan of enforced formatting rules. I believe that a programmer's formatting choice for some code (indention etc.) may contain info about the codes' structure or logic. Also, this repo is relatively small regarding both repo size and number of contributors anyway. So I would like to keep it as it for now. :)
Thanks for your reply. As someone often annoyed by Go's dogmatic code formatting, I totally understand your choice :).
If something bad happens during running the lsp server, e.g. the lsp server is not in
$PATH
, the backtrace looks like this:It isn't obvious what went wrong, and we don't even know which line in
emacs_lsp_booster::app::run_app_forever
specifically is the culprit.The fix is easy. Simply attach a context with
<anyhow::Result as anyhow::Context>::with_context
method.Afterwards, the error looks like this:
By the way, do you use a
.rustfmt.toml
locally? The code is not formatted byrustfmt
, so when I save the file and the auto-formatting tool is run, the changes are all over the place. Just my opinion that if the code is correctly formatted, it will be easier for others to contribute to this project :). Do you mind formatting the code or accepting a PR that does the formatting? I am ok to create such a PR :).Thx for your great project!