public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: Michael Whapples <mikster4@msn.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Advice
Date: Sat, 03 Mar 2007 18:39:18 +0000	[thread overview]
Message-ID: <BAY103-DAV4DB6371ACA7FBA25146CF8E860@phx.gbl> (raw)
Message-ID: <1172947158.2904.29.camel@layla> (raw)
In-Reply-To: <BAY102-DAV16E93BA803ABD6409B8C218F870@phx.gbl>

I don't know the answer about speakup intercepting the key strokes, but
you can solve it with orca by re-defining the key commands. This can be
found in the orca control panel under its own tab.

From
Michael Whapples
On Fri, 2007-03-02 at 11:15 -0800, Zachary Kline wrote:
>    Hi,
>     I'd appreciate some advice on the topic of speakup cooperating with other programs.  I know that I asked yesterday for information on how to kill speakup, and for the most part that works as expected.  However, I find that somehow Speakup seems to still be intercepting my keyboard commands in some cases.  I want to use Orca's laptop layout: a requirement because I don't have a keypad.  It uses the capslock key for some of it's functions, the same as speakup.
> Any advice here?  When I built my kernel I didn't compile Speakup as a module, primarily because I wanted to get speech at boot as soon as possible.  Should I perhaps go the modular route here?
> Thanks,
> Zack.
> 




  reply	other threads:[~ UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Advice Zachary Kline
     [not found] ` <1172947158.2904.29.camel@layla>
   ` Michael Whapples [this message]
 ` Advice Chris Norman

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=BAY103-DAV4DB6371ACA7FBA25146CF8E860@phx.gbl \
    --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).