On 10:01 Tue 10 Apr , Aaron Griffin wrote: > On 4/10/07, Alessio 'mOLOk' Bolognino <[EMAIL PROTECTED]> wrote: > > On 10:33 Tue 10 Apr , Benoit Myard wrote: > > > > This can happen if your terminal is misconfigured, or not understood by > > > > vim. > > > > > > > > outside vim: echo $TERM > > > > inside vim: :echo &term > > > > > > Sometimes, this happens when you start a screen session inside say > > > urxvt and re-attach it under a tty. > > > > > > I'm unsure whether this example will lead to the behavior described or > > > not, but you got the idea. > > > > uhmm... I usually use vim in urxvt + GNU/screen, and the $TERM is > > screen-256color-bce. > > ( $TERM and &term matches ) > > Sometimes vim freezes for 4/5 seconds and then it works again, it's very > > annoying, I use vim for almost everything :) > > I noticed this problem even with nvi (it's in the AUR). > > Out of curiosity, is $DISPLAY set and you're not in X? vim tries to > talk to X if DISPLAY is set, so it can link up with the clipboard. > Try "unset DISPLAY" before running vim, see if that helps
As always, it's hard to reproduce a strange bug. Anyway, this happened even in X. I'm going to do further testing. -- Alessio 'mOLOk' Bolognino Arch Linux Trusted User http://www.archlinux.org _______________________________________________ arch mailing list [email protected] http://archlinux.org/mailman/listinfo/arch
