Get 20M+ Full-Text Papers For Less Than $1.50/day. Start a 14-Day Trial for You and Your Team.

Learn More →

DOStips

DOStips One reason for using batch files is to streamline the user's workflow by handling complex command sequences automatically, operating behind the scenes. To suppress the echoing of commands to the screen, which could confuse the user, many batch files begin with an echo off command. Although this suppresses the echoing of the commands, it doesn't suppress any output that might result from those commands. Most of the remaining output can be suppressed by adding >NUL at the end of every command in the batch file that produces output, to redirect the output from the command to an imaginary device called NULthe bit bucket I've mentioned in previous columns. http://www.deepdyve.com/assets/images/DeepDyve-Logo-lg.png OCLC Micro Emerald Publishing

DOStips

OCLC Micro , Volume 3 (3): 2 – Mar 1, 1987

Loading next page...
 
/lp/emerald-publishing/dostips-I14Rwp4Pbq
Publisher
Emerald Publishing
Copyright
Copyright © Emerald Group Publishing Limited
ISSN
8756-5196
DOI
10.1108/eb055837
Publisher site
See Article on Publisher Site

Abstract

One reason for using batch files is to streamline the user's workflow by handling complex command sequences automatically, operating behind the scenes. To suppress the echoing of commands to the screen, which could confuse the user, many batch files begin with an echo off command. Although this suppresses the echoing of the commands, it doesn't suppress any output that might result from those commands. Most of the remaining output can be suppressed by adding >NUL at the end of every command in the batch file that produces output, to redirect the output from the command to an imaginary device called NULthe bit bucket I've mentioned in previous columns.

Journal

OCLC MicroEmerald Publishing

Published: Mar 1, 1987

There are no references for this article.