如果你的windows环境路径中有cygwin，你可以使用:

 dir > a.txt | tail -f a.txt

如果你想在屏幕上真正看到一些东西，下面的步骤会有所帮助——即使批处理文件被重定向到一个文件。如果重定向到一个文件，也可以使用设备CON

例子:

ECHO first line on normal stdout. maybe redirected
ECHO second line on normal stdout again. maybe redirected
ECHO third line is to ask the user. not redirected  >CON
ECHO fourth line on normal stdout again. maybe redirected

另请参阅良好的重定向说明:http://www.p-dd.com/chapter7-page14.html

不幸的是，没有这样的东西。

Windows控制台应用程序只有一个输出句柄。(嗯，有两个STDOUT, STDERR，但在这里不重要)>重定向输出通常写入控制台句柄到文件句柄。

如果你想要有某种多路复用，你必须使用一个外部应用程序，你可以将输出转移到它。然后，该应用程序可以再次写入文件和控制台。

发送输出到控制台，附加到控制台日志，从当前命令删除输出

dir  >> usb-create.1 && type usb-create.1 >> usb-create.log | type usb-create.1 && del usb-create.1

如果你的windows环境路径中有cygwin，你可以使用:

 dir > a.txt | tail -f a.txt

如果你在CLI中，为什么不用FOR循环来“DO”你想做的事情:

for /F "delims=" %a in ('dir') do @echo %a && echo %a >> output.txt

Great resource on Windows CMD for loops: https://ss64.com/nt/for_cmd.html The key here is setting the delimeters (delims), that would break up each line of output, to nothing. This way it won't break on the default of white-space. The %a is an arbitrary letter, but it is used in the "do" section to, well... do something with the characters that were parsed at each line. In this case we can use the ampersands (&&) to execute the 2nd echo command to create-or-append (>>) to a file of our choosing. Safer to keep this order of DO commands in case there's an issue writing the file, we'll at least get the echo to the console first. The at sign (@) in front of the first echo suppresses the console from showing the echo-command itself, and instead just displays the result of the command which is to display the characters in %a. Otherwise you'd see:

echo驱动器[x]中的卷为Windows

UPDATE: /F跳过空行，唯一的修复是预过滤输出，向每一行添加一个字符(可能通过命令find使用行号)。在CLI中解决这个问题既不快速也不漂亮。此外，我没有包括STDERR，所以这里捕获错误:

for /F "delims=" %a in ('dir 2^>^&1') do @echo %a & echo %a >> output.txt

重定向错误消息

插入符号(^)用于转义后面的符号，因为命令是一个正在被解释的字符串，而不是直接在命令行中输入它。