Xref: news2.mv.net comp.os.msdos.djgpp:3075
From: mcantos AT ocean DOT com DOT au (Marcelo Cantos)
Newsgroups: comp.os.msdos.djgpp
Subject: Re: Error messages and warnings...
Date: Wed, 24 Apr 96 14:45:21 GMT
Organization: (private)
Lines: 24
Message-ID: <4lliaa$pdu@news.mel.aone.net.au>
References: <Pine DOT SUN DOT 3 DOT 91 DOT 960415083521 DOT 3742K-100000 AT is> <4le0mq$64s AT pub DOT news DOT uk DOT psi DOT net>
NNTP-Posting-Host: 203.12.234.172
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp

>>> Tom Sgouros (tomss AT ids DOT net) writes:
>>> > Can anyone tell me how to record the voluminous error messages that the
>>> > code I am working on generates? (I am porting a big program that was
>>> 
>
>>The best alternative I know is to compile from an editor that catches the
>>error messages in a buffer (by properly redirecting stderr,
>
>If you use Win95 and want to do this consider Textpad. With this I hotkey to
>compile and then step forwards/backwards through the errors; the correct file
>comes up with the cursor at the right line and the error message in a status
>box at the bottom - cool.
>
>I also wrote a small prog for Textpad that takes the word that the cursor is
>currently on and does a search in info for that word - outputs to a file and
>opens it in Textpad!
>
>Jason.
>

Another alternative is 4DOS, which allows piping of stderr which is where the 
error messages are going. I just type:
   gcc ... |&more
Go to http://www.jpsoft.com for more information.