-
Notifications
You must be signed in to change notification settings - Fork 176
Feature request: Confusing task names #99
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
I’m open to suggestions if you have better names in mind. I assume you’re talking about these labels? cortex-m-quickstart/.vscode/tasks.json Line 12 in 3cbcb99
|
@rubberduck203, yes that's what I'm talking about. I didn't have anything specific in mind. I just want something that looks like a label rather than a shell command. Maybe |
How about the following?
Also, feel free to submit a PR, otherwise I'll get around to it sometime soon-ish. |
Those look good to me. There's no rush. I'll also try to get around to it soon, but you might beat me. Thanks for considering the change. |
@bradleyharden PR #100 is open. Just need to wait for a maintainer now. |
Fixes #99: Disambiguates VSCode Tasks
Thanks @rubberduck203! |
Using the equivalent command line as the task name caused some confusion. Users were under the impression that they could use any valid cargo command as a preLaunchTask in the launch configurations.
Hi,
I didn't have much experience with VSCode before using it with Rust. I was working with Cortex-Debug and the
preLaunchTask
field. The current Rust task names look like shell commands. Because of that, I assumed I could change thepreLaunchTask
string to a different shell command and it would work. I only realized later that thepreLaunchTask
string is actually a task name, and that the task names just happen to look like shell commands.I think this is misleading and probably a source of confusion for others who are not familiar with VSCode tasks. Can I suggest changing the names to something that doesn't look like a shell command?
The text was updated successfully, but these errors were encountered: