Avoid misconfiguration and try to help racer to find a Cargo.toml

[alkama]

• Rewrite the README file so that it warns for misconfiguration and is more structured.
• Do not launch completion if the configuration is obviously wrong.
• Check that "racer.racerBinPath" points to a valid file.
• Check that "racer.rustSrcPath" points to a valid directory.
• Rescan the current project path for each completion because it can change during the editor's life.
• Write the temporary file directly in the project path to help racer locate a related Cargo.toml.
• Clean temp files immediately after racer returns.

[alkama]

If it didn't mess it, it should be valid for a v0.12 and should fix #26

[edubkendo]

I don't understand what you mean by, if it didn't mess it?

[alkama]

I just meant that it should work fine! (but that's unless I missed a corner case, we're human after all)

[edubkendo]

:)

[edubkendo]

Sorry, messed up the publishing and skipped a minor version but it's published.

[alkama]

Cool! Thanks!

What remains now is to be more vocal about misconfigurations.
For now the errors go to the console and it seems Atom doesnt warn anymore about errors in the console. I'll see if I can use a message panel instead.

Maybe later I'll see if I can port a "go to definition" and/or snippet feature from racer.

[cart]

Unfortunately these changes did not fix completion from external crates using Cargo.toml or completion from files within the project. Are these completions working for you now? The only completions I get are from the current file and rust/src. What configurations do you have? I am running Linux 4.0.5, gnome-shell 3.16, Atom .207, rust nightly (as of today), and current racer.

[alkama]

Hum, I'm on OSX. Can you check if racer is working correctly in isolation?
It should be fairly easy to mimic what atom-racer is doing using a commandline and see if racer responds correctly.

something like:
RUST_SRC_PATH=[RUST_SRC]:[ATOM_PROJECT_ROOT] [PATH_TO_RACER]/racer complete [NUM_ROW] [NUM_COL] [ATOM_PROJECT_ROOT]/[CURRENT_INCOMPLETE_FILE]

Because that's basically what we are submitting and just using the results.

If it doesn't work, it's probably something to issue and debug at racer instead :)

Dumb exemple

for:

• an atom project in /home/me/rusttest
• with rustc source code in /home/me/rustc-1.0.0/src/
• and racer installed in /usr/local/bin/
• given a file to complete being /home/me/rusttest/src/main.rs

fn foo() {
    ;
}
fn main() {
    f
}

the command would be:
RUST_SRC_PATH=/home/me/rustc-1.0.0/src/:/home/me/rusttest /usr/local/bin/racer complete 5 2 /home/me/rusttest/src/main.rs

Note: the "2" is because i'm using tabs which account for 1 character (the markdown formatter converts that to spaces and dont give justice).

[cart]

I get cargo and project file completions when I run racer manually using the format you outlined. Now that I know what works, I will experiment with atom-racer and see if I can get something working.

[alkama]

Excellent :)
Hope you'll spot what's wrong.