From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from saidin.asmodean.net ([216.254.114.61]) by speech.braille.uwo.ca with esmtp (Exim 3.35 #1 (Debian)) id 16szmb-0000gc-00 for ; Thu, 04 Apr 2002 00:27:38 -0500 Received: from raul by saidin.asmodean.net with local (Exim 3.35 #1 (Debian)) id 16szmB-0000gg-00 for ; Wed, 03 Apr 2002 23:27:11 -0600 Date: Wed, 3 Apr 2002 23:27:10 -0600 To: speakup@braille.uwo.ca Subject: Re: SpeakUp Cursor Tracking Message-ID: <20020404052710.GB2512@asmodean.net> Mail-Followup-To: speakup@braille.uwo.ca References: <004601c1da9b$c8cabb40$9189160c@robin> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: User-Agent: Mutt/1.3.28i From: "Raul A. Gallegos" Sender: speakup-admin@braille.uwo.ca Errors-To: speakup-admin@braille.uwo.ca X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.0.8 Precedence: bulk Reply-To: speakup@braille.uwo.ca List-Help: List-Post: List-Subscribe: , List-Id: Speakup is a screen review system for Linux. List-Unsubscribe: , List-Archive: Simple answer. Don't use pico when composing, use nano, it's much better and speakup reads the characters much better. Igor Gueths said the following on Wed, Apr 03, 2002 at 09:30:31PM -0500: > Hi. I have noticed a similar problem with pine. If I try to use the arrow > keys when typing a message, or the backspace key or the spacebar, that > character doesn't get sent to the synth. This only happens in the message > text box, and in the other fields it works fine. I'm not sure if this has > to do with the way the field is layed out. Does the latest cvs source > address this? I could probably look in the speakup sources and probably > figure it out in time, but this would take a while. -- If you are good, you will be assigned all the work. If you are real good, you will get out of it. Raul A. Gallegos - http://www.asmodean.net