Windows command shell randomly prints block characters at output line endings
up vote
0
down vote
favorite
In my command prompt in Windows 10 (new console), I frequently see random cursor characters rendered at the end of some lines, depending on the load in other tasks. I believe this is associated with output lines containing LF characters (rather than Windows' usual CRLF line endings). Has anybody else seen this? Is there a way to stop these random cursor characters from printing?
windows command-line
asked Nov 27 at 20:03
Steve Hollasch
1012
add a comment |
up vote
0
down vote
favorite
In my command prompt in Windows 10 (new console), I frequently see random cursor characters rendered at the end of some lines, depending on the load in other tasks. I believe this is associated with output lines containing LF characters (rather than Windows' usual CRLF line endings). Has anybody else seen this? Is there a way to stop these random cursor characters from printing?
windows command-line
asked Nov 27 at 20:03
Steve Hollasch
1012
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of thedircommand), I still see only LF characters.
– Steve Hollasch
Nov 27 at 21:11
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
In my command prompt in Windows 10 (new console), I frequently see random cursor characters rendered at the end of some lines, depending on the load in other tasks. I believe this is associated with output lines containing LF characters (rather than Windows' usual CRLF line endings). Has anybody else seen this? Is there a way to stop these random cursor characters from printing?
windows command-line
asked Nov 27 at 20:03
Steve Hollasch
1012
In my command prompt in Windows 10 (new console), I frequently see random cursor characters rendered at the end of some lines, depending on the load in other tasks. I believe this is associated with output lines containing LF characters (rather than Windows' usual CRLF line endings). Has anybody else seen this? Is there a way to stop these random cursor characters from printing?
windows command-line
windows command-line
asked Nov 27 at 20:03
Steve Hollasch
1012
asked Nov 27 at 20:03
Steve Hollasch
1012
asked Nov 27 at 20:03
Steve Hollasch
1012
asked Nov 27 at 20:03
Steve Hollasch
1012
asked Nov 27 at 20:03
Steve Hollasch
1012
1012
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of thedircommand), I still see only LF characters.
– Steve Hollasch
Nov 27 at 21:11
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13
add a comment |
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of thedircommand), I still see only LF characters.
– Steve Hollasch
Nov 27 at 21:11
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of the
dir command), I still see only LF characters.– Steve Hollasch
Nov 27 at 21:11
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of the
dir command), I still see only LF characters.– Steve Hollasch
Nov 27 at 21:11
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1378873%2fwindows-command-shell-randomly-prints-block-characters-at-output-line-endings%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You're referring to the blocks at the ends of four of the lines? If that related to the Linux/Windows difference in line termination, it should be the same on every line.
– fixer1234
Nov 27 at 20:11
@fixer1234 — good point. I neglected to mention that I do not see this behavior in tools that emit CRLF line endings, only in tools that use LF only.
– Steve Hollasch
Nov 27 at 20:46
Have you tried copying lines with and without the blocks, and looking at the actual characters with a hex editor?
– fixer1234
Nov 27 at 20:59
It's a visual artifact. If you select and copy, the marks disappear. Pasting the copied data anyways yield no additional actual character. (And I'm not sure what encoding that would be. UTF-8?) Interestingly, if I use the command-prompt copy of what I would assume to be CRLF text (the help output of the
dircommand), I still see only LF characters.– Steve Hollasch
Nov 27 at 21:11
More interesting. If I select a character anywhere on a line with the cursor character at the end, the end mark disappears. Wait. Only sometimes. And some other times, selecting a character after the mark on the same line erases the mark. Odd.
– Steve Hollasch
Nov 27 at 21:13