On Fri, Jul 3, 2009 at 6:49 PM, Joseph L. Casale wrote:
>>With the lack of details, it's really hard to say, but - that sounds
>>like what would happen if $LINES or $COLUMNS were set incorrectly and
>>vim wasn't able to ask the terminal what the correct number of lines
>>and columns are.
>
> Matt,
> Thanks for taking the time to help and I apologize for the lack of details
> as I literally just don't know enough about vim to even know what to ask
> yet:)
>
> I tried playing with those, but now my problem is that I open a file, I
> see it all, but as I move the cursor down, once I hit the bottom, only the
> bottom line updates, so the initial page worth of lines remains unchanged
> and all the new lines only appear one at a time at the bottom?
>
> My .vimrc currently is very bare as I get it the way I like it, but it looks
> like this so far:
>
> if &term != 'xterm'
> set term=linux
> endif
Well, that is flat out wrong on Solaris. Solaris definitely doesn't
provide any terminals that would qualify as $TERM == 'linux'
> syntax on
>
> set nocompatible
Probably not related to your problem, but 'set nocompatible' should be
the first line in your vimrc. Toggling "compatible" changes a lot of
other options as a side effect, so putting it anywhere other than the
very beginning of your user settings can override things that you set
earlier.
Nothing else in your vimrc looks particularly suspect, though. Do you
see the same problem with
vim -u NONE -N
Are $COLUMNS and $LINES set to the correct numbers? What type of
terminal *are* you running? Do other full-screen curses applications
behave in it?
~Matt
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
