From karlheg at bittersweet.inetarena.com Sun Feb 26 16:40:01 2017 Content-Type: multipart/mixed; boundary="===============0890476423598885958==" MIME-Version: 1.0 From: Karl M. Hegbloom To: xemacs-beta at xemacs.org Subject: esd client env vars (Was: Re: More ESD ./configure bogosity) Date: 2000-01-20 02:21:54 -0800 Message-ID: <87embdf3gd.fsf_-_@bittersweet.intra> In-Reply-To: wmperry@aventail.com's message of "08 Dec 1999 10:35:28 -0500" --===============0890476423598885958== Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: quoted-printable >>>>> "William" =3D=3D William M Perry writes: William> Daniel Pittman writes: >> On Tue, 7 Dec 1999, Martin Buchholz wrote: >> = >> >>>>>> "ST" =3D=3D Stephen J Turnbull >> writes: > > ST> Why is the default "native, esd" and not >> "everything we can > ST> detect"? > > Good question. > > How >> do people feel about this more comprehensible user interface: >> = >> [... sane interface to sound in configure ...] >> = >> Sounds fine to me. It solves my problem nicely--I could build >> without ESD support happily :) William> We need a way from lisp to specify what host/port to William> connect to with ESD though. Otherwise it is kindof William> useless (at least here :) From the `esound.sgml': Environment Variables All client programs (except esdctl) can connect to remote hosts via the ESPEAKER environment variable: = bash $ export ESPEAKER=3Dinet.addr.of.host:p= ort tcsh > setenv ESPEAKER inet.addr.of.host:= port The client will connect to EsounD running on the specified host on the specified port. --===============0890476423598885958==--