-
Notifications
You must be signed in to change notification settings - Fork 67
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
Support Cargo project with workspace #51
Comments
Hi, I don't seem to be having this issue. When I select the error link on the compilation screen it takes me to the proper file / location. |
I updated the comment. This issue occurs for nightly Rust toolchain ( |
Yes, it is new rustc problem. If you compile inside crate "CrateA" that part of workspace, with new |
This should be fixed with #56 |
See sample project: https://github.com/nebgnahz/cargo.el-workspace
For a project with workspace, Cargo returns issue relative to the workspace root
directory.
cargo.el
instead find the directory withCargo.toml
, which can bedifferent. When these two project root directory differ, Emacs compilation mode
fails to find the correct file path. To a user, Emacs is unable to jump to the
error location and a window prompt is open.
In the linked sample project, the file in
add-one/src/lib.rs
has a typox1
. When onedoes a
cargo build
, we see the following compilation log:And Emacs wants to open a non-existant file
~/repos/cargo.el-workspace/add-one/add-one/src/lib.rs
.cargo.el
finds filerelative to
~/repos/cargo.el-workspace/add-one/
while Cargo~/repos/cargo.el-workspace/
.Note: this wasn't an issue for old Cargo/
cargo.el
. I did a package update today and start experiencing this issue.Edit:
The text was updated successfully, but these errors were encountered: