Comments (9)
Thank you guys, this helped a lot!
commit 8aa90a94bcdddde7fd17a21892c3fba1d71c7f5a (HEAD -> master, origin/master, origin/HEAD)
Author: Shadorain <shadow@Shadowraith>
Date: Mon Nov 8 10:41:10 2021 -0500
#4: removed RLS now just use rust-tools.nvim which auto initializes rust-analyzer; faster and cleaner
from shadovim.
Hmm.... thank you for bringing this up. I originally was going to just use rust-analyzer (because of rust-tools) but I found that paired with RLS I got some good lsp diagnostics and whatever else.
I actually had the same problem when trying to remove RLS so I am assuming that RLS is controlling the rust source for nvim-cmp (completion) so I just kept RLS because I get good completions. Rust-analyzer might provide better ones though, that is a good point, I should look into that more.
If you find anything more let me know as well 😁
Thanks!
from shadovim.
I think I made some progress, disable procMacro for rust-analyzer in your rust-tools settings, and also remove rust-analyzer in your LSP initliaization as rust-tools adds it in anyway, let me know if that works for you ?
from shadovim.
Yeah def remove rust analyzer from here and remove this whole block and it should be fine
from shadovim.
Yeah def remove rust analyzer from here and remove this whole block and it should be fine
Oh dang, you made rust-tools.nvim didn't ya? I'm assuming something else would handle the rust_analyzer lsp initialization then if I'm removing it from there?
from shadovim.
I think I made some progress, disable procMacro for rust-analyzer in your rust-tools settings, and also remove rust-analyzer in your LSP initliaization as rust-tools adds it in anyway, let me know if that works for you ?
Ah I see, you are right, rust-tools does it for me, don't need it twice. That is smart. I'll try that!
from shadovim.
I'm pretty sure you don't need to disable proc macros as well.
Also you put it in the tool opts where it does nothing
from shadovim.
I'm pretty sure you don't need to disable proc macros as well. Also you put it in the tool opts where it does nothing
The latest rust update broke proc_macros in rust-analyzer, try it out !
from shadovim.
I'm pretty sure you don't need to disable proc macros as well. Also you put it in the tool opts where it does nothing
True, didn't notice this will update
from shadovim.
Related Issues (1)
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from shadovim.