[SLL] screen caviot WAS: vim is slow to launch

[Ryan Allen]

* Brian Hatch <bri at ifokr.org> wrote on [01-21-08y 18:10]:
> Sometime near 2008-01-21 16:04 -0800, Ryan Allen pontificated:
> 
> > Hi SSL,
> > 
> >    I'm experiencing a strange vim problem.  Anytime I launch vim, there
> >    is a 4 second delay.  Very annoying.  This is with a mostly stock
> >    ubuntu 7.10 install.  Running with -V1 reveals:
> > 
> > ryan at dorje:~$ /usr/bin/vim.full -V1
> > XSMP opening connection   -- a few second pause --
> > 
> > XSMP SmcOpenConnection failed: Could not open network socket
> > not found in 'runtimepath': "ftdetect/*.vim"
> > Opening the X display took 0 msec
> > Testing the X display failed
> > Opening the X display took 0 msec
> > Testing the X display failed
> > Reading viminfo file "/home/ryan/.viminfo" infoOpening the X display
> > took 3 msecTesting the X display failed
> > Press ENTER or type command to continue
> > 
> > I'm sshed into the box remotely, so why is it even trying to test the X
> > display?  What tells vim to do anything X?  I cannot find any config
> > files, aliases or google searches about this.
> 
> Are you using X11 forwarding in ssh?  IE using 'ssh -X' or have
> 'ForwardX11 yes' in either /etc/ssh/ssh_config or ~/.ssh/config?
> 
> Do the following:
> 
>   * echo $DISPLAY
>   * xwininfo -root
>   * xeyes
> 
> If the first one is blank, the rest should say X isn't running.


Hey, thanks.  I figured it out.  I am not sshing with the -X flag, that
is too much bandwidth through my tiny VPN.  

echo $DISPLAY reveled :0.0 and theirs xwininfo info...

Here is how I got there:

On host system start a screen session, make a few windows, detach.
Later, ssh into that system remotely, and re-attach screen.  The env
implies you are sitting at a X session, but you aren't...

Thanks for the help Brian,

       -Ryan