speakout/direct and control codes

[Steve Holmes]

Yes, I was using echo commands.  I thought the backslash was the escape
code needed; didn't know another one was needed.  I just went over and
tried it with \\x05... and it does seem to work as advertised.  However,
\\005 did not.  Perhaps I'm missing something when it comes to escaping
values with the bash shell.  The speakout has some neat features and I
think it will be fun to write some perl scripts or something to use these
features.  It is a kind of take back to the DOS days when we could echo
whatever we wanted to the synthesiser.

Sorry for the false alarm, Jim and Kirt.


On 30 Mar 2001, John Covici wrote:

> If you are using echo statements, don't forget to double the back
> slahs because its necessary for the shell to see a backslash.
> 
> "Steve Holmes" <steve at holmesgrown.com> writes:
> 
> > I just installed the latest CVS version of speakup using the 2.2.18 kernel
> > and I find that the control-E character does not get escaped when sending
> > it to /proc/speakup/speakout/direct.  When I use \005 in front of a
> > command, I hear "005" followed by the command.  I get similar results when
> > trying ^E and such.  Isn't this supposed to work?
> > 
> > Let me know if I missed something.
> > 
> > P.S.  I know I'm running the latest version since I can get tone J to take
> > now.  That didn't work with speakup-0.10A production version.
> > 
> > 
> > _______________________________________________
> > Speakup mailing list
> > Speakup at braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> 
>