Date: Thu, 25 Apr 1996 03:09:26 +0800 (GMT+0800)
From: Orlando Andico <orly AT abigail DOT eee DOT upd DOT edu DOT ph>
To: Marcelo Cantos <mcantos AT ocean DOT com DOT au>
cc: djgpp AT delorie DOT com
Subject: Re: Error messages and warnings...
In-Reply-To: <4lliaa$pdu@news.mel.aone.net.au>
Message-ID: <Pine.LNX.3.91.960425030739.399A-100000@abigail.eee.upd.edu.ph>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII

On Wed, 24 Apr 1996, Marcelo Cantos wrote:

<snip>
> >>The best alternative I know is to compile from an editor that catches the
> >>error messages in a buffer (by properly redirecting stderr,
> >
<snip>
> >
> >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.
> 

And yet another is to use Jed, or Emacs!!! (I prefer Jed because the 
binary is quite small so you have more space for your compiler). The good 
part about this method is that you can sort-of IDE-style debug your 
programs with the messages in one window and the source in another.

Orlando Andico
orly AT abigail DOT eee DOT upd DOT edu DOT ph