On Fri, Jan 17, 2020 at 10:13:45PM -0500, Clem Cole wrote:
On Fri, Jan 17, 2020 at 9:35 PM Michael Parson
<mparson(a)bl.org> wrote:
It's like 99% compatible.
Exactly... As my old (non-PC) 10th-grade calculus teacher used to say,
"I'll give you partial credit when you can bring be me a female that is
partially pregnant."
To be you are either compatible or not. I would have been ok to have had
an option that you could turn on that gave you new behavior (but make the
user turn it on thank you).
BTW: the cX command's behavior I also find annoying visually, but it does
not screw up 30-40 years of programming in my fingers.
There was a time when, by default, vim started in 'compatible' mode, in
which u didn't ignore u, so you got the toggle-style undo. Compatible
mode also keeps the ol$ style of c representation, and so forth. You
can still force this by making a ~/.vimrc file that just contains
set compatible
I don't remember when vim stopped launching in compatible mode by
default, but that was basically when I stopped using it. I only figured
out how to force it back because it's on all the linux computers I run
into at work.
As I recall, the 'set compatible' command is shorthand to set all the
vi-compatibility flags by default; it is possible to set them
individually as well. So your proposal is (was?) at least implemented,
if not in a very useful manner.
khm