[bug]After the shell process end, the tab doesn't close automatic.
See original GitHub issueVersion: 1.0.73
Platform: win32 10.0.18356
Plugins: clickable-links, save-output, scrollbar, shell-selector
When I type exit
or press Ctrl + D
in the shell, the shell itself closed but left an empty tab and I have to close it manually.
I noticed #84, however, the issue seems still exist in my computer.
Issue Analytics
- State:
- Created 4 years ago
- Comments:8 (3 by maintainers)
Top Results From Across the Web
[bug]After the shell process end, the tab doesn't close automatic.
When I type exit or press Ctrl + D in the shell, the shell itself closed but left an empty tab and I...
Read more >How to prevent the command prompt from closing after ...
I have a solution which can only apply on .cmd and .bat files: Open regedit and go to each one of: [HKEY_CLASSES_ROOT\batfile\shell\open\command] ...
Read more >How to automatically close cmd window after batch file ...
I just wanted to close the command window automatically after exiting the game. I just double click on the .bat file on my...
Read more >Command Prompt just flashes and closes immediately
When I tried to use cmd to run a command I noticed it would just flash and immediately close, I read previous forums...
Read more >AutoCAD crashes or freezes when saving, closing, or plotting ...
AutoCAD Application has stopped working. A problem caused the program to stop working correctly. Windows will close the program and notify you ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Disable the scrollbar plugin - you don’t need it with the recent versions with xterm anyway
I had the same problem but I have not experienced it since I upgraded to 1.0.75.