comp.lang.idl-pvwave archive
Messages from Usenet group comp.lang.idl-pvwave, compiled by Paulo Penteado

Home » Public Forums » archive » Re: which stream is prompt written to?
Show: Today's Messages :: Show Polls :: Message Navigator
E-mail to friend 
Switch to threaded view of this topic Create a new topic Submit Reply
Re: which stream is prompt written to? [message #6963] Mon, 09 September 1996 00:00
Christian Soeller is currently offline  Christian Soeller
Messages: 46
Registered: August 1996
Member
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
Re: which stream is prompt written to? [message #6965 is a reply to message #6963] Sun, 08 September 1996 00:00 Go to previous message
chs11 is currently offline  chs11
Messages: 14
Registered: October 1995
Junior Member
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
Re: which stream is prompt written to? [message #6973 is a reply to message #6965] Fri, 06 September 1996 00:00 Go to previous message
Christian Soeller is currently offline  Christian Soeller
Messages: 46
Registered: August 1996
Member
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
  Switch to threaded view of this topic Create a new topic Submit Reply
Previous Topic: Re: looking for code
Next Topic: Re: How to produce EPS image file with preview???

-=] Back to Top [=-
[ Syndicate this forum (XML) ] [ RSS ] [ PDF ]

Current Time: Fri Oct 10 13:24:31 PDT 2025

Total time taken to generate the page: 1.03874 seconds