You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
in the document , it say , To echo a blank line on the screen, type : echo.
But there is a little problem about this.
If there is already a file named "echo" in the current directory , then type "echo." in CMD , it will show error information as below :
'echo.' is not recognized as an internal or external command,
operable program or batch file.
I think the document should warn people about this situation.
Some years ago , I meet this problem , and I asked people here ( a Chinese website ) : https://tieba.baidu.com/p/4771590029 .
One say that I can use "echo," or "echo+" instead of "echo." .
I don't know why , but it works .
Today I think of this problem , so I report this problem here .
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
ID: b73a4605-c4b3-46a8-ec4e-493751fff82b
Version Independent ID: 2bcfea05-35c7-49cb-0570-a0d5a4957ca1
[Enter feedback here]
( I speak Chinese , my English is not so good. )
in the document , it say , To echo a blank line on the screen, type : echo.
But there is a little problem about this.
If there is already a file named "echo" in the current directory , then type "echo." in CMD , it will show error information as below :
'echo.' is not recognized as an internal or external command,
operable program or batch file.
I think the document should warn people about this situation.
Some years ago , I meet this problem , and I asked people here ( a Chinese website ) : https://tieba.baidu.com/p/4771590029 .
One say that I can use "echo," or "echo+" instead of "echo." .
I don't know why , but it works .
Today I think of this problem , so I report this problem here .
Document Details
⚠ Do not edit this section. It is required for learn.microsoft.com ➟ GitHub issue linking.
The text was updated successfully, but these errors were encountered: