karlheg(a)bittersweet.inetarena.com (Karl M. Hegbloom) writes:
>>>>> "William" == William M Perry
<wmperry(a)aventail.com> writes:
William> Daniel Pittman <daniel(a)danann.net> writes:
>> On Tue, 7 Dec 1999, Martin Buchholz <martin(a)xemacs.org> wrote:
>>
>> >>>>>> "ST" == Stephen J Turnbull
<turnbull(a)sk.tsukuba.ac.jp>
>> 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':
<sect1 id="environment-variables">
<title>Environment Variables</title>
<para>
All client programs (except esdctl) can connect to remote hosts via
the <envar>ESPEAKER</envar> environment variable:
<literallayout>
<prompt>bash $ </prompt><userinput>export
ESPEAKER=inet.addr.of.host:port</userinput>
<prompt>tcsh > </prompt><userinput>setenv ESPEAKER
inet.addr.of.host:port</userinput>
</literallayout>
The client will connect to EsounD running on the specified host on the
specified port.
</para>
</sect1>
I think this should be visible from lisp with something like `esd-speaker',
because I might want to switch back and forth during the course of running
XEmacs. And should the connection to esd be persistent? Right now it
looks like it is opening/closing the connection for every sound.
This isn't a big deal for me anymore, since I have a SoundBlaster Live! in
the new machine, and it mixes everything together for me. No more need for
esd. :)
Now, if XEmacs were only multithreaded to take advantage of all the CPUs. :)
-bp