You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I think that there should be one Terminal linked with one Angular Project.
When you execute a command on a project (Right click, Run as, ng build for example) and there is currently a linked Terminal opened (for previous command run), reuse.
If there is no one (never opened or just closed), create a new one and link with the project (for future re-use).
@rubensa As much as I know thats what it already does. However, there could be more then 1 Terminal/Project, since commands like "ng serve" run until you stop them. So to execute "ng generate" while "ng serve" is running, it needs to open a new Terminal.
Thank you for the information.
I guess the terminal, used to create a project, get's a different id from the Terminals used for other commands.
Thats why they will be reused for other "create" commands too.
Another issue on these is that Terminalshould not be reused if a command is currently running (don't know if It's possible to ask the Terminal if there is a running process active).
Currently if a process is running you can see the new command written on the terminal (for example ng build) but It's never really run (cause there is an ongoing running process -for example if you previously manually executed an ng server).
Activity
probert94 commentedon Jul 10, 2017
@rubensa As much as I know thats what it already does. However, there could be more then 1 Terminal/Project, since commands like "ng serve" run until you stop them. So to execute "ng generate" while "ng serve" is running, it needs to open a new Terminal.
rubensa commentedon Jul 10, 2017
Hello @Springrbua
I missed that cause Terminal used to create the project is not re-used (so a bit more "reuse" could be done).
I've just checked that if I run twice "Run As --> ng build", same Terminal is used.
Thanks!
probert94 commentedon Jul 10, 2017
The Terminal used to create the project probably isn't linked to the Project. We might need to check that.
Thanks for the information!
rubensa commentedon Jul 10, 2017
Additional info on this issue...
Terminal console used to create a new project is re-used to create other new projects...
NOTE: PATH variable is updated to last created project.
probert94 commentedon Jul 10, 2017
Thank you for the information.
I guess the terminal, used to create a project, get's a different id from the Terminals used for other commands.
Thats why they will be reused for other "create" commands too.
rubensa commentedon Jul 11, 2017
Hello
Another issue on these is that Terminal should not be reused if a command is currently running (don't know if It's possible to ask the Terminal if there is a running process active).
Currently if a process is running you can see the new command written on the terminal (for example ng build) but It's never really run (cause there is an ongoing running process -for example if you previously manually executed an ng server).