Re: [Emacs-vr-mode-users] problems with correct that

[Patrik <pa...@uc...>]

Hi Colin,

No, this is not normal.  It will happen occasionally when the VR mode 
buffer gets out of sync with the Emacs buffer.  The most common reason for 
this is the use of the abbreviation commands in PBVElse.el.  Are you using 
these?  (If you don't know what I'm talking about, you're probably 
not.  It's the ability to say simple navigation commands, like "backward 
char", in the middle of a sentence.)

Just to make sure, the problem occurs in a "voice-activated" buffer, 
right?  The simplest way to confirm this is to make sure that it says "VR: 
on" (and not "VR-on") in the mode line.  Another way to confirm this is 
that you can use select and say in the buffer.  If you are NOT in an 
activated buffer, and you ARE using NaturallySpeaking version 7, this is 
due to a well-known NaturallySpeaking bug introduced in version 7 which 
broke correction in any sort of nonstandard windows like Emacs, the command 
prompt window or terminal windows.  This bug was severe enough (in 
combination with some others) to make me roll back to NaturallySpeaking 6.1.

If the above does not apply, you have a VR mode problem.  Can you send me 
some more information, like:

NaturallySpeaking version
VR mode version
Emacs version

also, try saying "resynchronize", and then dictating something and see if 
the correction works.  Can you discern any pattern when it does not work?

/Patrik

At 03:01 PM 9/26/2003 -0700, cr wrote:

>Hi there,
>
>One of my greatest frustrations with vr-mode is the way that it does not 
>seem to be able to handle the replacement part of the "correct that" 
>function. I get the window, selection works fine, but when it comes to 
>replacing the actual text it's usually off by one or two characters.
>
>Is this just me or is it a well-known bug.
>
>Thanks,
>
>Colin