On 2018/03/13 21:59, Nan Xiao wrote: > Hi Stuart, > > No! It doesn't happen when run "env -i vim $filename". > > But check my environment: > > # env > _=/usr/bin/env > LOGNAME=root > HOME=/root > SSH_TTY=/dev/ttyp0 > LSCOLORS=fxexcxdxbxegedabagacad > SHELL=/bin/ksh > PS1=$USER:$PWD# > TERM=xterm > SSH_CONNECTION=10.217.243.14 63260 10.217.242.61 22 > LD_LIBRARY_PATH=/usr/local/lib > MAIL=/var/mail/root > SSH_CLIENT=10.217.243.14 63260 22 > PATH=/sbin:/usr/sbin:/bin:/usr/bin:/usr/X11R6/bin:/usr/local/sbin:/usr/local/bin:/usr/local/jre-1.8.0/bin > USER=root > > Don't know what causes the problem. > Best Regards > Nan Xiao > > > On Tue, Mar 13, 2018 at 6:39 PM, Stuart Henderson <s...@spacehopper.org> > wrote: > > On 2018-03-13, Nan Xiao <xiaonan830...@gmail.com> wrote: > >> Hi Ville, > >> > >> I don't have ~/.vimrc, only a ~/.viminfo, thanks! > > > > Perhaps something in your environment is causing a problem. > > > > Does it also happen if you run "env -i vim $filename"? > > > >
The only thing that looks odd in there is the LD_LIBRARY_PATH setting though I don't see how that would be triggering this.. Other thing I'm wondering is what terminal it is. Perhaps running it under script(1) and examining ./typescript would give another clue.
