From: Janina Sajka <janina@afb.net>
To: blinux-list@redhat.com
Subject: Re: Speakup questions
Date: Thu, 15 Aug 2002 12:56:10 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0208151255170.3268-100000@TekRD.grg.afb.net> (raw)
In-Reply-To: <3.0.5.32.20020815210155.00819430@bgl.vsnl.net.in>
Hmmm, don't know about an automated scripting, but would expect something
is workable as Speakup's control parms are all in /proc/speakup.
The PrintScreen is used as an on/off toggle.
On Thu, 15 Aug 2002, Geetha Shamanna wrote:
> >I don't do it this way, so I'm likely not the best to answer, but why not
> >just kill Speakup in your emacspeak console with the PrintScreen key?
> And how does one reinvoke Speakup when one exits Emacspeak?
>
> Is it possible to configure things in such a way that Speakup is
> automatically killed when one runs Emacspeak, and reinvoked when one exits
> Emacspeak? Just curious.
>
> Geetha
> At 10:10 AM 15/08/02 -0400, you wrote:
> >
> >I don't do it this way, so I'm likely not the best to answer, but why not
> >just kill Speakup in your emacspeak console with the PrintScreen key?
> >
> >Also, you have the option of software speech with emacspeak using
> >eflite--see:
> >
> > http://eflite.sf.net
> >
> >On Thu, 15 Aug 2002, Dave Hunt < wrote:
> >
> >> If you wish to use the same synth for both, it will have to be one or
> >> You can use the same synthesizer for both, but not simultaniously. If
> >> you wish to run emacspeak, boot a kernel without speakup or its
> >> default keymap.
> >>
> >> -Dave
> >>
> >> Geetha Shamanna writes:
> >> > I plan to use the same internal synthesizer for both Speakup and
> Emacspeak
> >> > (DoubleTalk PC internal). Is that likely to cause problems?
> >>
> >>
> >>
> >> _______________________________________________
> >> Blinux-list mailing list
> >> Blinux-list@redhat.com
> >> https://listman.redhat.com/mailman/listinfo/blinux-list
> >>
> >
> >--
> >
> > 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
> >
> >
> >
> >_______________________________________________
> >Blinux-list mailing list
> >Blinux-list@redhat.com
> >https://listman.redhat.com/mailman/listinfo/blinux-list
> >
> >
> >
> >---
> >Incoming mail is certified Virus Free.
> >Checked by AVG anti-virus system (http://www.grisoft.com).
> >Version: 6.0.381 / Virus Database: 214 - Release Date: 02/08/02
> >
>
>
>
> _______________________________________________
> Blinux-list mailing list
> Blinux-list@redhat.com
> https://listman.redhat.com/mailman/listinfo/blinux-list
>
--
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
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
Geetha Shamanna
` Janina Sajka
` Dave Hunt <
` Geetha Shamanna
` Dave Hunt <
` Janina Sajka
` Geetha Shamanna
` Janina Sajka [this message]
[not found] ` <Pine.LNX.4.44.0208141404080.26724-100000@TekRD.grg.afb.net >
` Geetha Shamanna
` Janina Sajka
` ADFM
` John
` Janina Sajka
` John
` Jude DaShiell
` David Csercsics
` John
` Pawel (Paul) Loba
` Janina Sajka
` Janina Sajka
[not found] ` <Pine.LNX.4.44.0208141607110.26724-100000@TekRD.grg.afb.net >
` Geetha Shamanna
-- strict thread matches above, loose matches on Subject: below --
speakup questions Kristoffer Gustafsson
` Buddy Brannan
` Kirk Reiser
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=Pine.LNX.4.44.0208151255170.3268-100000@TekRD.grg.afb.net \
--to=janina@afb.net \
--cc=blinux-list@redhat.com \
/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).