From: "Joseph C. Lininger" <jbahm@pcdesk.net>
To: Speakup List <speakup@braille.uwo.ca>
Subject: cvs speakup and curser tracking
Date: Sat, 2 Aug 2003 22:58:49 -0600 (Mountain Daylight Time) [thread overview]
Message-ID: <Pine.WNT.4.56.0308022256220.1712@merlin> (raw)
Hello all,
I was just wondering if any of you have had some of the same curser tracking problems I have had with CVS Speakup. First, when I backspace in just about nay text editor, it doesn't read the characer that got deleted. Second, any program that uses any sort of moving highlight bar doesn't read at all. It used to work to some degree, but now it simply doesn't read the text being highlighted. Is there anything that can be done about this?
--
Joseph C. Lininger
jbahm@pcdesk.net
next reply other threads:[~ UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
Joseph C. Lininger [this message]
` Buddy Brannan
` Steve Holmes
` Thomas Stivers
` Janina Sajka
` Adam Myrow
` Janina Sajka
` William Hubbs
` Gregory Nowak
` Thomas Stivers
` Gene Collins
` Thomas Stivers
` Gregory Nowak
` Shaun Oliver
` Steve Holmes
` Buddy Brannan
` Thomas Stivers
` John covici
` Janina Sajka
` Steve Holmes
` Kenny Hitt
` Joseph C. Lininger
` Luke Davis
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.WNT.4.56.0308022256220.1712@merlin \
--to=jbahm@pcdesk.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).