On 2006-06-07, Jared <[EMAIL PROTECTED]> wrote:
> On 06/07/2006 15:10, Gary Johnson wrote:
> > On 2006-06-07, Jared <[EMAIL PROTECTED]> wrote:
> > I haven't been following this discussion very closely, but I just
> > tried the experiment on Red Hat Linux 9, SunOS 5.8 and Windows XP
> > with vim 7.0, no patches, and the cursor always goes to the 'o' in
> > the third line. Is that what you were looking for?
>
> Which test case are you using? My original snippet:
>
> let g:loaded_autoit_completion = 1
> let s:cache_name = []
> " This function is used for the 'omnifunc' option.
>
> Or Benji's:
>
> long line
> ()
> another
>
> Reason I'm asking is because if you're using mine, then you do NOT see the
> bug. If you're using Benji's then you do see the bug. It's an unfortunate
> coincidence that 'o' signifies a success in one case but a failure in the
> other.
I was using Benji's. To be precise, I started vim at the shell
prompt in Unix and at the Command Prompt in Windows as
vim -u NONE
Then I executed
:set nocp
Then I either typed or pasted
long line
()
another
and deleted the empty line 4, if present, so that the buffer
contained only those three lines. Then I executed
:runtime plugin/matchparen.vim
And finally, I moved the cursor to the first line, typed
$i<down><down>
and the cursor went to the 'o' in 'another' in all three cases.
Regards,
Gary
--
Gary Johnson | Agilent Technologies
[EMAIL PROTECTED] | Wireless Division
| Spokane, Washington, USA
