public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: William Hubbs <w.d.hubbs@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: experience with speakup git of today tusing 2.6.25-gentoo-r5
Date: Tue, 1 Jul 2008 22:45:45 -0500	[thread overview]
Message-ID: <20080702034544.GA18325@linux1> (raw)
In-Reply-To: <Pine.LNX.4.64.0806302110170.3570@gube.gnpgvphfpbzzhavpngvbaf.arg>

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Mon, Jun 30, 2008 at 09:13:29PM -0400, luke wrote:
> On Sun, 29 Jun 2008, William Hubbs wrote:
> > Are you sure it was dead or crashed, or did you just lose speech?  The
> > reason I ask is you might have come across the  issue that happens when
> > we time out too many times waiting for the synth to tell us it can
> > receive more data -- after it times out so many times we  assume that
> > someone has turned off the synth and put it in an unavailable status.
> 
> Is that rectified by repeatedly pressing review keys until the speech 
> suddenly returns?  (five or six quick hits of a read current character key 
> usually brings it back for me)
> Or is what I experience a different issue?
 
I just looked at the code for this again, and it is rectified
by pressing printscreen.  This should turn speakup back on.

Thanks,

William

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.9 (GNU/Linux)

iEYEARECAAYFAkhq+egACgkQblQW9DDEZTj0TgCdFzPW858D9PjyGiqQy/+hrvGM
3lgAn2dPAyUtW7HQSJw6IKjauP7aiIsJ
=1SQf
-----END PGP SIGNATURE-----

  reply	other threads:[~ UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John covici
 ` William Hubbs
   ` John covici
     [not found]     ` <Pine.LNX.4.64.0806302114200.3570@gube.gnpgvphfpbzzhavpngvbaf.arg>
       ` John covici
   ` luke
     ` William Hubbs [this message]
     [not found] ` <20080629230330.GF5963@implementation>
   ` John covici
 luke

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=20080702034544.GA18325@linux1 \
    --to=w.d.hubbs@gmail.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).