Open Bkeinn opened 1 year ago
What is the rust version you are using (rustc --version
) ?
Also, what happens if you do cargo build
from your project in a terminal ?
rustc 1.66.0 (69f9c33d7 2022-12-12)
cargo build:
Compiling learn_async v0.1.0 (/home/heimchen/Documents/Programing/Rust/learn_async)
Finished dev [unoptimized + debuginfo] target(s) in 1.08s
LSP seams to work in vim
Ah, I see. Looking into this further - this could be a flycheck issue:
Can you see if installing and configuring flycheck-rust would resolve the issue: https://github.com/flycheck/flycheck-rust ?
Flycheck-rust was already installed. I reinstalled and nothing changed.
Did you also have this in your init.el
:
(with-eval-after-load 'rust-mode
(add-hook 'flycheck-mode-hook #'flycheck-rust-setup))
If that doesn't work, then I would suggest you to try re-installing all the packages and check again.
If even that doesn't work, probabaly can make your project public so that I can test your project directly (A new sample project works fine for me in both rust-mode as well as rustic) ?
If you want to use doom-emacs you should stick with the doom approach. rust-mode(only indirectly through rustic) and paradox are not used by doom. I would suggest that you try to get a minimal doom-emacs config working and then start adding additional config options. There are lots of tutorials that help you with it.
Another possibility would be to try emacs without doom-emacs. You can take a look at https://github.com/rksm/emacs-rust-config and try if it works for you. Configs like these(and of course doom) are used by many other people so the chance is good that it should be working for you, if you stick to the defaults.
I am very new to emacs and are trying to set it up for rust development. When I am in a *.rs file and M-x rust-mode this error pops up:
I updated cargo rust with:
rustup update
and updated all my packages with paradox. Emacs: Doom OS: Fedora config.el:(rustic and lsp mode both don't work either but I am starting with rust-mode, because it told me to open a new issue)