Yakov Lerner wrote:
> On 8/28/07, *Yakov Lerner* <[EMAIL PROTECTED] 
> <mailto:[EMAIL PROTECTED]>> wrote:
> 
>     On 8/27/07, *Bram Moolenaar* <[EMAIL PROTECTED]
>     <mailto:[EMAIL PROTECTED]>> wrote:
> 
> 
>         Yakov Lerner wrote:
> 
>         >  I get weird up/down behaviour when cursor traverses the
>         braces. vim 7.1.87,
>         >  no custom plugins. This is apparently somehow related to
>         matchparen.
>         >
>         >  The testfile is x.c below.
>         >  Here is what happens if I press down starting from the
>         beginning of file,
>         >  position 1:
>         >
>         >  1. Down. instead of going to line 2, cursor shows at line 4 !!!
>         >  2. Down. cursor is at line 3
>         >  3. Down. cursor is at line 2 !!!
>         >  4. Down. cursor is at line 5
>         >  6. Up. Cursor is at line 2!!!
>         >  7. Up. Cursor is at line 3.
>         >  8. Up. Cursor is '}' line 4!!!
>         >  9. Up. Cursor is at line 1.
>         >
>         >  ----------- x.c ----------------
>         >  int foo()
>         >  {
>         >     return 0;
>         >  }
>         >  /* */
> 
>         I don't have a vt220 so I can't try it out.  I wonder if you are
>         actually using a vt220 anyway, these are quite rare these days... 
> 
> 
>     I observe same results when setting XTERM to xterm-mono.
>     The terminal was actually xterm.
>     You can change vt220 to xterm-mono and see the same results.
> 
>     >  How can you tell where the cursor is and it's not the highlighting
>     that
>     >  makes you think the cursor is somewhere else? 
> 
>     I can do :echo line('.') col('.'). This shows me that cursor is not
>     where vim shows the white block on the screen.
> 
>     >  Try using a different color scheme.
> 
>     I normally work in color xterm. There is no problem there.
>     I do not normally work in B/W term. What we were doing, we were
>     checking how some console software  (not vim) behaves under the
>     black-and-white TERM.
> 
>     As a side effect, I noticed that matchparen behaves weirdly on B/W 
>     term. In the mentioned B/W setup, the colorscheme was default
>     because .vimrc is empty.
> 
>     Anyway, if you want to see the matchparen problem on BW term (with
>     default colorscheme), you can set TERM to xterm-mono and see for
>     yousrself.
> 
> 
> Maybe the solution is that patchparen would turn itself off when the 
> terminal is black and white.
> Even if matchparen gets fixed and shows exactly same blocks at two 
> places -- at the cursor point and and at the matching parent point -- 
> this looks confusing.
> 
> Yakov

Assuming that your cursor is normally a block, one of

        :hi MatchParen term=underline
or
        :hi MatchParen term=bold

should show its mate differently. (I thought of "term=blink" but apparently 
Vim doesn't know about that.)


Best regards,
Tony.
-- 
Collaboration, n.:
        A literary partnership based on the false assumption that the
other fellow can spell.

--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---

Raspunde prin e-mail lui