Skip to content
This repository has been archived by the owner on Dec 8, 2020. It is now read-only.

racer crash when there is an empty space in path on windows #218

Closed
BusyJay opened this issue Apr 29, 2017 · 5 comments
Closed

racer crash when there is an empty space in path on windows #218

BusyJay opened this issue Apr 29, 2017 · 5 comments

Comments

@BusyJay
Copy link

BusyJay commented Apr 29, 2017

Version of VSCode: 1.11.2
Version of the extension: 0.3.14
OS: Windows 10

Description:

When there is a space in path, racer crashes.

Output of the "Rust logging" channel:

WARNING: Legacy Mode Manager: CompletionManager: restart
DEBUG: Legacy Mode Manager: CompletionManager: stop
DEBUG: Legacy Mode Manager: CompletionManager: start: enter
DEBUG: Legacy Mode Manager: CompletionManager: start: racerPath=C:\Users\user name\.cargo\bin\racer.EXE
DEBUG: Legacy Mode Manager: CompletionManager: start: ENV[RUST_SRC_PATH] = C:\Users\user name\.rustup\toolchains\nightly-2016-12-19-x86_64-pc-windows-msvc\lib\rustlib\src\rust\src

Related issue: nodejs/node#7367
There is no workaround currently, because path always gets stripped by FileSystem.findExecutablePath.

@KalitaAlexey
Copy link
Member

@BusyJay
Copy link
Author

BusyJay commented Apr 29, 2017

Sorry not making my point clear. What I mean is that we can't quote the path in configuration to make it recognized when spawning the racer process. I did get it working by specified a new path without any space in it.

@KalitaAlexey
Copy link
Member

I got your point.
I showed you a workaround.

@TheRealHnefi
Copy link

This issue happens with a fresh install of vscode-rust while letting it install all related tools through VSCode, if the user path on Windows has a space in it.

I've tried to manually set rust.rustLangSrcPath and rust.racerPath to symlinks without spaces, but it seems they have no effect. What configuration am I supposed to change so that I can change what paths are used when invoking racer?

@KalitaAlexey
Copy link
Member

@TheRealHnefi,
You changed the correct parameters.
It should work.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants