public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Léonie Watson" <lw@nomensa.com>
To: "Speakup" <speakup@braille.uwo.ca>
Subject: Conflict with Emacspeak?
Date: Mon, 15 Sep 2003 15:05:18 +0100	[thread overview]
Message-ID: <007301c37b92$8a6e1e20$1e02a8c0@danlo2> (raw)

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/



             reply	other threads:[~ UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Léonie Watson [this message]
 ` Kenny Hitt
   ` jack mendez
   ` Cheryl Homiak
     ` Kenny Hitt
       ` Shaun Oliver
   ` Danny Crone
     ` Kenny Hitt
     ` Léonie Watson
   ` 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='007301c37b92$8a6e1e20$1e02a8c0@danlo2' \
    --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).