> place -but they are there (/util6/SUNWspro/contrib/vim/share/vim/vim63/).
> I did install those for 7.3 in my friend's home directory under ~/vimfiles.
On Unix, it should not be ~/vimfiles, but ~/.vim so unless you have
manually and correctly set your runtimepath, this would not have worked.
> I do not see what `problems' I would encounter by not scripts and files. They
> are extra, and not necessary for the executable to function.
True, but many, many Vim features need them.
> Again - no vim related envirenment variables, one .exrc file in the home
> directory which all versions of vim read.
Do both versions show ++builtin_terms in their :version output? Or
perhaps only with one +? Or is it missing altogether?
What about +terminfo?
I wonder if both are looking in the same place for terminfo stuff, and
for terminfo in the same format (e.g. subdirectories with first letters
or hex codes of first letters). If they're not, that could easily cause
the problem. Particularly when using a binary someone else compiled, you
don't know if it was compiled using a terminfo library configured the
same as is currently on the system, too. Unless you check, you don't
know if terminfo is compiled in dynamically or statically either, I
don't think. These kinds of differences could easily cause these kinds
of problems.
Do both Vims show the same thing for :set term? (include the question
mark in the command to be safe!)?
In fact, it may be helpful if you send us the output to peruse. Do this
in each version:
:redir @a
:version
:set
:redir END
:new
:put a
You will then have the output of :version and :set captured in a buffer.
Write that to a file somewhere, for each version, and then send both to
the list. We might be able to spot something.
> With 6.4 keys and screen seem fairly normal with term=vt102. But with the same
> term and 7.3 -- all kinds of things go crazy. Motion keys insert text, and
> make the cursor jump to odd places, the j key writes the file to disk -- too
> many things to mention here.
This is really strange.
Do you get the same thing if you start Vim with the command
vim -u NONE -U NONE -N --noplugin
? Maybe a mapping or something is interfering.
Also, does your .exrc include :set nocompatible ? If not, maybe some of
the problems are related to running in compatible mode.
Does your .exrc include (m)any hardcoded key sequences, e.g. for
simulating arrow keys in mappings? If so, maybe that is compounding the
issue, as they may not be being recognised as terminal sequences if the
terminal isn't being correctly identified.
>> Compare the output of the :version command from each Vim version.
>
> This is the most likely source of the problem. Of course 7.3 has gobbs of
> extra features including client-server, python, ruby etc. Most particularly,
> it is compiled with GTK2 GUI, while 6.4 is compiled without the gui. Im used
> to launching gvim when I have a gui, so I do not know what it means for the
> console vim to be compiled with a gui. But it may be doing graphics related
> things that confuse a text based console interface.
The GUI stuff shouldn't be relevant. If Vim isn't started with the -g
option, or :gui given, about the only thing Vim uses that is even
vaguely GUI-related is the clipboard, I think. Clientserver stuff
doesn't even work when running in console mode, I don't think.
Also, what does echo $TERM give you prior to starting Vim after logging
into the remote machine?
Ben.
--
You received this message from the "vim_use" 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
No comments:
Post a Comment