From:	jpmorgan AT unm DOT edu (James Paul Morgan)
Subject:	Catching g++ error output
18 Apr 1997 02:34:46 -0700 :
Approved:	cygnus DOT gnu-win32 AT cygnus DOT com
Distribution:	cygnus
Message-ID:	<Pine.A32.3.91.970418010547.20142E-100000.cygnus.gnu-win32@pegasus.unm.edu>
Mime-Version:	1.0
Original-To:	gnu-win32 AT cygnus DOT com
In-Reply-To:	<Pine.SUN.3.96.970417185746.15874C-100000@tlaloc.stat.colostate.edu>
Original-Sender:	owner-gnu-win32 AT cygnus DOT com

Well, this question is less about the Cygnus win32 itself and more about 
one of the tools included with it, but...


Is there any way to capture the error output from g++ when it fails on a 
compile?  Sometimes, a few simple typos or minor bugs can generate more 
than a screen-full of output, and so I loose the earliest lines.  

On UNIX w/ Xwindows, I can just scroll back within the window.  But 
Windows95 doesn't have that option.  I've tried using '>' to dump it into 
a file, but that didn't work.  (I didn't expect it to as it doesn't on 
UNIX, but I figured I'd try.)  

Any suggestions of some way to manipulate the bash or possibly an add-on 
I could download or some simple trick I've just missed would be appreciated.


See ya around the Mulberry bush.

--James

:)

-
For help on using this list (especially unsubscribing), send a message to
"gnu-win32-request AT cygnus DOT com" with one line of text: "help".

- Raw text -