Comment 22 for bug 58002

Revision history for this message
Martin Sander (forke) wrote :

Hey,
bug #93449 is a duplicate of this one, but as here it hasn't gotten a lot of attention recently.
Could somebody file a bug where it is more appropriate? Obviously it is not vim's fault, so maybe it should be a sudo-bug..

I have spent some hours banging my head against the wall today trying to find out why vim doesn't behave the way I am used to.