Well there's some dispute over whether it's actually a bug. But for someone unfamiliar with vi/vim & how one or the other's 'supposed' to work - perhaps using it to edit some config files because they can't boot into the GUI - the current situation could render this tool unusable. For them, it looks like a bug & quacks like a bug...
For people who do know how vi/vim are supposed to work will, it looks & quacks like compatibility mode.
Well there's some dispute over whether it's actually a bug. But for someone unfamiliar with vi/vim & how one or the other's 'supposed' to work - perhaps using it to edit some config files because they can't boot into the GUI - the current situation could render this tool unusable. For them, it looks like a bug & quacks like a bug...
For people who do know how vi/vim are supposed to work will, it looks & quacks like compatibility mode.
So why not just "fix" it for the people who'll perceive it as a bug & ship a la fix here: ubuntuforums. org/showthread. php?t=449784
http://
The only downside is *not* confusing the experts...