From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Sleep functionality for Speakup with XWindow
Date: Tue, 21 Nov 2006 12:47:12 +0000 [thread overview]
Message-ID: <cone.1164113232.857906.4215.0@layla> (raw)
In-Reply-To: <000601c70d50$9a3c3410$230110ac@JIMPERSONAL1>
It would be better to have some of those features that Jim suggests, but for
just silencing speakup doing
echo none > /proc/speakup/synth_name
would work. I don't know if that would stop speakup intercepting keypresses,
may be someone can answer that.
Using speakup to control synths would be nice, but I don't like the idea
when a software synth is used in speakup, orca, speakup (possibly with a
driver bridging those), speechd-up, speech-dispatcher and then finally the
TTS, just seems too much to me.
From
Michael Whapples
Jim Grimsby JR. writes:
> Hi another idea is if it could be done. Have speakup in some way find the x
> windows screen reader and start it. Also if the x window screen reader
> could talk to the speakup modgel. So if you started speakup with a dectalk
> express for example the screen reader would talk threw the dectalk express.
> Also if you do not have access enabled speakup trying to start it would
> cause it to be turned on. Not sure if this is doable but it seems to me to
> be more helpful then just speakup going to sleep.
>
> -----Original Message-----
> From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca]
> On Behalf Of Sean Murphy
> Sent: Tuesday, November 21, 2006 1:14 AM
> To: Speakup is a screen review system for Linux.
> Subject: Sleep functionality for Speakup with XWindow
>
>
> All.
>
> I would like Speakup to go into a sleep mode when you switch to a XWindow
> console. This sleep mode should tell speakup not intercept any keystrokes
> or speak. Once you move back into the text console, speakup automatically
> comes alive.
>
> This would resolve problems with key conflicts with XWindow screen readers
> and speakup trying to read XWindow screens.
>
> I don't want to have to kill the module for Speakup everytime I have to go
> into XWindow. Xwindow is an up coming option for everyone. So lets put in
> the ability of doing this.
>
> Sean
> _______________________________________________
> 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.5.430 / Virus Database: 268.14.11/542 - Release Date: 11/20/2006
> 4:23 PM
>
>
>
>
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
Sean Murphy
` Jim Grimsby JR.
` Michael Whapples [this message]
` Chris Norman
` David Csercsics
` Samuel Thibault
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=cone.1164113232.857906.4215.0@layla \
--to=mikster4@msn.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).