Message-Id: <199808020537.GAA28573@sable.ox.ac.uk>
Comments: Authenticated sender is <mert0407 AT sable DOT ox DOT ac DOT uk>
From: George Foot <george DOT foot AT merton DOT oxford DOT ac DOT uk>
To: drmcc AT ecr DOT mu DOT oz DOT au
Date: Sun, 2 Aug 1998 06:36:10 +0000
MIME-Version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7BIT
Subject: Re: Another stupid question
Reply-to: george DOT foot AT merton DOT oxford DOT ac DOT uk
CC: djgpp AT delorie DOT com
Precedence: bulk

On  2 Aug 98 at 13:32, Donald McComb wrote:

> Is there a command line argument for gcc which tells the compiler to
> display error messages only one screen at a time?  It seems like such a
> trivial problem and it's getting me REALLY annoyed.  I've tried using
> piping (ie. 'gcc -c filename.c | more') to no avail - it still does it! 
> ARGH!

DOS's command.com can't redirect stderr, and that's where gcc is 
sending the error messages.  You can use the `redir' utility to 
redirect errors either to a file, or to stdout instead.  If you 
redirect them to stdout, all DOS's redirection and piping will work 
again.  So for example:

    redir -e errors.txt gcc ....
or: redir -eo gcc .... | more
or: redir -o allout.txt -eo gcc ....  (all output redirected to the file)

Replace `....' with your command line for gcc.  See the DJGPP FAQ
(section 6.10) for more informaiton.

-- 
george DOT foot AT merton DOT oxford DOT ac DOT uk