-
Notifications
You must be signed in to change notification settings - Fork 4.3k
Rust: don't show run button in build scripts #14720
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.
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
Comments
Every |
this is what in vscode, ![]() A button that doesn't work shouldn't exist, that's a design problem. |
to clarify, not all build.rs files, only rust build scripts https://doc.rust-lang.org/cargo/reference/build-scripts.html |
I agree that we shouldn't show a run button in build scripts, but to just put it out there: it's a bit harder than just checking if a file is named |
If the rust analyzer isn't doing anything neither is the LSP and the LSP is where the hooks for the test functions go so that last example isn't configured correctly, also why is there an expectation that it shouldn't be there, is there any issue to offering the feature? |
|
Build scripts are runnable, you usually don't want to run them on their own but they should be runnable |
build scripts are for We use but output is not supported by build scripts now. rust-lang/cargo#985 |
Should |
Hi there! 👋 |
This issue was closed due to inactivity. If you're still experiencing this problem, please open a new issue with a link to this issue. |
Check for existing issues
Describe the bug / provide steps to reproduce it
Environment
Zed: v0.144.3 (Zed)
OS: macOS 14.5.0
Memory: 32 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
No response
If applicable, attach your Zed.log file to this issue.
Zed.log
The text was updated successfully, but these errors were encountered: