CMD - How to Save Console Output to File in Real Time Without Buffering

Question

Hello. I would like to write the output of a console program to a text file.
In general, I know what commands to use. The problem is that the result is always saved after the program executes. So the result is buffered, the program executes and then the whole log is saved.
And I would like the log to be saved "live" without buffering the text (result).

mdmyt · Accepted Answer

Hello. Syntax: command_with_parameters> path for the file Example: ping elektroda.pl -t> D: \ file.txt The ping result will be written to file.txt on drive D

phaxe · Accepted Answer

Upload tee.exe from and use it like this: Code: text Expand Select all Copy to clipboardtwoja_komenda | tee wynik.txt The output of the command goes to the screen and to the file simultaneously.

.:aspire:. · Answer

Thank you for the answer, but I know this command. The problem is that I use an application that takes a few minutes to execute. And a normal redirect will only work after this app has been executed. I would like to view the log in a text file while the program is running.
So the idea is that exe'k should not cache the results.

.:aspire:. · Answer

Unfortunately it does not work

phaxe · Answer

For me, it works, for example, when copying files: Code: text Expand Select all Copy to clipboardXCOPY X:\katalog\*.* Y:\katalog\ /E /K /H /Y /D | tee D:\wynik.txt The copy result goes to the screen and to the result.txt file simultaneously

marek003 · Answer

What else are you talking about.

You are talking about a single command and the author is talking about a console application / program.

To the author
Perhaps it is worth rethinking (remembering) how the program works in "console mode".

If you were to see it on the fly, you would need to change (edit and correct) the application you have, in other words, with each "internal command" of your "application" you would have to put code to throw information.
Now the question: where?

Just "txt" would not be enough in this case because after each command returning information to the txt file you would have to refresh (reopen) this text file.
Alternatively, it would remain watching the console window if the results were returned to the screen.

piotr_be · Answer

I ran into this thread having a similar problem, this time not redirecting anything from the screen to a text file. I am writing here so as not to clutter the forum with a new topic unnecessarily, especially since the problem is solved, so only for someone who happens to him in a similar way.

Recommendation composer install

Standard: composer install> result.txt

But in the result.txt file, I don't have everything I can see on the screen.
It turns out that the result visible on the screen is printed partly on STDERR and partly on STDOUT.

To save everything that is visible on the screen to a file, you need to write:
composer install> result.txt 2> & 1

CMD - How to Save Console Output to File in Real Time Without Buffering

Post #1

Post #2

Post #3

Post #4

Post #5

Post #6

Post #7

Post #8

Didn't find an answer? Ask Artificial Intelligence

Topic summary