-
Notifications
You must be signed in to change notification settings - Fork 36
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
Autocomplete doesn't work #129
Comments
The completion only work when you press Tab, maybe you're expecting it to show up automatically ? (not currently implemented) If that's not the case, Just to double check you should have Then I guess the second thing to check is does a rust-analyze process gets created when you run irust ? you can check after starting it , in top or similar utility. If that's the case , I guess the next step to add some dbg! here https://github.com/sigmaSd/IRust/blob/master/crates/irust/src/irust/ra/rust_analyzer.rs |
That's weird, rust analyzer seem to have spawned so it's an issue in the cominucation for some reason Can you dbg! completion_request line, character here https://github.com/sigmaSd/IRust/blob/master/crates/irust/src/irust/ra/rust_analyzer.rs#L157 after you press tab (while having some input to complete) If you're a flatpak user , can you try the flatpak just for testing (link in the readme) |
Also you should comment this line out to see if the lsp server is complaining https://github.com/sigmaSd/IRust/blob/master/crates/irust/src/irust/ra/rust_analyzer.rs#L28 |
By this, i could saw the rust-analyzer was not installed and after installing it, completion works. However unlike evcxr, only the functions are autocompleted and the variables are not auto completed. I see there is an option in rust-analyzer called "rust-analyzer.completion.privateEditable.enable", so I tried setting that in rust_analyzer.rs but still getting filled only with the functions, if it possible to fill the variables on tab? |
you need to redirect stderr to make sense of the output |
Thanks, It's working for me also. Seems I have missed clean build. |
I also can't get the autocomplete to work. Using it in windows terminal / powershell. The readme says the config is at "Win: C:\Users$USER\AppData\Roaming/irust/config.toml" but there was no config file there at all so i manually made it and fill it with the default config but changed "enable_rust_analyzer = true" and re-run but no change, pressing tab or shift tab does nothing. |
Hello, the config should be created by default, so I think you modified the wrong location You need to enable rust analyzer there like you already tired, also make sure that |
I'm really not looking in the wrong place, i even deleted the whole folder and cargo uninstalled/reinstalled and upon running irust the irust folder appears in /Roaming with irust_prelude and themes folders inside but there is never a config.toml made even after i run "irust --default-config" Running rust-analyze from console would give "error: Unknown binary 'rust-analyzer.exe' in official toolchain 'nightly-x86_64-pc-windows-msvc'" so i ran "rustup component add rust-analyzer" and it did install, but irust still does not have autocomplete or a config file (i did even search whole system for a config and there isn't any new config.toml files made) |
I seem to have broken that in a recent release, I pushed a new version 1.71.25 can you test that one Make sure to run irust, then close it, then enable rust analyzer in the generated config.toml I think you already made sure rust-analyzer works in the cli, so in theory it should be enough, when you hit tab you should see suggestions now, If it still doesn't work check the task manger when irust is running to see if it did spawn rust-analzer |
Cheers can confirm new version has working autocomplete :) |
I have the latest version of irust, rust_analyzer and everything work fine in Helix and VSCode, but the autocomplete doesn't work in irust in kitty or default ubuntu terminal. I have the rust_analyzer config flag set to true. How can that be debugged ?
The text was updated successfully, but these errors were encountered: