search

lapce / lapce-rust

Apache License 2.0
80 stars 26 forks source link

Cargo check not allowing all features #16

Open Seven0492 opened 1 year ago

Seven0492 commented 1 year ago

Lapce Version

0.2.4

System information

Arch Linux kernel version: 5.15.81-1-lts

Describe the problem

I was working on a Rust project, I had changed it to a library model for ease of organization.

But then I made the GUI a feature which is not compiled by default.

And then the only thing showing up now were syntax highlighting, the only exception was compile-time errors, warnings were ignored.

I have to add the GUI feature to the default temporarily so everything works has expected each time I want to work on it. (And I have to remember to remove it from the default in the next git push)

Describe the bug

Adding the cargo check flag --all-features or --features '*' show me an error on restart and ask me to check the server logs...

But the thing is, the server logs of what? How am I supposed to magically just 'know' where that log file is?

And the features flag should have worked, this is clearly a bug/error in the Rust plugin.

Problem resumed

Cargo check gives an error when passing the --all-features flag in the Rust plugin configuration.

Lack of information of what server (Probably rust-analyzer or cargo) is the logs from and where the logs even are.

Seven0492 commented 1 year ago

Feature suggestion

Adding a list of features (Or a simple check mark) to enable and disable individual features or non-default features.

Seven0492 commented 1 year ago

Maybe there should be a rust plugin wiki? (I'd be willing to help writing it, though I'm still a beginner in Rust)

Seven0492 commented 1 year ago

So, rephrasing, is there any way I can help?

hbina commented 1 year ago

Have you checked ~/.local/share/lapce-stable/logs/? This is where logs are written to.

hbina@akarin ~/g/sqlite (master)> ls ~/.local/share/lapce-stable/logs/
20230104-071058.log  20230112-174008.log  20230117-103551.log  20230117-110441.log  20230118-174837.log  20230119-141826.log  20230121-172807.log  20230122-114148.log  20230122-124848.log
20230105-112828.log  20230113-105730.log  20230117-103921.log  20230117-110507.log  20230118-175032.log  20230119-145011.log  20230121-173928.log  20230122-114534.log  20230122-124904.log
20230111-130216.log  20230114-161525.log  20230117-103931.log  20230117-110759.log  20230118-180847.log  20230119-145619.log  20230122-071657.log  20230122-114854.log
20230111-135642.log  20230117-095636.log  20230117-104018.log  20230117-110911.log  20230118-180902.log  20230119-152246.log  20230122-080405.log  20230122-115837.log
20230111-195518.log  20230117-095731.log  20230117-104905.log  20230117-193652.log  20230119-124825.log  20230119-195033.log  20230122-091918.log  20230122-120902.log
20230111-195812.log  20230117-100655.log  20230117-105652.log  20230118-131122.log  20230119-141525.log  20230120-163222.log  20230122-092020.log  20230122-121351.log
20230111-195848.log  20230117-101037.log  20230117-110131.log  20230118-133229.log  20230119-141747.log  20230121-171114.log  20230122-092450.log  20230122-121741.log

For any issues related to rust LSP itself, you should query https://github.com/rust-lang/rust-analyzer since we this plugin is just a small shim that starts and talks to the LSP.