Perhaps I've configured it incorrectly? I had a very old copy of Racer installed which at some point stopped working, so today I'm finally trying to fix it. It's now mostly working, but here's a scenario that doesn't:
I've got a copy of Remacs checked out, and in rust_src/src/base64.rs there is the line
I can use M-. to jump all of the identifiers on this line except make_unibyte_string. For LispObject and from_raw, it jumps correctly to their definitions in rust_src/src/lisp.rs. For encoded and encoded_length, it jumps a few lines up to where those local variables are defined. For make_unibyte_string I expected it to jump to rust_src/remacs-sys/lib.rs, which has the definition on line 1434. This is inside of a local crate, listed in the Cargo.toml file like this:
I've also checked that I can jump to items in the standard library, and to items from the base64 crate, but not to either of the local crates. I've also verified that I can jump to definitions inside these local crates if I'm starting from a file that is already in that crate.
Perhaps I've configured it incorrectly? I had a very old copy of Racer installed which at some point stopped working, so today I'm finally trying to fix it. It's now mostly working, but here's a scenario that doesn't:
I've got a copy of Remacs checked out, and in rust_src/src/base64.rs there is the line
I can use
M-.
to jump all of the identifiers on this line exceptmake_unibyte_string
. ForLispObject
andfrom_raw
, it jumps correctly to their definitions in rust_src/src/lisp.rs. Forencoded
andencoded_length
, it jumps a few lines up to where those local variables are defined. Formake_unibyte_string
I expected it to jump to rust_src/remacs-sys/lib.rs, which has the definition on line 1434. This is inside of a local crate, listed in the Cargo.toml file like this:I've also checked that I can jump to items in the standard library, and to items from the
base64
crate, but not to either of the local crates. I've also verified that I can jump to definitions inside these local crates if I'm starting from a file that is already in that crate.racer-debug shows this racer command:
It also shows that it's executing racer from the rust_src directory, so the Cargo.toml file is right there for it to find.