This is possibly fixed in Vim 7.3.430 (which is just ahead of the vim released in precise).
http://code.google.com/p/vim/issues/detail?id=52
This is possibly fixed in Vim 7.3.430 (which is just ahead of the vim released in precise).
http:// code.google. com/p/vim/ issues/ detail? id=52