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

Test output has strange indentation when using \n as the EOL #124558

Closed
jdneo opened this issue May 25, 2021 · 3 comments
Closed

Test output has strange indentation when using \n as the EOL #124558

jdneo opened this issue May 25, 2021 · 3 comments
Assignees
Labels
*as-designed Described behavior is as designed

Comments

@jdneo
Copy link
Member

jdneo commented May 25, 2021

Does this issue occur when all extensions are disabled?: Yes/No

Version: 1.57.0-insider (user setup)
Commit: 5319757
Date: 2021-05-24T05:14:19.500Z
Electron: 12.0.7
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: 8.9.255.25-electron.0
OS: Windows_NT x64 10.0.19043

Steps to Reproduce:

  1. Using the test-provider-sample project
  2. Update the method invocation of appendOutput(), use just \n as the EOL
  3. The output indentation looks strange. If using \r\n, it looks as expected

image

// cc @connor4312

@vscodebot
Copy link

vscodebot bot commented May 25, 2021

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

@connor4312
Copy link
Member

The output is displayed as terminal output; \n only moves the cursor down a line, you want to use \r too in order to reset its position (\r\n)

@connor4312 connor4312 added the *as-designed Described behavior is as designed label May 25, 2021
@github-actions github-actions bot locked and limited conversation to collaborators Jul 9, 2021
This issue was closed.
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
*as-designed Described behavior is as designed
Projects
None yet
Development

No branches or pull requests

3 participants
@connor4312 @jdneo and others