From: mert0407 AT sable DOT ox DOT ac DOT uk (George Foot) Newsgroups: comp.os.msdos.djgpp Subject: Re: redir -e etc. Date: 17 Oct 1997 10:33:52 GMT Organization: Oxford University, England Message-ID: <627eug$2ct$3@news.ox.ac.uk> References: <34455E08 DOT 32F1 AT sympatico DOT ca> NNTP-Posting-Host: sable.ox.ac.uk Lines: 25 To: djgpp AT delorie DOT com DJ-Gateway: from newsgroup comp.os.msdos.djgpp Precedence: bulk On Thu, 16 Oct 1997 00:21:28 GMT in comp.os.msdos.djgpp Frank Faubert (frank DOT faubert AT sympatico DOT ca) wrote: : As I read these messages (except for the guy who keeps screaming to be : removed), I notice that alot of times, you folks show things like: : redir -e errors.txt gcc -c xyz.cc : (Sorry Andreas, yours was handiest). I realize that these are to entered : on the command line if you're using a text editor, but how do you : implement them in RHIDE (I don't know squat about Unix so I use : something that compiles for me). `redir' is simply a utility that juggles the input and output streams, redirecting them to/from files or each other. The reason the above command is useful is that it runs `gcc -c xyz.cc', capturing its stderr output to `errors.txt'. This trick works on anything that uses those output streams; however, I doubt that RHIDE does at all, so you couldn't capture its output. However, RHIDE already does capture the output of the processes it runs; this is how it puts it in a window for you, with all the error messages. So you don't actually have the problem to which this use of redir is a solution. -- George Foot Merton College, Oxford