For the record, this is with using vim-lite on FreeBSD. I never
install full vim.
I cannot speak for those who did not encounter this issue. Those who
did, however, may take notice of the following: in my case, I have
found that the issue can be avoided by including the following line in
the system-wide vimrc or your user .vimrc:
nocp
This prevents vim from using vi compatibility.
niek
On Thu, Apr 7, 2011 at 9:27 AM, Matthew D. Fuller
<fullermd@over-yonder.net> wrote:
> On Thu, Apr 07, 2011 at 08:57:12AM -0400 I heard the voice of
> Wesley Shields, and lo! it spake thus:
>>
>> I get a similar problem when editing python files.
>
> For a data point, I edit .php files all day long, and .py files
> occasionally (with both full vim and vim-lite), and have never seen
> this with either...
>
>
> --
> Matthew Fuller =C2=A0 =C2=A0 (MF4839) =C2=A0 | =C2=A0fullermd@over-yonder=
..net
> Systems/Network Administrator | =C2=A0http://www.over-yonder.net/~fullerm=
d/
> =C2=A0 =C2=A0 =C2=A0 =C2=A0 =C2=A0 On the Internet, nobody can hear you s=
cream.
>
_______________________________________________
freebsd-ports@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-ports
To unsubscribe, send any mail to "freebsd-ports-unsubscribe@freebsd.org"