I'm currently working on a library that uses a file in the examples/ directory to ship a simple implementation of a frontend. It seems that no editor I can find (at least, not Atom, RustDT, or VSCode) will use RLS to analyze examples. How can I enable this?
First follow the instructions on https://github.com/jonathandturner/rls_vscode, for use in vscode install package it as visx file by running,
npm install -g vsce
vsce package
and then do cmd+shift+p and type in install from visx.
Find the visx file and then install it, after that the info from the rls server will show up when coding .
I know how to set up my editor to work with RLS. My problem is that there
doesn't seem to be a RLS.toml setting to analyze sources in the examples
directory.
On Sat, Apr 22, 2017, 16:09 Lenard Pratt notifications@github.com wrote:
First follow the instructions on
https://github.com/jonathandturner/rls_vscode, for use in vscode install
package it as visx file by running,npm install -g vsce
vsce packageand then do cmd+shift+p and type in install from visx.
Find the visx file and then install it, after that the info from the rls
server will show up when coding .—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/rust-lang-nursery/rls/issues/269#issuecomment-296401709,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ADI0_UGKoFJiSqU9B7bjnR0TkyBsUKlZks5rymyTgaJpZM4NFI5Z
.
I've cloned a project with files in the example directory and I tried to do the same thing as well. Looking at the RLS Language server output, it gives out a this error message
[Error - 22:50:16] Request textDocument/definition failed.
Message: GotoDef failed to complete successfully
Code: -32601
unfortunately I cant find any thing that defines the error code
Ignore what I said but when using vscode do this :

and check to see if theirs an error message
RLS currently only works for the main project of a source tree. Unfortunately, it doesn't yet work for the examples directory, though we hope to enable that in the future.
Are there still plans to enable this feature, or is there any kind of workaround to achieve this?
I would like to support this and indexing tests, but no plans to do it soon. It is a bit complex (though hopefully easier since workspace support landed).
Isn't this now provided by all_targets = true config?
Yes! This fixes the issue for me.
Most helpful comment
Isn't this now provided by
all_targets = trueconfig?