Another way that works.
tell application "VoiceOver"
        quit
                delay 0.1
        activate
end tell


On Nov 24, 2010, at 10:50 AM, Hai Nguyen wrote:

> here you go. I understand and should have sent the source code the first time.
> 
> --Author Hai Nguyen Ly November 24, 2010
> (*
> This Apple script will open Terminal.app and run a kill all command forcing 
> VoiceOver to restart. Once the command has been activated, Terminal will 
> quit. This script works best when associated with a keyboard shortcut in the 
> event VoiceOver decides to freeze.
> *)
> 
> tell application "Terminal"
>       activate
>       "killall -Hup VoiceOver '"
>       
>       say "restarting VoiceOver, Please wait"
>       tell application "Terminal"
>               quit
>       end tell
> end tell
> On Nov 24, 2010, at 12:44 PM, louie wrote:
> 
>> I will not use a script that I can't read the source.
>> How do we know that script will not cause all kinds of troubles on our Macs?
>> How about sharing the source code?
>> 
>> On Nov 24, 2010, at 10:32 AM, Hai Nguyen wrote:
>> 
>>> Good afternoon  all,
>>> The following Apple script will cause VO to restart gracefully. I suggest 
>>> for optimum efficiency to associate this script with a keyboard shortcut so 
>>> that it can be executed with one keystroke in the event VO freezes.
>>> http://dl.dropbox.com/u/4918985/VORestart.zip
>>> 
>>> Enjoy
>>> On Nov 24, 2010, at 11:53 AM, Carolyn wrote:
>>> 
>>>> Ah, leave it to Scott to bring us some grace.:)  I haven't a clue what 
>>>> y'all are talking about.  But I guess I should know this in case Alex ever 
>>>> decides to give me the silent treatment.  I don't recall an initial post 
>>>> on this but better save these in a backup for future reference.
>>>> To all who care:  Happy Thanksgiving
>>>> 
>>>> Carolyn
>>>> ----- Original Message -----
>>>> From: Scott Granados
>>>> To: macvisionaries@googlegroups.com
>>>> Sent: Wednesday, November 24, 2010 10:36 AM
>>>> Subject: Re: The KillAll command
>>>> 
>>>> Whoa -9 and -hup do * not * do the same thing.
>>>> 
>>>> 
>>>> -9 is a kill all with no graceful shutdown.  -HUP is a restart, -1 is a 
>>>> graceful shutdown.
>>>> 
>>>> 
>>>> On Nov 24, 2010, at 8:41 AM, Geoff Waaler wrote:
>>>> 
>>>>> Hi Eric and Nic,
>>>>> 
>>>>> Thanks much -- the -9 seems to cause a restart, hence appears to have the 
>>>>> identical affect of the -hup parm.
>>>>> 
>>>>> On Nov 24, 2010, at 3:22 AM, Nicolai Svendsen wrote:
>>>>> 
>>>>>> Hi!
>>>>>> 
>>>>>> True enough. -HUP accomplishes the same thing, though, but of course the 
>>>>>> parameters mean something different. I always just use -9 to ensure it 
>>>>>> actually quits, and it's just as efficient in the long-run. And, it's 
>>>>>> less parameters to type.
>>>>>> 
>>>>>> Regards,
>>>>>> ic
>>>>>> GoogleTalk: chojiro1...@gmail.com
>>>>>> Facebook
>>>>>> Twitter
>>>>>> Skype: Kvalme
>>>>>> MSN Messenger: nico...@home3.gvdnet.dk
>>>>>> Yahoo! Messenger: cin368
>>>>>> AIM: cincinster
>>>>>> 
>>>>>> On Nov 24, 2010, at 10:08 AM, Eric Oyen wrote:
>>>>>> 
>>>>>>> the killall command works. -9 will simply force it to quit. I prefer 
>>>>>>> the use of killall -HUP VoiceOver as it forces a reset of voiceover 
>>>>>>> without going through all the issues of restarting it via keystrokes.  
>>>>>>> btw, you must capitalize the V and the O otherwise it will not find the 
>>>>>>> process name.
>>>>>>> 
>>>>>>> -Eric
>>>>>>> 
>>>>>>> On Nov 24, 2010, at 1:53 AM, Geoff Waaler wrote:
>>>>>>> 
>>>>>>>> Greetings,
>>>>>>>> I meant to reply to one of Nic's recent posts, but  deleted it.  He 
>>>>>>>> suggested that if VO goes silent one could enter terminal into 
>>>>>>>> spotlight and then enter -- I forget the exact command but believe it 
>>>>>>>> was killallall -9 voiceover.
>>>>>>>> 
>>>>>>>> I tried this with and without the extra "all" and also tried inserting 
>>>>>>>> a space between the two alls, but only receive a message that no 
>>>>>>>> matching processes were found.
>>>>>>>> 
>>>>>>>> I'd like to get this right in case I do experience a vo crash.  May 
>>>>>>>> not have recalled the parm Nic mentioned, but I did use the one he 
>>>>>>>> specified (which may not have been -9).
>>>>>>>> 
>>>>>>>> TIA for any clarification, and best regards.
>>>>>>>> Geoff
>>>>>>>> 
>>>>>>>> -- 
>>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>>> Groups "MacVisionaries" group.
>>>>>>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>>>>>>> To unsubscribe from this group, send email to 
>>>>>>>> macvisionaries+unsubscr...@googlegroups.com.
>>>>>>>> For more options, visit this group at 
>>>>>>>> http://groups.google.com/group/macvisionaries?hl=en.
>>>>>>>> 
>>>>>>> 
>>>>>>> -- 
>>>>>>> You received this message because you are subscribed to the Google 
>>>>>>> Groups "MacVisionaries" group.
>>>>>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>>>>>> To unsubscribe from this group, send email to 
>>>>>>> macvisionaries+unsubscr...@googlegroups.com.
>>>>>>> For more options, visit this group at 
>>>>>>> http://groups.google.com/group/macvisionaries?hl=en.
>>>>>>> 
>>>>>> 
>>>>> 
>>>>> 
>>>>> -- 
>>>>> You received this message because you are subscribed to the Google Groups 
>>>>> "MacVisionaries" group.
>>>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>>>> To unsubscribe from this group, send email to 
>>>>> macvisionaries+unsubscr...@googlegroups.com.
>>>>> For more options, visit this group at 
>>>>> http://groups.google.com/group/macvisionaries?hl=en.
>>>> 
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "MacVisionaries" group.
>>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>>> To unsubscribe from this group, send email to 
>>>> macvisionaries+unsubscr...@googlegroups.com.
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/macvisionaries?hl=en.
>>>> 
>>>> -- 
>>>> You received this message because you are subscribed to the Google Groups 
>>>> "MacVisionaries" group.
>>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>>> To unsubscribe from this group, send email to 
>>>> macvisionaries+unsubscr...@googlegroups.com.
>>>> For more options, visit this group at 
>>>> http://groups.google.com/group/macvisionaries?hl=en.
>>> 
>>> 
>>> -- 
>>> You received this message because you are subscribed to the Google Groups 
>>> "MacVisionaries" group.
>>> To post to this group, send email to macvisionar...@googlegroups.com.
>>> To unsubscribe from this group, send email to 
>>> macvisionaries+unsubscr...@googlegroups.com.
>>> For more options, visit this group at 
>>> http://groups.google.com/group/macvisionaries?hl=en.
>> 
>> louie
>> louiem...@wavecable.com
>> 
>> 
>> 
>> -- 
>> You received this message because you are subscribed to the Google Groups 
>> "MacVisionaries" group.
>> To post to this group, send email to macvisionar...@googlegroups.com.
>> To unsubscribe from this group, send email to 
>> macvisionaries+unsubscr...@googlegroups.com.
>> For more options, visit this group at 
>> http://groups.google.com/group/macvisionaries?hl=en.
>> 
> 
> 
> -- 
> You received this message because you are subscribed to the Google Groups 
> "MacVisionaries" group.
> To post to this group, send email to macvisionar...@googlegroups.com.
> To unsubscribe from this group, send email to 
> macvisionaries+unsubscr...@googlegroups.com.
> For more options, visit this group at 
> http://groups.google.com/group/macvisionaries?hl=en.

louie
louiem...@wavecable.com



-- 
You received this message because you are subscribed to the Google Groups 
"MacVisionaries" group.
To post to this group, send email to macvisionar...@googlegroups.com.
To unsubscribe from this group, send email to 
macvisionaries+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/macvisionaries?hl=en.

Reply via email to