Hey Willie, If I remember correctly, we dealt with this situation in outSPOKEN for Windows with an overridden version of "shutup" that recognized the situation of streaming output into a terminal window, and suppressed all further speech output only from that window. The moment the user typed something else, this "shutup" would be lifted until the next time the user hit the "shutup" key. A useful modification to this would be to recognize the terminal prompt, and say something like "done" when that appears alone on the last line of output (and since outSPOKEN didn't have scripting support, we weren't in a good position to attempt that modification). Regards, Peter Korn Accessibility Architect, Sun Microsystems, Inc. I can reproduce this by doing a "find /" in gnome-terminal. What's happening is that Orca is reading output as it goes flying by. To avoid this, you can do things such as: 1) Redirect the output to a file 2) Minimize the offending window 3) Give focus to another window (Alt+Tab) 4) Disable speech (Insert+s) before doing a command you know will produce lots of output. Insert+s again will re-enable speech. Dealing with this in more automatic creative ways may be a challenge, since we don't really know how much output we're going to get from these kinds of commands. People also want to get presentation of one and two-line output, so we cannot just always disable speech. I'd like to hear what ideas people have for how we might address this. Will Paul Hunt wrote:Hi, I get this all the time with Orca when in gnome-terminal. If I do a command that produces a lot of text like apt-get or commands for building packages. This is on Ubuntu Hardy RC. Haven't seen it outside of gnome-terminal but I haven't been using Orca that long. Is there anything that can be done to stop it happening? Paul ----- Original Message ----- From: "Willie Walker" <William Walker Sun COM> To: "Kenny Hitt" <kenny hittsjunk net> Cc: <orca-list gnome org> Sent: Wednesday, April 23, 2008 12:37 PM Subject: Re: [orca-list] unable to stop speech with Orca 2.22.Hi Kenny: This is sometimes an indication that the AT-SPI registry daemon has died or that an AT-SPI call that Orca made has hung (*&*&^#*$ CORBA doesn't seem to have timeouts for calls). Are you experiencing this solely when running a command from gnome-terminal? Will On Apr 23, 2008, at 2:01 AM, Kenny Hitt wrote:Hi. It looks like I can get Orca into a state where I can't silence speech. The first time it happened was when I ran a fetchmail command that produced a large amount of output. Pressing control didn't stop speech. repeated presses of control didn't work either. Switching to another window with alt-tab also didn't help. I was finally forced to do a killall orca to get speech to stop. The second time it happened was because I held down the read line key (keypad 8) on the desktop layout. Once again, I tried everything I could think of to stope speech with no results. I finally had to killall orca to get it to stop. Can anyone else reproduce this problem? I'm running Orca 2.22.1, gnome-speech 0.4.18. I'm using the espeak driver. Before I try to file a bug, I'd like to hear from others to see if this is a general problem or something specific to my setup. Kenny _______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca_______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca_______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca_______________________________________________ Orca-list mailing list Orca-list gnome org http://mail.gnome.org/mailman/listinfo/orca-list Visit http://live.gnome.org/Orca for more information on Orca |