From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: by befuddled.reisers.ca (Postfix, from userid 65534) id 716E51F0507; Sun, 28 May 2017 18:38:43 -0400 (EDT) Received: from mail0205.smtp25.com (mail0205.smtp25.com [174.37.170.205]) by befuddled.reisers.ca (Postfix) with ESMTPS id 2B3021F03C3 for ; Sun, 28 May 2017 18:38:42 -0400 (EDT) Received: from ccs.covici.com (localhost [127.0.0.1]) by ccs.covici.com (8.14.9/8.14.8) with ESMTP id v4SMcdhr025447 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NOT); Sun, 28 May 2017 18:38:39 -0400 Received: (from covici@localhost) by ccs.covici.com (8.14.9/8.13.7/Submit) id v4SMcduR025445; Sun, 28 May 2017 18:38:39 -0400 Date: Sun, 28 May 2017 18:38:39 -0400 Message-ID: From: John Covici To: Okash Khawaja Cc: "Speakup is a screen review system for Linux." Subject: Re: speakup-r functionality In-Reply-To: <20170528204856.GA883@sanghar> References: <20170528204856.GA883@sanghar> User-Agent: Wanderlust/2.15.9 (Almost Unreal) SEMI-EPG/1.14.7 (Harue) FLIM/1.14.9 (=?ISO-8859-4?Q?Goj=F2?=) APEL/10.8 EasyPG/1.0.0 Emacs/25.2 (x86_64-pc-linux-gnu) MULE/6.0 (HANACHIRUSATO) Reply-To: covici@ccs.covici.com Organization: Covici Computer Systems MIME-Version: 1.0 (generated by SEMI-EPG 1.14.7 - "Harue") Content-Type: text/plain; charset=US-ASCII X-SpamH-Filter: s-out-001.smtp25.com-v4SMcd6W016695 X-SpamH-OriginatingIP: 70.109.53.110 X-Bogosity: Ham, tests=bogofilter, spamicity=0.000000, version=1.2.4 X-BeenThere: speakup@linux-speakup.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 28 May 2017 22:38:43 -0000 I just have one question -- how did it work with the old serial i/o system? On Sun, 28 May 2017 16:48:56 -0400, Okash Khawaja wrote: > > On Sun, May 28, 2017 at 02:39:17PM -0400, John Covici wrote: > > Well, find a document such as a text file -- I use emacs for this, but > > I suppose any editor will work -- of course it has to be in a text > > console. Now, make sure the synthesizer supports indexing -- I think > > indexing support was not implemented for all drivers. Now do > > speakup-r and the file should be spoken and when you hit the control > > key the cursor should be where the last word spoken. Currently its a > > number of lines down. Try this with the old speakup with the serial > > workaround patch to hear what it is supposed to b like. > > > > Hope this helps. > Thanks. I don't have a synth that supports indexing. But it looks like > this fix by Dan Carpenter likely addresses the issue: > http://linux-speakup.org/pipermail/speakup/2017-May/060802.html > > handle_cursor_read_all() in main.c ultimately calls into > spk_ttyio_in_nowait. If value returned by spk_ttyio_in_nowait() is 0xff > when 0x00 is expectd then sentence count and index count will be > different (higher in this case) than expected. > > I have update speakup.tgz to include this fix. If the above explanation > makes sense then please test it when possible. > > Okash -- Your life is like a penny. You're going to lose it. The question is: How do you spend it? John Covici covici@ccs.covici.com