18 Jan
2020
18 Jan
'20
9:37 p.m.
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 rare event when I disagree with you, Clem (sometimes it seems like
we were separated at birth :) If it was compat by default then you
wouldn't learn any of the new stuff.
set compatible
isn't that hard but we'd have to read docs to find that.
Anyhoo, cross reference to Ted's thought that Linux didn't have to
deal with the Gods of BSD so they could rip stuff out and try again,
his point is that worked better than the BSD way. Compat is fine
but if you want progress, sometimes you break compat.
For me, I've got a .exrc that I've been carrying around for decades
(has maps in it for some compat bindings to an editor I used on CP/M,
it's _that_ old) and vim is perfectly happy with it.
I mostly use vim as a vi compat but I regularly use 2 panes, that's
super useful. It's progress and you can have compat mode easily,
seems like a win.
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).