From: Christopher Moore <christopher.h.moore@verizon.net>
To: speakup@braille.uwo.ca
Subject: speakup & emacspeak
Date: Mon, 8 Sep 2003 13:35:26 -0400 [thread overview]
Message-ID: <20030908173526.GA244@chris> (raw)
Hello,
I'm running speakup-1.5 and tried that idea of killing speakup with the
prtscrn key before entering emacspeak. Well, it doesn't work as advertised
on my box. I think speakup still has control of the serial port, so
emacspeak complains with a "process speaker not running" message.
In the past, I recall receiving advice to create a separate lilo entry
witout speakup if you want to run emacspeak.
Perhaps things are different with speakup-2.0.
Chris
next reply other threads:[~ UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
Christopher Moore [this message]
` Ann Parsons
` Shaun Oliver
` Emacs Tutorial Richard Wells
` Kirk Reiser
` knoppix jack mendez
` knoppix Sina Bahram
` knoppix Kenny Hitt
` knoppix Sina Bahram
` knoppix Chris
` knoppix Ryan Mann
` knoppix jack mendez
` Emacs Tutorial Ann Parsons
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=20030908173526.GA244@chris \
--to=christopher.h.moore@verizon.net \
--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).