Open Kristinita opened 7 years ago
I get CR break type in ends of lines.
I get normal break type behavior in any Windows terminal.
No CR in ends of lines.
For example, I run vagrant status command:
vagrant status
My User/Vagrant.sublime-settings file:
User/Vagrant.sublime-settings
{ "output_to_window": true, "vagrant_path": "C:\\HashiCorp\\Vagrant\\bin\\vagrant.exe" }
I reproduce the problem in a version of Sublime Text without plugins and user settings.
I install Vagrant via Package Control → I restart Sublime Text → I run any Vagrant command → I get CR symbol in line ends output.
If I run same command in Windows terminal (ConEmu, for example), I don't get the problem.
Operating system and version: Windows 10 Enterprise LTSB 64-bit EN Sublime Text: Build 3126 Vagrant 1.9.1
Thanks.
1. Summary
I get CR break type in ends of lines.
I get normal break type behavior in any Windows terminal.
2. Expected behavior
No CR in ends of lines.
3. Actual behavior
For example, I run
vagrant status
command:4. Settings
My
User/Vagrant.sublime-settings
file:5. Steps to reproduce
I reproduce the problem in a version of Sublime Text without plugins and user settings.
I install Vagrant via Package Control → I restart Sublime Text → I run any Vagrant command → I get CR symbol in line ends output.
If I run same command in Windows terminal (ConEmu, for example), I don't get the problem.
6. Environment
Operating system and version: Windows 10 Enterprise LTSB 64-bit EN Sublime Text: Build 3126 Vagrant 1.9.1
Thanks.