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.

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

cmder no longer works on integrated terminal and spams external cmder instances #6935

Closed
Tyriar opened this issue May 26, 2016 · 2 comments
Closed

cmder no longer works on integrated terminal and spams external cmder instances #6935

Tyriar opened this issue May 26, 2016 · 2 comments
Assignees
@Tyriar
Labels
*as-designed Described behavior is as designed terminal General terminal issues that don't fall under another label

Comments

@Tyriar
Copy link
Member

Tyriar commented May 26, 2016

Pretty sure ti was at one point, now it's opening a bunch of issues repeatedly as they exit with exit code 0.
@Tyriar Tyriar added bug Issue identified by VS Code Team member as probable bug important Issue identified as high-priority terminal General terminal issues that don't fall under another label labels May 26, 2016
@Tyriar Tyriar self-assigned this May 26, 2016
@Tyriar Tyriar changed the title cmder no longer works on integrated terminal cmder no longer works on integrated terminal and spams external cmder instances May 26, 2016
Tyriar added a commit that referenced this issue May 26, 2016
@Tyriar
Recreate terminal when relaunched, not based on exit code
3052ed0 
Fixes #6937
Part of #6935
@Tyriar Tyriar added this to the May 2016 milestone May 26, 2016
@Tyriar
Copy link
Member Author

Tyriar commented May 26, 2016

Actually I'm not sure this every worked as cmder is a full blown UI app, the issue with the relaunching is fixed though so closing this.

@Tyriar Tyriar closed this as completed May 26, 2016
@Tyriar Tyriar removed this from the May 2016 milestone May 26, 2016
@Tyriar Tyriar removed the important Issue identified as high-priority label May 26, 2016
@joaomoreno
Copy link
Member

Any verification steps here?

@Tyriar Tyriar added *as-designed Described behavior is as designed and removed bug Issue identified by VS Code Team member as probable bug labels Sep 2, 2016
@Tyriar Tyriar mentioned this issue Sep 14, 2016
Closed
@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.
Assignees

@Tyriar Tyriar

Labels
*as-designed Described behavior is as designed terminal General terminal issues that don't fall under another label
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@joaomoreno @Tyriar