public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Victor Tsaran" <tsar@sylaba.poznan.pl>
To: <speakup@braille.uwo.ca>
Subject: Re: speakup+emacspeak+debian
Date: Mon, 18 Jun 2001 09:29:02 +0200	[thread overview]
Message-ID: <004b01c0f7ca$d9fb1860$0100a8c0@cybertsar> (raw)
In-Reply-To: <004601c0f7b8$f0ea3d60$0d27893e@essex.ac.uk>

[-- Attachment #1: Type: text/plain, Size: 976 bytes --]

I think there is some trick to it! Speakup intercepts all signals to the ttyS and Emacspeak cannot find a port.
Best,
Vic

  ----- Original Message ----- 
  From: Saqib Shaikh 
  To: speakup@braille.uwo.ca 
  Sent: Monday, June 18, 2001 7:38 AM
  Subject: speakup+emacspeak+debian


  hi all,
  in order to get a newbie up and running, i installed debian linux using speakup 0.10a. we now have a talking system using speakup. i then did
  apt-get install emacspeak-ss
  this went to the cd and installed emacspeak-ss, emacspeak, emacs, tcl, tclx, bla bla bla and all the things it needed. i then entered ins+enter on the keypad and typed emacspeak. emacs beeped at me. so i turned speakup back on to review the screen and anything i did, even c-x c-c resulted in "process speaker not running". in the past i have run just speakup, and currently i am running just emacspeak. i don't understand how to get both working at once.
  thanks for any help.
  saqib


[-- Attachment #2: Type: text/html, Size: 2264 bytes --]

  reply	other threads:[~ UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 speakup+emacspeak+debian Saqib Shaikh
 ` Victor Tsaran [this message]
 ` speakup+emacspeak+debian Terry D. Cudney
   ` speakup+emacspeak+debian Cheryl Homiak
   ` speakup+emacspeak+debian The Electronicman Scott Berry
     ` speakup+emacspeak+debian Gregory Nowak
       ` speakup+emacspeak+debian The Electronicman Scott Berry
   ` speakup+emacspeak+debian Geoff Shang
 ` speakup+emacspeak+debian 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='004b01c0f7ca$d9fb1860$0100a8c0@cybertsar' \
    --to=tsar@sylaba.poznan.pl \
    --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).