From: "Léonie Watson" <lw@nomensa.com>
To: <speakup@braille.uwo.ca>
Subject: Re: Conflict with Emacspeak?
Date: Mon, 15 Sep 2003 20:03:54 +0100 [thread overview]
Message-ID: <010001c37bbc$90a13d20$ac85ccd9@shakespeare> (raw)
In-Reply-To: <Pine.LNX.4.44.0309151233510.854-100000@localhost.localdomain>
For my part, exploring the possibilities with a view to writing a paper on
the accessibility of linux to a newbie.
Other than that, I can quite see that either one or the other would be
prefferable.
Cheers,
Tink
----- Original Message -----
From: "Danny Crone" <dannyboy@pobox.com>
To: <speakup@braille.uwo.ca>
Sent: Monday, September 15, 2003 5:34 PM
Subject: Re: Conflict with Emacspeak?
> If Emacs can be used with speakup, what would be the advantage of using
> Emaccspeak?
>
> On Mon, 15 Sep 2003, Kenny Hitt wrote:
>
> > Hi. If you're trying to get emacspeak to use the same synth as speakup,
> > you will need to boot using a kernel without speakup for emacspeak to
use it.
> > The print screen key doesn't unload speakup, it just stops it from doing
> > anything on the current console. Since speakup got the synth when the
> > system booted, no other screen reader can use it. Speakup does have a
> > way to let other programs talk to the synth, but the other programs will
> > have to be written to use it.
> >
> > Kenny
> >
> > On Mon, Sep 15, 2003 at 03:05:18PM +0100, Léonie Watson wrote:
> > > All,
> > >
> > > I'm still suffering the conflict between Speakup and Emacspeak on
my
> > > Debian (testing) distro.
> > >
> > > I've tried using the printscr key to unload Speakup before
entering
> > > Emacspeak, but Speakup doesn't unload.
> > >
> > > I'm using a Dectalk Express, should this make any difference and
at this
> > > time, really don't know enough to figure out much for myself.
> > >
> > > Apologies to those on the Emacspeak list, where I am also pursuing
this
> > > enquiry, for the dual post.
> > >
> > > Thanks,
> > > Tink
> > > --
> > > Léonie Watson | t. +44 (0) 117 344 5012
> > >
> > > Visit our web site today:
> > > http://www.nomensa.com/
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
Léonie Watson
` Kenny Hitt
` jack mendez
` Cheryl Homiak
` Kenny Hitt
` Shaun Oliver
` Danny Crone
` Kenny Hitt
` Léonie Watson [this message]
` Léonie Watson
` Shaun Oliver
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='010001c37bbc$90a13d20$ac85ccd9@shakespeare' \
--to=lw@nomensa.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).