-
Notifications
You must be signed in to change notification settings - Fork 38.2k
Closed
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugterminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another labelwindowsVS Code on Windows issuesVS Code on Windows issues
Milestone
Description
- VSCode Version: Code - Insiders 1.9.0-insider (fcac9b6, 2017-01-31T00:57:46.157Z)
- OS Version: Windows_NT ia32 10.0.15019
- Extensions:
| Extension | Author | Version |
|---|---|---|
| vscode-eslint | dbaeumer | 1.2.2 |
| theme-dracula | dracula-theme | 1.2.5 |
| vscode-great-icons | emmanuelbeziat | 1.1.38 |
| Theme-azure | gerane | 0.0.2 |
| theme-material-theme | jprestidge | 1.0.1 |
| vs-color-picker | lihui | 0.3.2 |
| Theme-MaterialKit | ms-vscode | 0.1.1 |
| view-in-browser | qinjia | 0.0.4 |
| ActiveFileInStatusBar | RoscoP | 1.0.2 |
| eval | Stormspirit | 0.0.5 |
| omnipascal | Wosi | 0.12.0 |
Steps to Reproduce:
- running grunt test to run unit testing should produce this output: (here in cmd.exe)
Here is what I got in VSCode integrated terminal:
Note that the first time I ran it, the layout of the prompt was also broken, instead of the cursor directly following the prompt, like:
I was having:
(and I could not move the cursor more on the left)
Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugIssue identified by VS Code Team member as probable bugIssue identified by VS Code Team member as probable bugterminalGeneral terminal issues that don't fall under another labelGeneral terminal issues that don't fall under another labelwindowsVS Code on Windows issuesVS Code on Windows issues



