Skip to content

Vs Code - Special Case/Ignore .rs Fiels in target/ #1428

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
theduke opened this issue Jun 22, 2019 · 5 comments
Closed

Vs Code - Special Case/Ignore .rs Fiels in target/ #1428

theduke opened this issue Jun 22, 2019 · 5 comments

Comments

@theduke
Copy link
Contributor

theduke commented Jun 22, 2019 •
edited
Loading

This is a relatively minor issue, but:

When opening a .rs file inside ./target, for example auto-generated FFI bindings, VS Code constantly (re)opens the console, spams a lot of error messages and re-displays the "a request has failed" popup.

It would be sensible to somehow disable LSP integration for those files in the plugin.
@lnicola
Copy link
Member

lnicola commented Jun 22, 2019

Wouldn't completion support be useful for the generated files?

@theduke
Copy link
Contributor Author

theduke commented Jun 22, 2019

Sure, ideally, but I imagine that's not something that will happen overnight.

@lnicola
Copy link
Member

lnicola commented Jun 22, 2019

Rather, why is RA panicking on those files?

@theduke
Copy link
Contributor Author

theduke commented Jun 22, 2019 •
edited
Loading 

[Error - 9:18:23 PM] Request textDocument/codeAction failed.
  Message: Rust file outside current workspace is not supported yet

The error is fairly descriptive. ;)

@lnicola lnicola mentioned this issue Jun 25, 2019
Closed
@matklad
Copy link
Member

matklad commented Jul 15, 2020

fixd

@matklad matklad closed this as completed Jul 15, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@theduke @lnicola @matklad