[OSC_dev] No dumpOSC output in pipe in non-interactive terminal

[Torsten Anders]

The following bash lines test whether the file descriptors 0-2 (i.e.  
stdin, stdout, and stderr)  refer to a terminal. In the interactive  
terminal, they all return yes, and when called in a shell started  
from within my language, they all return no.

if test -t 0; then echo yes; else echo no; fi
if test -t 1; then echo yes; else echo no; fi
if test -t 2; then echo yes; else echo no; fi

Best
Torsten


On Sep 8, 2007, at 9:12 AM, Torsten Anders wrote:
> Dear Tim,
>
> On Sep 8, 2007, at 1:40 AM, Tim Kreger wrote:
>> What platform/environment are you using?
>> I've had success using oscDump from within QT on OSX.
>
> I am presently running Mac OS X 10.4.10. I call dumpOSC from the  
> language Oz (www.mozart-oz.org) via a pipe, where the environment  
> is as shown below. As I said, in an interactive terminal it works,  
> even redirecting stdout into files or pipes. But not on the non- 
> interactive 'terminal' of my language, where the TERM environment  
> variable is set to dump. I tried simply changing this variable  
> without effect.
>
> Thank you!
>
> Best
> Torsten
>
>
> MANPATH=/sw/share/man:/usr/share/man:/usr/local/share/man:/Library/ 
> TeX/Distributions/.DefaultTeX/Contents/Man:/usr/X11R6/man:/sw/lib/ 
> perl5/5.8.6/man
> TERM=dumb
> SHELL=/bin/bash
> PERL5LIB=/sw/lib/perl5:/sw/lib/perl5/darwin
> EMACSDATA=/Applications/Aquamacs Emacs.app/Contents/Resources/etc
> COPY_EXTENDED_ATTRIBUTES_DISABLE=true
> TK_LIBRARY=/usr/local/oz/platform/i486-darwin/wish/tk
> EMACSPATH=/Applications/Aquamacs Emacs.app/Contents/MacOS/libexec:/ 
> Applications/Aquamacs Emacs.app/Contents/MacOS/bin
> EMACS=t
> USER=t
> LD_LIBRARY_PATH=/Users/t/.oz/1.3.99/platform/i486-darwin/lib:/usr/ 
> local/oz//platform/i486-darwin/lib
> OZ_PI=1
> TCL_LIBRARY=/usr/local/oz/platform/i486-darwin/wish/tcl
> TERMCAP=
> __CF_USER_TEXT_ENCODING=0x1F5:0:2
> COLUMNS=91
> PATH=/usr/local/oz//bin:/usr/local/oz//bin:/usr/bin:/bin:/usr/sbin:/ 
> sbin:/usr/local/texlive/2007/bin/i386-darwin/:/usr/local/oz/bin/:/ 
> Users/t/.oz/1.3.99/bin/:/usr/local/bin:/opt/local/bin:/opt/local/ 
> sbin:/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/ 
> usr/texbin:/usr/X11R6/bin:/usr/local/texlive/2007/bin/i386-darwin/:/ 
> usr/local/oz/bin/:/Users/t/.oz/1.3.99/bin/:/usr/local/bin:/opt/ 
> local/bin:/opt/local/sbin:/sw/bin:/sw/sbin:/bin:/sbin:/usr/bin:/usr/ 
> sbin:/usr/local/bin:/usr/texbin:/usr/X11R6/bin:/usr/local/teTeX/bin/ 
> powerpc-apple-darwin-current
> PWD=/Users/t/oz/music/Strasheela/strasheela/testing
> EDITOR=emacs
> SFDIR=/Users/t/Sound/tmp
> EMACSLOADPATH=/Applications/Aquamacs Emacs.app/Contents/Resources/ 
> lisp:/Applications/Aquamacs Emacs.app/Contents/Resources/leim:/ 
> Applications/Aquamacs Emacs.app/Contents/Resources/site-lisp
> SHLVL=3
> HOME=/Users/t
> DYLD_LIBRARY_PATH=/Users/t/.oz/1.3.99/platform/i486-darwin/lib:/usr/ 
> local/oz//platform/i486-darwin/lib
> OZPATH=.:/usr/local/oz//share
> INFOPATH=/sw/share/info:/sw/info:/usr/share/info:~/Library/ 
> Application Support/Emacs/info:/Library/Application Support/Emacs/ 
> info:/Applications/Aquamacs Emacs.app/Contents/Resources/site-lisp/ 
> edit-modes/info:/Applications/Aquamacs Emacs.app/Contents/Resources/ 
> info:~/Library/Application Support/Emacs/info:/Library/Application  
> Support/Emacs/info:/Applications/Aquamacs Emacs.app/Contents/ 
> Resources/site-lisp/edit-modes/info:/Applications/Aquamacs  
> Emacs.app/Contents/Resources/info
> DISPLAY=:0.0
> OZHOME=/usr/local/oz/
> INSIDE_EMACS=22.1.1,comint
> EMACSDOC=/Applications/Aquamacs Emacs.app/Contents/Resources/etc
> SECURITYSESSIONID=405610
> _=/usr/bin/env
>
>
>
> On Sep 8, 2007, at 1:40 AM, Tim Kreger wrote:
>> What platform/environment are you using?
>>
>> I've had success using oscDump from within QT on OSX.
>>
>>
>> On 08/09/2007, at 9:23 AM, Torsten Anders wrote:
>>
>>> Dear Angelo,
>>>
>>> thanks for your reply. My idea was, to make the job simply by  
>>> following the UNIX philosophy (cf. http://www.catb.org/~esr/ 
>>> writings/taoup/html/) of combining specialised programs via  
>>> piping...
>>>
>>> The dumpOSC option -quiet appears to suggest that it was also  
>>> intended for such usage. Why do advise against doing so (except  
>>> for the added overhead of parsing the textual output, of course)?
>>>
>>> Thank you!
>>>
>>> Best
>>> Torsten
>>>
>>>
>>> On Sep 7, 2007, at 11:25 PM, Angelo Fraietta wrote:
>>>> Torsten Anders wrote:
>>>>> Dear all,
>>>>> I would like to use the program dumpOSC for receiving and  
>>>>> processing  OSC packets. However, I would like to use dumpOSC  
>>>>> from within some  programming language via a pipe.
>>>>
>>>> I think the purpose of OSCDump is primarily to show you how to  
>>>> read OSC packets. The best way to implement it in your  
>>>> application is to compile what you need as a part of your app.
>>>>
>>>> -- 
>>>> Dr Angelo Fraietta
>>>> A.Eng, A.Mus.A, BA(Hons), Ph.D.
>
> _______________________________________________
> OSC_dev mailing list
> OSC_dev at create.ucsb.edu
> http://www.create.ucsb.edu/mailman/listinfo/osc_dev

--
Torsten Anders
Interdisciplinary Centre for Computer Music Research
University of Plymouth
http://strasheela.sourceforge.net
http://www.torsten-anders.de