-
Notifications
You must be signed in to change notification settings - Fork 11
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
automatic imports stopped working #61
Comments
Which lsp backend do you use? |
rust-analyzer |
just want to confirm that i've observed same issue on my side as well; invoking using rust-analyzer (tagged as |
Ah sorry I meant which LSP client is used inside of emacs, lsp-mode or eglot, or something else? |
I'm using |
btw, not sure whether that helps but I observed some other problems as well that make the overall experience way less smooth that it was just a couple of weeks ago ... summarized them here: https://users.rust-lang.org/t/recent-problems-with-emacs-rustic |
Could you try to log the communication between Then it should be possible to figure out if it happens because of |
@Erk- what would I be looking out for ? |
One of the techniques which I use to debug this kind of issue is follow this:
|
The request/response which inserts the imports is |
the items look like this:
|
@the-drunk-coder Does |
Also, make sure that |
Added them to my |
yes, they look like this:
(it's from a subsequent attempt, not the same one as above) But it's strange that all the info needed (additional imports, etc) already seems to be present in the request .. |
Looks like an upstream issue: rust-lang/rust-analyzer#18363 |
Hi,
I've been using rustic mode for a while now, but today I noticed that automated imports stopped working.
That is, when starting to type a type name, the options show up, but if I hit "return" or "tab", nothing happens, when in the past the required type would be added automatically.
Not sure whether that's a rustic issue, but maybe someone can point me in the right direction?
Best,
N
The text was updated successfully, but these errors were encountered: