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

Closing working directory/folder with the terminal open restarts the integrated terminal process and kills it's child processes #37552

Closed
fortraan opened this issue Nov 2, 2017 · 1 comment
Closed

Closing working directory/folder with the terminal open restarts the integrated terminal process and kills it's child processes #37552

fortraan opened this issue Nov 2, 2017 · 1 comment
Assignees
@Tyriar
Labels
*duplicate Issue identified as a duplicate of another issue(s) terminal General terminal issues that don't fall under another label

Comments

@fortraan
Copy link

fortraan commented Nov 2, 2017 •
edited
Loading

  • VSCode Version: Code 1.17.1 (1e9d365, 2017-10-10T14:10:17.189Z)
  • OS Version: Darwin x64 16.7.0
  • Extensions:
Extension Author (truncated) Version
vscode-eslint dba 1.4.2

Steps to Reproduce:

  1. Open a folder/working directory
  2. Open the integrated terminal
  3. Run a program, ie: idle3 or /Applications/TextEdit.app/Contents/MacOS/TextEdit &
  4. From the command bar, run File >> Close Folder

Processes spawned by the terminal will die and the terminal window will go blank (the text disappears, to be specific). Closing and re-opening the integrated terminal drops you into a new instance of the terminal/shell.
Running processes in the background doesn't spare said processes from this issue. The same problem occurs upon opening a folder/working directory as well.

Reproduces without extensions: Yes
@vscodebot vscodebot bot added the terminal General terminal issues that don't fall under another label label Nov 2, 2017
@Tyriar
Copy link
Member

Tyriar commented Dec 28, 2017

Duplicate #20013

@Tyriar Tyriar closed this as completed Dec 28, 2017
@Tyriar Tyriar added the *duplicate Issue identified as a duplicate of another issue(s) label Dec 28, 2017
@vscodebot vscodebot bot locked and limited conversation to collaborators Feb 11, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@Tyriar Tyriar

Labels
*duplicate Issue identified as a duplicate of another issue(s) 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
@Tyriar @fortraan