From: "Albert E. Sten-Clanton" <albert.e.sten_clanton@verizon.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Speakup in Combination with Emacspeak and others
Date: Thu, 01 Mar 2007 12:18:44 -0500 [thread overview]
Message-ID: <003f01c75c25$ab07f800$6405a8c0@ALBERTLC7SN0ZA> (raw)
In-Reply-To: <BAY102-DAV17083CC1B2F4FBEA158C048F800@phx.gbl>
You might just kill speakup and then run emacspeak. When you're done with emacspeak, you can then bring it back to life. I did it this morning using the left-most key of the three-key group on the far right of the function key row: that is, to the right of the three groups of four function keys. The same key kills it and brings it back. Hope this helps.
Al
----- Original Message -----
From: "Zachary Kline" <Z_kline@hotmail.com>
To: <Speakup@braille.uwo.ca>
Sent: Thursday, March 01, 2007 11:27 AM
Subject: Speakup in Combination with Emacspeak and others
> Hi,
> I was wondering if anybody could give me some advice about using Speakup in combination with Emacspeak, and possibly Orca for Gnome. I use software speech out of necescity, which implies speech-dispatcher and all that. I'm not sure if I need to echo to proc and disable the software or not.
> Any advice on the best approach to do this?
> Thanks,
> Zack.
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> --
> No virus found in this incoming message.
> Checked by AVG Free Edition.
> Version: 7.1.413 / Virus Database: 268.18.5/706 - Release Date: 2/28/2007
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
Zachary Kline
` Albert E. Sten-Clanton [this message]
` Steve Holmes
` Zachary Kline
` Sean McMahon
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='003f01c75c25$ab07f800$6405a8c0@ALBERTLC7SN0ZA' \
--to=albert.e.sten_clanton@verizon.net \
--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).