Skip to content

Option to launch without debugging turned on #2592

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

Closed
danrubel opened this issue Apr 16, 2012 · 6 comments
Closed

Option to launch without debugging turned on #2592

danrubel opened this issue Apr 16, 2012 · 6 comments
Assignees
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Milestone

Comments

@danrubel
Copy link

When I create a Dartium launch I can choose whether to enable debugging or not.
I don't want to decide whether I'll be debugging a launch or not. Mostly I want to just run it. I only want to debug it when there is a problem. Now to just run a launch that has debugging enabled I either need to disable the debugging in the launch or delete all breakpoints.
To separate actions run and debug like in Eclipse would be much more convenient.
////////////////////////////////////////////////////////////////////////////////////
Editor Version: 6442

@danrubel
Copy link
Author

Are there any differences between run and debug from a speed or functionality standpoint?


Set owner to @devoncarew.

@danrubel
Copy link
Author

danrubel commented Jun 1, 2012

Added this to the Later milestone.

@devoncarew
Copy link
Member

Removed this from the Later milestone.
Added this to the M3 milestone.

@danrubel
Copy link
Author

Removed this from the M3 milestone.
Added this to the Later milestone.

@devoncarew
Copy link
Member

This is very unlikely now for the Editor; we've removed the option to launch w/o debugging.


Added NotPlanned label.

@clayberg
Copy link

Removed this from the Later milestone.
Added this to the M3 milestone.

@danrubel danrubel added Type-Enhancement closed-not-planned Closed as we don't intend to take action on the reported issue labels Jan 17, 2013
@danrubel danrubel added this to the M3 milestone Jan 17, 2013
@kevmoo kevmoo added type-enhancement A request for a change that isn't a bug and removed type-enhancement labels Mar 1, 2016
dart-bot pushed a commit that referenced this issue Aug 11, 2020
> git log --oneline 04b054b62cc437cf23451785fdc50e49cd9de139..master
0d185a39 (HEAD -> master, origin/master, origin/HEAD) Push null-safety forwards to 2.11 (#2604)
56f9f27f Hide outdated --mode flag (#2603)
61ce6f81 Avoid double loop (#2605)
fa6e57d7 (disable_mixed_mode_validation) Fix outdated latest ordering (#2598)
6549e4aa Remove unused dependency from pubspec.yaml (#2592)
61543d07 Don't look for external package foo during testing (#2599)
590b448f Fixed license headers (#2595)
04e0601e Don't show entries for dev-dependencies in outdated --json --no-dev-dependencies (#2591)
8c3778c4 Configure GitHub move app (#2578)
eec7beca (top_level_command) Pass --(no-)sound-null-safety arg through to VM. (#2542)
152e4740 Warn about publishing in mixed mode (#2583)
0b7a3abe Removed april fools toys (#2325)
b74a5b73 Actually print hints (#2582)
8ec3a66d (pub2) Fix outdated --no-color (#2572)
7bb3d4e6 Use getSdkPath() in NullSafetyAnalysis (#2573)
3c578f24 Drop the "magic" package concept (#2577)
0e967ff0 Remove unused function (#2570)
988fefef Remove dependency overrides (#2568)

Change-Id: I58bf14234ed55bf9d825de60a40ded1d65281195
Reviewed-on: https://dart-review.googlesource.com/c/sdk/+/158003
Reviewed-by: Jonas Jensen <[email protected]>
Commit-Queue: Sigurd Meldgaard <[email protected]>
This issue was closed.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
closed-not-planned Closed as we don't intend to take action on the reported issue type-enhancement A request for a change that isn't a bug
Projects
None yet
Development

No branches or pull requests

4 participants