Bram Moolenaar 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.
>
> After I do ":set term=xterm-mono" I get no syntax HL and no matchparen
> highlighting. The cursor shows up in the expected position.
>
> I suspect there is something wrong with your termcap/terminfo entry for
> xterm-mono. Check the output of ":set termcap".
>
If I use
TERM=xterm-mono vim
in a konsole which is normally xterm-color, I do see matchparen highlighting.
The cursor is a blinking block (albeit slow blinking, not as usual), and the
matched paren is unblinking reverse video.
I don't see much highlighting -- after all, the possibilities of a mono
console are limited -- but I see cursorline/cursorcolumn highlighting, and
with 'list' on, end-of-line markers are in bold. I also see the more-prompt in
bold but not the htmlBold highlight group. I see default groups and those for
help, but it seems that filetype detection doesn't set the 'syntax' option.
Aha! The vimrc_example.vim doesn't set ":syntax on" on mono terminals. IMO it
should ('t_Co' is empty but the terminal can do bold, underline and reverse,
as well as any combination of them). Well, I can add it in my vimrc.
Best regards,
Tony.
--
Mynd you, m00se bites Kan be pretty nasti ...
"Monty Python and the Holy Grail" PYTHON (MONTY) PICTURES LTD
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
