public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Igor Gueths" <igueths@attbi.com>
To: <speakup@braille.uwo.ca>
Subject: Re: emacspeak
Date: Tue, 7 May 2002 14:39:06 -0400	[thread overview]
Message-ID: <002501c1f5f6$788497c0$02213e18@mycomputer> (raw)
In-Reply-To: <Pine.LNX.4.44.0205061742230.3734-100000@toccata.grg.afb.net>

Hi Janina. Well what happens is that first, I hit pint screen to so-called kill Speakup. Next, I type emacspeak. When I get Speakup up again to see why I got a \a (bell character), I see that at the bottom it says process speaker not running. I believe that this has to do with the i/o errors I was getting while trying to test the speech server with tcl. Also, I might be getting another dectalk express sometime in the future. If I plug that into my other serial port /dev/ttyS1, and re-export the dtk_port variable, could this possibly fix the problem? Or possibly using viavoice instead? Thanks!
----- Original Message ----- 
From: Janina Sajka <janina@afb.net>
To: <speakup@braille.uwo.ca>
Sent: Monday, May 06, 2002 11:43 PM
Subject: Re: emacspeak


> Igor:
> 
> What happens when you launch emacspeak?
> 
> I presume you boot with Speakup. So, what happens when you
> launch Emacspeak?
> On Mon, 6 May 2002, Igor Gueths wrote:
> 
> > Hi all. Where can I find the resolution to this issue? What keywords
> > should I search for in the vassar archives? Thanks!
> > 
> > On Mon, 6 May 2002, Janina Sajka wrote:
> > 
> > > Speakup and emacspeak can share the same hardware synth.
> > >
> > > This issue was resolved some time ago.
> > >
> > > On Mon, 6 May 2002, Igor Gueths wrote:
> > >
> > > > Hi Janina and Hi all. Janina, I understand you are on the Emacspeak list
> > > > as well as the Speakup list, as I have subscribed to it. Do you or anyone
> > > > else, for that matter, know if Speakup interferes with i/o even after you
> > > > hit print-screen and Speakup is killed so I can start Emacspeak? Because I
> > > > have been getting basically I/o errors when testing the dtk-exp speech
> > > > server with tcl. Does anyone know if this is the case? Because I was
> > > > mainly going to use it for possibly Emacs itself (I've been digging around
> > > > Emacs docs for quite a while), and possibly running something like Tnt.
> > > > Can Tnt run under a Bash console, since it runs under a sort of shell
> > > > anyway? The only difference is that it is inside of Emacs not at a regular
> > > > Tcsh/Bash prompt? Any insite on this would be appreciated. Thanks!
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > > --
> > >
> > > Janina Sajka, Director
> > > Technology Research and Development
> > > Governmental Relations Group
> > > American Foundation for the Blind (AFB)
> > >
> > > Email: janina@afb.net Phone: (202) 408-8175
> > >
> > > Chair, Accessibility SIG
> > > Open Electronic Book Forum (OEBF)
> > > http://www.openebook.org
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > 
> 
> -- 
> 
> Janina Sajka, Director
> Technology Research and Development
> Governmental Relations Group
> American Foundation for the Blind (AFB)
> 
> Email: janina@afb.net Phone: (202) 408-8175
> 
> Chair, Accessibility SIG
> Open Electronic Book Forum (OEBF)
> http://www.openebook.org
> 
> 
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  parent reply	other threads:[~ UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 emacspeak Igor Gueths
 ` emacspeak Adam Myrow
   ` emacspeak Alex Snow
     ` emacspeak Igor Gueths
       ` emacspeak Alex Snow
         ` emacspeak 'Georgina'
   ` emacspeak Igor Gueths
     ` emacspeak Adam Myrow
 ` emacspeak Janina Sajka
   ` emacspeak Igor Gueths
     ` emacspeak Buddy Brannan
     ` emacspeak Janina Sajka
       ` emacspeak Ann Parsons
         ` emacspeak Janina Sajka
           ` emacspeak Ann Parsons
             ` emacspeak Janina Sajka
               ` emacspeak Ann Parsons
       ` Igor Gueths [this message]
         ` emacspeak Janina Sajka
           ` emacspeak Igor Gueths
             ` emacspeak Igor Gueths
             ` emacspeak Janina Sajka
               ` emacspeak Alex Snow
                 ` emacspeak Janina Sajka
 emacspeak Igor Gueths
     [not found] <E175EXw-0003n8-00@speech.braille.uwo.ca>
 ` emacspeak Thomas Ward
 interesting experiment Adam Myrow
 ` Alex Snow
   ` Ann Parsons
     ` Octavian Rasnita
       ` Ann Parsons
         ` emacspeak brian Moore
           ` emacspeak Saqib Shaikh
             ` emacspeak brian Moore
             ` emacspeak Janina Sajka
               ` emacspeak brian Moore
               ` emacspeak Dave Hunt <
           ` emacspeak Ann Parsons
             ` emacspeak Janina Sajka
           ` emacspeak Dave Hunt <
 Emacspeak Scott Howell
 ` Emacspeak Janina Sajka

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='002501c1f5f6$788497c0$02213e18@mycomputer' \
    --to=igueths@attbi.com \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).