Tech-Recipes - Latest Comments in Supress Responses From Commands In Batch Files

Re: Supress Responses From Commands In Batch Files

vicky — Fri, 29 Apr 2011 13:43:36 -0000

Thank you very much.
This small tip has helped me a lot

Re: Supress Responses From Commands In Batch Files

Thu, 09 Jul 2009 04:53:32 -0000

Re: Supress Responses From Commands In Batch Files

Ghanny — Mon, 29 Jun 2009 13:28:40 -0000

For standard output also try "@echo off" at the start of the batch file. This will suppress echoing all the input commands.

Re: Supress Responses From Commands In Batch Files

timlarsen — Fri, 19 Nov 2004 02:54:50 -0000

The actual syntax (at least on Win2K) is

dir badfile.txt > null 2>&1

Note the position of the ampersand.

Re: Supress Responses From Commands In Batch Files

qmchenry — Thu, 05 Feb 2004 14:50:02 -0000

Greg,

That is a fantastic piece of knowledge. I've been redirecting stderr that way in unix for many years, but I've never tried it in dos. I wouldn't have thought to try. I also didn't know there was an eqivalent to /dev/null in dos. Great stuff!

Quinn

Re: Supress Responses From Commands In Batch Files

gmartin — Thu, 05 Feb 2004 14:36:41 -0000

This tip is good but it only goes so far. It will redirect STDOUT to null. Errors will still be displayed. As an example, run dir badfile.txt >nul and you will still see "File not found" displayed. That's because errors are written to STDERR

To redirect STDERR to nul as well, try this:

dir badfile.txt > nul 2&>1

Of course you may want to see the errors. So a better tack to take could be to write to a log file

dir badfile.txt >log.txt 2&>1

\Greg