public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Littlefield, Tyler" <compgeek13@gmail.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: 2 questions: "echo" and starting automatically
Date: Sat, 16 Jun 2007 23:45:00 -0600	[thread overview]
Message-ID: <000201c7b0f9$603c2c50$6401a8c0@GRANDMA> (raw)
In-Reply-To: <Pine.LNX.4.64.0706162109130.19234@mylaptop>

if you're using debian. this may not be the best way, but it works for me.
:)
cd /etc/init.d
pico
<commands here>
save as the name of script you want.
chmod ug+x script
update-rc.d defaults script 15
HTH,
Thanks,
~~TheCreator~~
[My programs don't have bugs; just randomly added features]
msn:
compgeek13@gmail.com
aim: st8amnd2005
skype: st8amnd127
vertigo head coder
web: tysdomain.com
----- Original Message ----- 
From: "Terrence van Ettinger" <terrence@terrencevak.net>
To: <Speakup@braille.uwo.ca>
Sent: Saturday, June 16, 2007 11:12 PM
Subject: 2 questions: "echo" and starting automatically


> Hello, all,
>   I have 2 questions regarding speakup.  First, I'm using speakup
> with festival and speech-dispatcher, and I occasionally get a sort of
> broken echo.  Is there a way to fix this?  Second, is there a way I can
> have speech-dispatcher and speechd-up start automatically with the
> computer?  I always have to do it manually after login.
>
> Thanks,
> Terrence
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup



  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 Terrence van Ettinger
 ` Littlefield, Tyler [this message]
 ` Littlefield, Tyler
   ` Terrence van Ettinger
     ` Jan Buchal
       ` Hermann
         ` Jan Buchal
           ` Hermann
             ` Jan Buchal
               ` Hermann
               ` Hermann
                 ` Zachary Kline
             ` Terrence van Ettinger

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='000201c7b0f9$603c2c50$6401a8c0@GRANDMA' \
    --to=compgeek13@gmail.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).