Not warning about the lack of rust-analyzer
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 87
- Forks
- 30
- PR merge metrics
- No merged PRs in 30d
Description
Lapce Version
0.2.4
System information
Arch Linux kernel version: 5.15.81-1-lts
Describe the bug
Autosuggestion not working when dealing with some crates (In Rust)
Syntax highlighting just not showing in some cases
The problem?
I fixed it, it was that rust-analyzer was not installed.
The problem with that?
I only found out when I was trying to switch to Helix,
and had to install rust-analyzer via rustup and do a symlink to a directory in PATH from the analyzer binary.
What I suggest?
Adding a prompt warning about the lack of rust-analyzer like other mainstream IDE's instead of just being silently faulty.
Or even installing it automatically.
I had no idea what was wrong with the Rust plugin, I thought the 'sub-par' (Used lightly) performance of its highlighting was 'normal', until I added the missing part by accident and made it work like a champ!
I can now use Lapce coding in Rust without reservation and have had a fantastic experience so far, keep it up!
This is a wonderful project that was badly needed (The Rust plugin was needed too :P).
I just want other people coming to Lapce for a good Rust environment not be discouraged by its problem when it lacks rust-analyzer.
I made this issue since I think this is something that should me made aware to the user.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating the Rust plugin's initialization and its handling of rust-analyzer availability; compare the requested warning with the alternative of automatic installation. Done should include a clear user-facing response when rust-analyzer is missing and coverage for that condition.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- developer-experience, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100