Скачать или смотреть How to Redirect Echoes of Windows Batch-File Commands for Cleaner Output

Discover how to redirect the echoed commands of Windows batch-files to a log file, while keeping certain outputs in the console for clearer script execution.
---
This video is based on the question https://stackoverflow.com/q/63678302/ asked by the user 'thecommexokid' ( https://stackoverflow.com/u/1187304/ ) and on the answer https://stackoverflow.com/a/63713137/ provided by the user 'aschipfl' ( https://stackoverflow.com/u/5047996/ ) at 'Stack Overflow' website. Thanks to these great users and Stackexchange community for their contributions.

Visit these links for original content and any more details, such as alternate solutions, latest updates/developments on topic, comments, revision history etc. For example, the original title of the Question was: Redirect echos of Windows batch-file commands

Also, Content (except music) licensed under CC BY-SA https://meta.stackexchange.com/help/l...
The original Question post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license, and the original Answer post is licensed under the 'CC BY-SA 4.0' ( https://creativecommons.org/licenses/... ) license.

If anything seems off to you, please feel free to write me at vlogize [AT] gmail [DOT] com.
---
Introduction

Running batch scripts on Windows can often clutter your command prompt with echoed commands, making it difficult to read the actual output you're interested in. By default, when executing commands in a .bat file, the command prompt displays each command before it runs. This is helpful for debugging but can be annoying if you only want the output.

In this post, we will explore how to effectively redirect these echoed commands to a log file, allowing for a tidier console output while still capturing essential information.

Understanding the Problem

Let’s consider a simple example. Suppose you have a batch file named example.bat with the following commands:

[[See Video to Reveal this Text or Code Snippet]]

When you run this script, the command prompt displays:

[[See Video to Reveal this Text or Code Snippet]]

As seen, the command prompt echoes both the ver and vol commands. If you decide to redirect the output of ver to a log file like so:

[[See Video to Reveal this Text or Code Snippet]]

The output of ver gets saved into example.log but the command prompt still echoes the command C:\test>ver.

The Challenge

The goal is to redirect the echo of the command ver to the log file without losing the visibility of subsequent command outputs in the console.

The Solution

Achieving this requires some clever scripting. Here’s a breakdown of how you can successfully redirect echoed commands using a subroutine.

Step-by-Step Process

Start your batch script with the @ rem command: This tells the script not to display commands that it is executing.

Use a subroutine: Place the commands intended for redirection in a separate subroutine.

Call the subroutine with redirection: Redirecting the output of that call to your log file.

Execute other commands normally: Keep any commands you want to display in the main section of the script.

Here is how your modified batch file should look:

[[See Video to Reveal this Text or Code Snippet]]

Explanation of the Components

@ rem: This is a comment line that helps to explain the script without executing any lines, hence no output is echoed.

@ call :SUB: This calls the subroutine named SUB, invoking the ver command whose echoed input is redirected to file.log.

Output Command (vol): This output is still printed to the command prompt for visibility.

Result

When you run your updated batch script, you will no longer see the command echo for ver in the command prompt, but rather, its output will be stored in file.log. The output of vol will still appear in the command prompt, providing a clear and condensed view of your script execution.

Conclusion

Redirecting the echoed commands of Windows batch-files can greatly improve the clarity of your command prompt. By utilizing subroutines and clever redirection, you can maintain a clean display while capturing important information in log files.

Feel free to experiment with this technique in your own batch scripts to enhance your development experience!