Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: ted@loft.tnolan.com (Ted Nolan ) Newsgroups: comp.os.linux.misc,alt.folklore.computers Subject: Re: Recent history of vi (was: Re: Python/C/Pascal ... How To Choose ?) Date: 16 Nov 2025 05:15:42 GMT Organization: loft Lines: 26 Message-ID: References: X-Trace: individual.net dH4pkwqolqknJvXs1rOOSQbv+dXluuUtNItAfbCR+8CVRi6ksG X-Orig-Path: not-for-mail Cancel-Lock: sha1:Wfc2LFqEtAeW8Wrciwy8oJ0zHSI= sha256:J7hDKZr2NZ8P/2YADft1ry/9B0ytyavD8XYPCD7+nhQ= X-Newsreader: trn 4.0-test76 (Apr 2, 2001) Xref: csiph.com comp.os.linux.misc:77620 alt.folklore.computers:232183 In article , rbowman wrote: >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. I believe as well as "set compatible" I had do do "syntax off" and there was still some thing I never figured out where in some case it was "helpfully" automatically inserting something. Can't recall exactly what triggered that. There was also maybe something where it would watch the file I was editing and try to be helpful if it had been modified by anything else. Don't care, shut up. -- columbiaclosings.com What's not in Columbia anymore..