comp.lang.idl-pvwave archive - RDF feed
type: channel
description: Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado
items: Re: which stream is prompt written to?

Re: which stream is prompt written to?
type: item
description: chs11@aloha.cc.columbia.edu (Carl H Sayres) writes: > I need to pipe commands into idl and recieve the output from the stdout > and stdin streams. It all works fine except that I don't receive the > "IDL> " prompt. I'd like this so that I can know when a command has > finished. It's written to stderr. If you say something like un*x> idl 2>stderr.out you find all the prompts and the startup message in the file stderr.out. So maybe un*x> idl > named_pipe 2>&1 is what you would want to do (assuming ksh like shell syntax). Regards, Christian ------------------------------------------------------------ -------- Christian Soeller mailto: csoelle@sghms.ac.uk St. Georges Hospital Medical School Dept. of Pharmacology Cranmer Terrace London SW17 0RE
creator: Christian Soeller
date: 1996-09-06T07:00:00-00:00

Re: which stream is prompt written to?
type: item
description: In article <503f0wypx9.fsf@mbcsg1.sghms.ac.uk>, Christian Soeller <csoelle@sghms.ac.uk> wrote: > chs11@aloha.cc.columbia.edu (Carl H Sayres) writes: > >> I need to pipe commands into idl and recieve the output from the stdout >> and stdin streams. It all works fine except that I don't receive the >> "IDL> " prompt. I'd like this so that I can know when a command has >> finished. > It's written to stderr. If you say something like > un*x> idl 2>stderr.out > you find all the prompts and the startup message in the file stderr.out. > > So maybe > un*x> idl > named_pipe 2>&1 > is what you would want to do (assuming ksh like shell syntax). Your first example works (idl 2>stderr.out). But if you put a set of commands in a file and do this: idl < idl.in > idl.out 2> idl.err you don't get any prompts! Can anyone explain???? Carl
creator: chs11
date: 1996-09-08T07:00:00-00:00

Re: which stream is prompt written to?
type: item
description: chs11@ciao.cc.columbia.edu (Carl H Sayres) writes: > > Your first example works (idl 2>stderr.out). But if you put a set of > commands in a file and do this: > idl < idl.in > idl.out 2> idl.err > you don't get any prompts! Can anyone explain???? My guess is that idl checks if the input stream is associated with a terminal and won't generate prompt messages otherwise. Maybe you would be better of using callable IDL (see IDL advanced development guide) for your particular way of issuing IDL commands under external program control ? Regards, Christian ------------------------------------------------------------ -------- Christian Soeller mailto: csoelle@sghms.ac.uk St. Georges Hospital Medical School Dept. of Pharmacology Cranmer Terrace London SW17 0RE
creator: Christian Soeller
date: 1996-09-09T07:00:00-00:00