From: Roy Nickelson <roylee@visuallink.com>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: Effortless editing with Speakup
Date: Wed, 12 May 2004 21:35:50 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.4.44.0405122133540.13580-100000@localhost.localdomain> (raw)
In-Reply-To: <007501c43862$60a12320$cc00a8c0@nickysp4>
Hi,
I have the same problem in vi. pico isn't much better when ou are
inserting text sometimes after you type a letter speakup reads the next
word. And the worst example is in naim speakup says "space" before
every character that is typed.
Roy
On Wed, 12 May 2004, nick G wrote:
> Actually, VI has a little proble. Everytime I type something it says
> something to the effect of,
> t 1
> h2
> i3
> s4
> space 5
> i6
> s7
>
> YOu get the idea.
> Thanks,
> Nick
> ----- Original Message -----
> From: "Kirk Reiser" <kirk@braille.uwo.ca>
> To: <norlingdeborah@fhda.edu>
> Cc: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
> Sent: Wednesday, May 12, 2004 1:54 PM
> Subject: Re: Effortless editing with Speakup
>
>
> > This is bullshit! There are extremely powerful editors you can use and
> > they work just fine. Either vim or emacs can do just about anything
> > you want and they work fine with the cvs cursor tracking code. Cursor
> > tracking works fine under speakup 1.5 except it doesn't automatically
> > speak but the cursor should track no problems. On the other hand
> > nobody should be using speakup 1.5 anymore.
> >
> > Kirk
> >
> > --
> >
> > Kirk Reiser The Computer Braille Facility
> > e-mail: kirk@braille.uwo.ca University of Western Ontario
> > phone: (519) 661-3061
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
Debee Norling
` Gregory Nowak
` Roy Nickelson
` Gregory Nowak
` Debee Norling
` Buddy Brannan
` Kirk Reiser
` nick G
` Janina Sajka
` Terry Klarich
` Thomas Stivers
` Roy Nickelson [this message]
` Where, and what is the latest version of speakup?! cris
` Kirk Reiser
` Roy Nickelson
` Gregory Nowak
` Roy Nickelson
` Steve Holmes
` Effortless editing with Speakup Alex Snow
` Stephen Clower
` Debee Norling
` Chuck Hallenbeck
` Hart Larry
` Janina Sajka
` Luke Davis
` Jared Stofflett
` Debee Norling
` Alex Snow
-- strict thread matches above, loose matches on Subject: below --
Debee Norling
` Gregory Nowak
` Thomas Stivers
` Hart Larry
` Chuck Hallenbeck
` Steve Holmes
` Gene Collins
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=Pine.LNX.4.44.0405122133540.13580-100000@localhost.localdomain \
--to=roylee@visuallink.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).