I build packages personally, and I don't use rustup. It should search the PATH instead of bailing, and have a config to set the RLS executable path if it makes sense.
ishitatsuyuki
All 8 comments
Seems the config option already exists, but it's completely undocumented.
ishitatsuyuki
on 12 Aug 2017
@ishitatsuyuki which config option did you use to achieve this?
beefsack
on 19 Aug 2017
"rls.path"
ishitatsuyuki
on 19 Aug 2017
Thanks, worked a treat. Confirmed it worked by setting it to an invalid path and it failed to start.
beefsack
on 19 Aug 2017
Is there a reason that rls.path is not documented?
lily-mara
on 8 Feb 2018
Is there a reason that rls.path is not documented?
It is only meant for RLS developers to use, and it is documented in the developer docs for the RLS
nrc
on 11 Feb 2018
@nrc Can you consider documenting this? I don't use rustup but instead create packages on myself, so the rustup integration isn't an option for me.
ishitatsuyuki
on 4 Apr 2018
Sure, I guess it would be fine to document
nrc
on 6 Apr 2018
Related issues
booyaa
路
4Comments
olehmisar
路
5Comments
tYYGH
路
3Comments
kjeremy
路
5Comments
byteshiva
路
4Comments
Most helpful comment
"rls.path"