Skip to content
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

Test: Ability to select and start a launch using keyboard #20982

Closed
2 tasks done
michelkaporin opened this issue Feb 21, 2017 · 7 comments
Closed
2 tasks done

Test: Ability to select and start a launch using keyboard #20982

michelkaporin opened this issue Feb 21, 2017 · 7 comments
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Milestone

Comments

@michelkaporin
Copy link
Contributor

michelkaporin commented Feb 21, 2017

Complexity: 1

Refs: #16613
We have introduced an ability to select and launch debug configuration through the command palette.

Verify:

  • Open command palette (Ctrl+E) and type: debug with space at the end. The list of all debug configurations listed in launch.json should appear.
  • Open command palette and type >Debug: Select and Start Debugging, option should appear, upon clicking should be presented with a list of all launch configs.
  • Correct debug configuration started upon selection.
  • Correct debug configuration is selected in the drop-down menu of debug view upon config running (Ref Select box debug configuration listener #20985).
@jrieken jrieken added this to the February 2017 milestone Feb 21, 2017
@jrieken
Copy link
Member

jrieken commented Feb 21, 2017

@michelkaporin fyi - please set milestone and testplan-item label

@michelkaporin
Copy link
Contributor Author

@jrieken I don't have permissions for this yet, unfortunately. Thanks for the notice anyway!

@isidorn isidorn added the debug Debug viewlet, configurations, breakpoints, adapter issues label Feb 21, 2017
@jrieken
Copy link
Member

jrieken commented Feb 21, 2017

doh. didn't know that... hope that changes soon

@MartinSGill
Copy link

I keep getting confused between "task" and "launch" configurations, that is I try to use the command pallet to start a debug "task" and wonder why there's nothing there.

In my mental model I see both as doing the same thing: running something. One is interactive (i.e. debug) while the other isn't.

Might this be an opportunity to merge/unify these somehow under a single keyword/alias?

e,g.

> Run: "Attach to VS Code" (debug)
> Run: "watch" (task)

@michelkaporin
Copy link
Contributor Author

michelkaporin commented Feb 23, 2017

@MartinSGill Thank you for your comment. Task and debug concepts are different. The first one is used to automate tasks like building, packaging, testing or deploying, whereas the other one configures the way you want to debug your program. Merging those two concepts into one would be wrong from simple software design perspective, and would lead to those concepts collision, as essentially they target two different purposes. Therefore, reference to them is kept under different keywords/aliases.

Please see the links below for further reference.
https://code.visualstudio.com/Docs/editor/debugging and
https://code.visualstudio.com/Docs/editor/tasks

@aeschli
Copy link
Contributor

aeschli commented Feb 23, 2017

Verified on Linux
Version 1.10.0-insider
Commit 64cccfc
Date 2017-02-23T09:13:27.511Z

@aeschli aeschli removed their assignment Feb 23, 2017
@ramya-rao-a
Copy link
Contributor

Verified on Mac
Version 1.10.0-insider
Commit 64cccfc
Date 2017-02-23T09:13:27.511Z

@ramya-rao-a ramya-rao-a removed their assignment Feb 23, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Nov 18, 2017
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
debug Debug viewlet, configurations, breakpoints, adapter issues testplan-item
Projects
None yet
Development

No branches or pull requests

6 participants