Re: [ecasound] TERM variable not set

On Tue, 14 Dec 2010 22:47:25 +0200 (EET)
Kai Vehmanen <kvehmanen@email-addr-hidden> wrote:

> Hi,
>
> On Tue, 14 Dec 2010, Dave Serls wrote:
>
> > I get this message when trying to run ecasound via rsh on another PC.
> > Both environments tell me that TERM=xterm. I realize the remote shell environment
> > will be different. Is there a way to have ecasound ignore its console environment?
>
> passing '-D' should do it.

  Thanks, Kai.
  Sorry to bother you. I did unearth that from a more thorough reading
  of the 'man' page. I also coded -C for some reason to insure the 'batchness'
  of the run and redirected stderr and stdout. Wonderfully functional.
>
> This disabled curses-support, which requires to know the TERM setting.
> Alternatively you can compile ecasound without ncurses, but in most cases
> '-D' is enough.
>
> ------------------------------------------------------------------------------
> Lotusphere 2011
> Register now for Lotusphere 2011 and learn how
> to connect the dots, take your collaborative environment
> to the next level, and enter the era of Social Business.
> http://p.sf.net/sfu/lotusphere-d2d
> _______________________________________________
> Ecasound-list mailing list
> Ecasound-list@email-addr-hidden
> https://lists.sourceforge.net/lists/listinfo/ecasound-list

------------------------------------------------------------------------------
Lotusphere 2011
Register now for Lotusphere 2011 and learn how
to connect the dots, take your collaborative environment
to the next level, and enter the era of Social Business.
http://p.sf.net/sfu/lotusphere-d2d
_______________________________________________
Ecasound-list mailing list
Ecasound-list@email-addr-hidden
https://lists.sourceforge.net/lists/listinfo/ecasound-list
Received on Wed Dec 15 08:15:02 2010