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

Integrated terminal needs to be closed in memory not just visually. #7107

Closed
bastienJS opened this issue Jun 1, 2016 · 5 comments
Closed
Assignees
Labels
info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label

Comments

@bastienJS
Copy link

bastienJS commented Jun 1, 2016

  • VSCode Version: 1.2.0
  • OS Version: Windows 10 x64

Steps to Reproduce:

  1. Open the integrated terminal
  2. Run "ng serve" which starts a process
  3. Close the terminal by clicking on the right-top X
  4. Open terminal again
  5. Everything is like before, I can NOT enter anything in the terminal.
  6. How am I assumed to cancel the current process to enter something new like ng build, ng test, or any other tool?
    6.5 At the moment I have always to restart vscode :/
  7. WebStorm has a red square button for that feature :-)
@Tyriar
Copy link
Member

Tyriar commented Jun 1, 2016

Do you mean you want to run multiple processes at once? #6458 will probably solve this.

@Tyriar Tyriar added info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label labels Jun 1, 2016
@Tyriar Tyriar self-assigned this Jun 1, 2016
@bastienJS
Copy link
Author

bastienJS commented Jun 1, 2016

@Tyriar I thought about this issue again. Actually its enough for me, if I could enter text into the terminal when there is a process runnung. Its just I can not type anything when "ng serve" is done. I followed your link and found your statement:

"I think pretty early on we will get the feature request to support multiple terminals. As soon as you run a program from the terminal, you cannot use it anymore."

Right, you can not use it anymore, thats my problem. Its a fire and forget terminal ;-)
Multiple terminal sound logical then to me.

@Tyriar
Copy link
Member

Tyriar commented Jun 1, 2016

@bastienJS ng serve continues to run though, so the terminal is not supposed to have control until the process is terminated??

@bastienJS
Copy link
Author

bastienJS commented Jun 1, 2016

@Tyriar Well I just would like to have it like it worked in WebStorm. There a integrated terminal has an exit button terminating the process within the terminal :-)

I think there are even 2 use cases:

  1. Exit an always running process within a integrated terminal to run something different
  2. Start another process in the same/another terminal in parallel.

@Tyriar
Copy link
Member

Tyriar commented Jun 1, 2016

Ah ok, yeah I think I'll close this in favor of #6458. That will include a UI where you can kill terminal instances.

@Tyriar Tyriar closed this as completed Jun 1, 2016
@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
info-needed Issue requires more information from poster terminal General terminal issues that don't fall under another label
Projects
None yet
Development

No branches or pull requests

2 participants