Marc Aldorasi wrote:
> Steps to reproduce:
>
> 0. Have the matchparen plugin enabled.
>
> 1. Create a file with the following 3 lines:
>
> {
> {
> }
>
> 2. Move to the second line, and indent it with "=="
>
> 2.5 Notice that the brace on the third line is highlighted.
>
> 3. Type "=j" to indent the third line.
>
> What I expected:
>
> The highlighting on the third line should move with the brace.
>
> What actually happened:
>
> The highlighting on the third line did not move even though the brace
> did. This is especially noticeable if you indent with tabs, as the
> entire tab width is highlighted.
>
> This also happens if I use parens instead of braces, and happens even
> when I start vim with " vim -u NONE +'set nocp | runtime
> plugin/matchparen.vim' ". It also happens if there is other text
> between the braces, and if I use "==" instead of "=j". It does not
> happen if the first brace moves along with the second. The highlighting
> returns to normal if the cursor is moved within the window, or if I
> switch to another window and then switch back.
Thanks for the clear explanation, I can reproduce the problem.
--
Sometimes I think the surest sign that intelligent life exists elsewhere
in the universe is that none of it has tried to contact us. (Calvin)
/// Bram Moolenaar -- [email protected] -- http://www.Moolenaar.net \\\
/// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\
\\\ an exciting new programming language -- http://www.Zimbu.org ///
\\\ help me help AIDS victims -- http://ICCF-Holland.org ///
--
--
You received this message from the "vim_dev" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php
---
You received this message because you are subscribed to the Google Groups
"vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
For more options, visit https://groups.google.com/groups/opt_out.
