delorie.com/archives/browse.cgi   search  
Mail Archives: djgpp/2001/01/29/10:31:50

From: Hans-Bernhard Broeker <broeker AT physik DOT rwth-aachen DOT de>
Newsgroups: comp.os.msdos.djgpp
Subject: Re: newbie
Date: 29 Jan 2001 13:52:05 GMT
Organization: Aachen University of Technology (RWTH)
Lines: 23
Message-ID: <953si5$o1g$1@nets3.rz.RWTH-Aachen.DE>
References: <952496$kks$1 AT planja DOT arnes DOT si>
NNTP-Posting-Host: acp3bf.physik.rwth-aachen.de
X-Trace: nets3.rz.RWTH-Aachen.DE 980776325 24624 137.226.32.75 (29 Jan 2001 13:52:05 GMT)
X-Complaints-To: abuse AT rwth-aachen DOT de
NNTP-Posting-Date: 29 Jan 2001 13:52:05 GMT
Originator: broeker@
To: djgpp AT delorie DOT com
DJ-Gateway: from newsgroup comp.os.msdos.djgpp
Reply-To: djgpp AT delorie DOT com

David Krmpotic <David DOT Krmpotic AT guest DOT arnes DOT si> wrote:
> I'm new to DJGPP so I need some help..

> what's the best way to see the compiler output (errors) if the screen
> scrolls. Is using redir.exe the only way? 

No. Other (and better, IMHO) ways include using a DJGPP-aware
editor/IDE like RHIDE or Emacs. Once you've got used to having the
error messages in one text window, and the culprit line of source code
automatically synchronized in the other, you'll never want to go back.

> is there any switch to pause the
> output on each 25 lines?

Not in redir, no. It's better to redirect the messages to file,
instead, and use 'less' or 'more' (or any other textfile viewing
program you prefer) to view them. That way, you'll also have them
stored so you can look at them as often as you like, without having to
recompile.

-- 
Hans-Bernhard Broeker (broeker AT physik DOT rwth-aachen DOT de)
Even if all the snow were burnt, ashes would remain.

- Raw text -


  webmaster     delorie software   privacy  
  Copyright © 2019   by DJ Delorie     Updated Jul 2019