Xref:	news2.mv.net comp.os.msdos.djgpp:5842
From:	Tom Wheeley <tomw AT tsys DOT demon DOT co DOT uk>
Newsgroups:	comp.os.msdos.djgpp
Subject:	Re: Screen capture of compilations
Date:	Tue, 09 Jul 96 21:26:15 GMT
Organization:	City Zen FM
Lines:	30
Message-ID:	<836947575snz@tsys.demon.co.uk>
References:	<199606301118 DOT HAA05922 AT fcshome DOT stoneham DOT ma DOT us> <4rgdle$8s6 AT news DOT euro DOT net> <31DC02DA DOT 4E4D AT cybernex DOT net>
Reply-To:	tomw AT tsys DOT demon DOT co DOT uk
To:	djgpp AT delorie DOT com
DJ-Gateway:	from newsgroup comp.os.msdos.djgpp

In article <31DC02DA DOT 4E4D AT cybernex DOT net>
           vmeister AT cybernex DOT net "Ian Viemeister" writes:

> Bram Stolk wrote:
> > : This is because warnings/errors are written to STDERR, not stdout.
> > : Unfortunately, DOS's command procesor (command.com) does not provide
> > : a way to redirect stderr so, as with any other DOS program that writes
> > 
> > I use NDOS (Norton DOS), and I can do:
> > make >& log
> > Maybe msdos doesn't do this, but you could try it.
> 
> Doesn't command.com support stderr redirection with 'make 2> log' ?

No.  But the great program `redir' supplied with djgpp does.

try:

  redir -eo make | more

one day.  I use it all the time when the error messages scroll the screen
(err, should I be admitting that? :-)  In my defence it's generally only when
I miss off a `;' from a prototype...

..splitbung
-- 
* TQ 1.0 * The 'Just So Quotes'.
File names are infinite in length where infinity is set to 255 characters.
    	-- Peter Collinson, "The Unix File System"

- Raw text -