From:	rpolzer AT web DOT de (Rudolf Polzer)
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: newbie
References:	<Pine DOT SUN DOT 3 DOT 91 DOT 1010129082033 DOT 28507L-100000 AT is>
X-newsgroup:	comp.os.msdos.djgpp
X-Mailer:	GehtDichNenScheissdreckAn 1.0
User-Agent:	GehtDichNenScheissdreckAn 1.0
Message-ID:	<slrn97bapv.4d2.rpolzer@rebounce.rpolzer-lx>
User-Agent:	slrn/0.9.6.2 (Linux)
Date:	Mon, 29 Jan 2001 18:41:19 +0100
Lines:	23
NNTP-Posting-Host:	213.6.55.205
X-Trace:	980886575 news.freenet.de 128 213.6.55.205
X-Complaints-To:	abuse AT freenet DOT de
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp
Reply-To:	djgpp AT delorie DOT com

Eli Zaretskii <eliz AT is DOT elta DOT co DOT il> schrieb Folgendes:
> 
> On Sun, 28 Jan 2001, Alexei A. Frounze wrote:
> 
> > ever tried to do something like this:
> >   c:\>dir |more
> > ?
> > try to add " |more" and see what happens.
> > or even better...
> > add " >test.txt" -- this will write the output to a text file instead of the
> > screen.
> 
> This will not work with programs which print error messages to stderr 
> instead of stdout.  COMMAND.COM doesn't know how to redirect stderr.

Why is 2>&1 not implemented in command.com? cmd.exe of WinNT can do
it. Or why doesnt gcc print error messages to STDOUT on WinDOZe when a
switch like -stdout is passed? Since gcc does not stop at the first error
message, you cannot find the error without the pause key or an IDE!

-- 
Nuper erat medicus, nunc est vispillo, Diaulus:
Quod vispillo facit, fecerat et medicus.

- Raw text -