Tony Mechelynck wrote:
> On 20/06/09 02:07, Tony Mechelynck wrote:
>
>> On 20/06/09 01:56, Tony Mechelynck wrote:
>>
>>> On 19/06/09 18:06, Dale Huffman wrote:
>>>
>>>> My console version of vim is acting funny.
>>>> It starts up with the status line displaying
>>>> ,0-1 All<snip> and then a zero at the end of
>>>> the line.
>>>>
>>>> I can go into insert mode but then every keypress generates a newline
>>>> and the screen shifts up.
>>>> the status line gets moved up the screen
>>>>
>>>> For example here I entered insert mode and typed "help me" and this is
>>>> what the bottom of my screen looks like.
>>>> And I see none of my typing. I'm sure how to start debugging this.
>>>>
>>> [...]
>>>
>>>> gvim works fine
>>>> I'm using
>>>> VIM - Vi IMproved 7.1 (2007 May 12, compiled Jan 8 2009 02:55:10)
>>>> on Ubuntu 8.04 installed from Ubuntu repositories.
>>>>
>>> :echo '"' . $TERM . '"'
>>> :verbose set term? ttybuiltin?
>>> :version
>>>
"xterm"
term=xterm
ttybuiltin
>>> See also |:redir| about how to capture the output of one or more of
>>> these commands.
>>>
>>> Near the middle of the output of ":version", it says "system vimrc
>>> file:" with a pathfilename. Does that file exist? If it does, does its
>>> contents look "sensible"?
>>>
The file exists and I guess it's reasonable, though I'm not sure.
The only uncommented lines are:
runtime! debian.vim
if filereadable("/etc/vim/vimrc.local")
source /etc/vim/vimrc.local
endif
and /etc/vim/vimrc.local does not exist
Most of the options in this file I have set in my .vimrc file
>>> BTW, 7.1 is, let's say, not this semester's fashion. You may want to
>>> compile your own Vim, see my HowTo for Unix/Linux at
>>> http://users.skynet.be/antoine.mechelynck/vim/compunix.htm -- it isn't
>>> really hard, I started when I was still hardly more than a Vim newbie.
>>>
OK - I'll try that.
>>> The latest patchlevel is currently (as of this writing) 7.2.209. You can
>>> see a one-line summary of every bug already fixed for Vim 7.2 at
>>> http://ftp.vim.org/pub/vim/patches/7.2/README
>>>
>>>
>>> Best regards,
>>> Tony.
>>>
>> Oops! It won't work, because there's something wrong with how Vim reads
>> your keyboard.
>>
>> So let's see if it can interpret these commands from the shell command-line:
>>
>> vim --cmd 'redir ~/vim.log' --cmd 'version' -c scriptnames -c 'echo "<"
>> . $TERM . "<"' -c 'verbose set term? ttybuiltin?' -c 'redir END' -cqa
>>
>> (all on one line). You might also try the same with -u NONE in addition,
>>
That's great I had no idea you could use vim that way. But I am able to
see the output of : commands. Some are garbled but most are legible.
>> immediately after vim.
>>
>>
>> Best regards,
>> Tony.
>>
>
> P.S. Then see (in each case) what was printed on ~/vim.log
>
> Best regards,
> Tony.
>
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_use" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
