--version does not print a new line at the end
See original GitHub issueUsing 2.4.3 on linux, I get the following behavior when calling --version
(using the auto-generated help text):
$ dotnet run --version
strans 0.0.2$
The output does not terminate in a line break. This looks very ugly. Instead, it should be:
$ dotnet run --version
strans 0.0.2
$
All other commands nicely finish in a newline.
Issue Analytics
- State:
- Created 5 years ago
- Comments:6
Top Results From Across the Web
How to print without a newline or space - python
In Python 2.x, you can just add , at the end of the print function, so it won't print on a new line....
Read more >Python Print Without Newline: Step-by-Step Guide
Here's an example: print("Hello there!", end = '') The next print function will be on the same line. When you're programming, you may...
Read more >How to print without newline in Python?
x, you can use a comma at the end of the print statement, just like in the given code. Python ...
Read more >Python Print Without Newline: Easy Step-by-Step Guide
To print without a newline in Python, you can use the end and sep parameters in the print function, or use alternatives like...
Read more >Here is how to print without a newline or space in Python
To print without a newline or space in Python, you can use the end parameter of the print() function. This parameter specifies the...
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
My workaround is to check whether the version is requested, and if so, append a newline:
Edit: Never mind, even echo gives its result back like that so I guess it is just the way
cmd
does it. I guess I just never noticed it before.Don’t know if it is a problem but thought I’d mention it anyway. The output, using the package above, running from a
cmd
prompt on Windows looks like this now:Running from a
powershell
prompt seems unaffected though so maybe this is just how it was always supposed to look incmd
.