Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: rbowman Newsgroups: comp.os.linux.misc,alt.folklore.computers Subject: Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Date: 15 Nov 2025 21:38:15 GMT Lines: 14 Message-ID: References: <10f9iud$3dmon$1@dont-email.me> Mime-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit X-Trace: individual.net KJcfha001NO/I4uVpPBk5AA75TRIrq6FBjy245YISsyWCAp91l Cancel-Lock: sha1:Ng+AkZnXSu5K3tWkrPSxMsoKPmU= sha256:/0MR3RLFkJatJjZdjyqklOqNbosqUjHkTtsB7ha/05M= User-Agent: Pan/0.162 (Pokrosvk) Xref: csiph.com comp.os.linux.misc:77588 alt.folklore.computers:232168 On 15 Nov 2025 18:48:51 GMT, Ted Nolan wrote: > I find it takes a lot of munging to get vim to *really* work like vi. > The one on FreeBSD which I think is technically "nex" is much closer out > of the box. :he compatible has the disclaimer When this option is set, numerous other options are set to make Vim as Vi-compatible as possible. The Arch vi is the real thing. I've no idea what version it is because real vi doesn't do --version or much of anything useful.