From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from opera.rednote.net (opera.rednote.net [208.111.39.221]) by speech.braille.uwo.ca (Postfix) with ESMTP id 740C1C1A17D for ; Thu, 18 Nov 2010 15:34:32 -0500 (EST) Received: from sonata.rednote.net (sonata.rednote.net [IPv6:2001:470:8:4ef:216:d3ff:fecc:ec01]) by opera.rednote.net (8.14.4/8.14.3) with ESMTP id oAIKYUZN009648 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO) for ; Thu, 18 Nov 2010 20:34:31 GMT Received: from sonata.rednote.net (sonata.rednote.net [127.0.0.1]) by sonata.rednote.net (8.14.4/8.14.3) with ESMTP id oAIKYTLr009009 for ; Thu, 18 Nov 2010 15:34:29 -0500 Received: (from janina@localhost) by sonata.rednote.net (8.14.4/8.14.4/Submit) id oAIKYT7x009007 for speakup@braille.uwo.ca; Thu, 18 Nov 2010 15:34:29 -0500 X-Authentication-Warning: sonata.rednote.net: janina set sender to janina@rednote.net using -f Date: Thu, 18 Nov 2010 15:34:29 -0500 From: Janina Sajka To: "Speakup is a screen review system for Linux." Subject: Re: If bash can, why not Speakup? Message-ID: <20101118203429.GF2358@sonata.rednote.net> References: <98haom$7bpkcl@ipmail06.adl6.internode.on.net> <20101117233043.GA26689@linux1> <66C69DD6A5F94BFCB6951A9C97A97D34@ownercb76d9f6c> <20101118011817.GB2891@lnx3.holmesgrown.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Disposition: inline In-Reply-To: <20101118011817.GB2891@lnx3.holmesgrown.com> X-Operating-System: Linux sonata.rednote.net 2.6.35.6-48.spk.fc14.x86_64 X-PGP-Key: http://rednote.net/JaninaSajka_gpg_key.html User-Agent: Mutt/1.5.21 (2010-09-15) X-BeenThere: speakup@braille.uwo.ca X-Mailman-Version: 2.1.13 Precedence: list Reply-To: "Speakup is a screen review system for Linux." List-Id: "Speakup is a screen review system for Linux." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 18 Nov 2010 20:34:32 -0000 Steve, that would sure drive me crazy. In fact I doubt I'd be willing to live with it. All I can tell you is that it ain't happenin to me. I was having an issue in vim where Speakup would read the char I left plus the new char I had just written, but this wnet away entirely when I switched back to iso 8859-1. Janina Steve Holmes writes: > I realize the more this gets talked about, the more diluted it > probably becomes. When I insert text with Vim or when I insert text in a command > line in Bash, speakup speaks everything following in that line. I'm > sure this is because screen contents are being changed ans speakup > reflects this. However, The old vi editor (probably elvis or > something) doesn't seem to exhibit this behavior but vim does. I > usually have cursoring on when I do this. I don't remember if this > changes when it is turned off. > > Another thing that would help speakup behave better with curses type > applications would be to add support for user defined windows where > parts of the screen could be spoken or blocked. This would be like > what is available in Vocal-Eyes and Window-Eyes for that matter. This > is obviously a big project and I think it would be fun to add but not > sure how well that would work in a kernel based program. > > On Wed, Nov 17, 2010 at 07:48:38PM -0500, Albert Sten-Clanton wrote: > > In addition to the suggestion below, I'd very much like to hear the > > characters I'm backspacing over. I asked about this a few years ago, but I > > gathered that this wasn't easy to do. Any thoughts? > > > > Al > > > > -----Original Message----- > > From: speakup-bounces@braille.uwo.ca [mailto:speakup-bounces@braille.uwo.ca] > > On Behalf Of William Hubbs > > Sent: Wednesday, November 17, 2010 6:31 PM > > To: speakup@braille.uwo.ca > > Subject: Re: If bash can, why not Speakup? > > > > On Thu, Nov 18, 2010 at 09:23:29AM +1000, pj@pjb.com.au wrote: > > > Janina Sajka wrote: > > > > I've been happily using vim for years. > > > > > > How do you cope with the endlessly-updating bottom line?, like: > > > "497L, 15593C 450,2 93%" > > > > > > I find speakup is in general difficult with curses applications > > > because of their screen-update optimisation. The characters don't > > > necessarily come out in a text-related order. > > > > You can disable that line by putting the following line in your > > ~/.vimrc: > > > > set noruler > > > > > > My biggest complaint is that I need to be ultra-careful to track > > > > whether I'm in insert or command mode, i.e. it would sure help if > > > > Speakup could give me a differently pitched voice > > > > > > Good point :-) It might need some help from the vim folk... > > > > Yes, something like this would take modifications to vim to make it > > communicate to speakup some how, and I'm not sure what that would involve > > since I haven't looked at the vim code at all. > > > > William > > > > _______________________________________________ > > 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 > _______________________________________________ > Speakup mailing list > Speakup@braille.uwo.ca > http://speech.braille.uwo.ca/mailman/listinfo/speakup -- Janina Sajka, Phone: +1.443.300.2200 sip:janina@asterisk.rednote.net Chair, Open Accessibility janina@a11y.org Linux Foundation http://a11y.org Chair, Protocols & Formats Web Accessibility Initiative http://www.w3.org/wai/pf World Wide Web Consortium (W3C)