On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:

> vi could find the matching brace automatically. vim even highlights the matching brace
> for you.

Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.

Brian

In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
Default User <defaultuserbr@yahoo.com> wrote:
>On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>
>> vi could find the matching brace automatically. vim even highlights the
>matching brace
>> for you.
>
>Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>
>Brian
>

I still use vi...
--
My reviews can be found at http://jamesdavisnicoll.com/
My tor pieces at https://www.tor.com/author/james-davis-nicoll/
My Dreamwidth at https://james-davis-nicoll.dreamwidth.org/
My patreon is at https://www.patreon.com/jamesdnicoll

In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
Default User <defaultuserbr@yahoo.com> wrote:
>On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>
>> vi could find the matching brace automatically. vim even highlights
>the matching brace
>> for you.
>
>Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>
>Brian
>

Vim tries to be way too helpful. I always have to spend some time clubbing
it over the head to get it to shut up and act like vi whenever I get an
account on a new system.
--
columbiaclosings.com
What's not in Columbia anymore..

On 11/04/2022 19:25, Default User wrote:
> On Tuesday, April 5, 2022 at 8:59:09 PM UTC-5, grschm...@gmail.com wrote:
>
>> Fallible memory is prompting me to say he founded "Whitesmiths" to
>> produce C compilers, I recall using it to cross-compile stuff on VAXen
>> for MC68K boards. It was crap. Greenhills was a much better compiler
>> for the 68K.
>
> I used Whitesmiths indentation style for a long time until I started working on a big software project at Megacorp and had to work to the project coding style for C++ which used Allman style indentation. Then the company devised a Coding Standard based on that so every C++ and C# project I was on used that style. Which I suppose is the purpose of having such a thing.
>
> https://en.wikipedia.org/wiki/Indentation_style#Whitesmiths_style
> https://en.wikipedia.org/wiki/Indentation_style#Allman_style
>
I've been using subtle variants on Allman style for (;;). ;-)

Cheers,
Gary B-)

P.S. Mostly I set sw=3.

On 12/04/2022 06:33, Scott Lurndal wrote:
> ted@loft.tnolan.com (Ted Nolan <tednolan>) writes:
>> In article <t31u8o$9g2$1@dont-email.me>,
>> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>>> On 4/11/2022 4:25 AM, Default User wrote:
>
>>>>
>>>> I used Whitesmiths indentation style for a long time until I started
>>> working on a big software project at Megacorp and had to work to the
>>> project coding style for C++ which used Allman style indentation. Then
>>> the company devised a Coding Standard based on that so every C++ and C#
>>> project I was on used that style. Which I suppose is the purpose of
>>> having such a thing.
>>>>
>>>> https://en.wikipedia.org/wiki/Indentation_style#Whitesmiths_style
>>>> https://en.wikipedia.org/wiki/Indentation_style#Allman_style
>>>>
>>>> Brian
>>>
>>> I use Allman style with indented comments.
>>>
>>> Lynn
>>>
>>
>> I use Allman style with 30 minute extended jams..
>
> Which was followed by the excellent Trucks/Haynes style....
Butch or ... ?????

Cheers,
Gary B-)

On 12/04/2022 11:16, James Nicoll wrote:
> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
> Default User <defaultuserbr@yahoo.com> wrote:
>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>
>>> vi could find the matching brace automatically. vim even highlights the
>> matching brace
>>> for you.
>>
>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>>
>> Brian
>>
>
> I still use vi...

Some of my UNIX systems only have vi, but that's because
$(CORPORATION)/$(BANK)/$(GOVERNMENT_DEPARTMENT) spent so very, very,
very much with IBM or HP or Sun that they intend to run those machines
until there is only rust left on the Data Centre floor. (Not that they
don't do the same with Linux or Winderrs, I have to keep RHEL5 and W2K3
boxes alive (and off the network) just for them. At least I got rid of
the Solaris 2.5 (yes, 2.5, not 2.5.1) boxes in 2015.)

Although recent Solaris versions have vim as a replacement for vi:
$ ll /bin/vi
1 lrwxrwxrwx 1 root root 3 Jul 14 2019 /bin/vi -> vim*

Anything that doesn't have vi/vim on it that will be around for more
than five minutes gets vim installed quick smart! (And Cygwin if it's
Winderrs.)

Cheers,
Gary B-)

On 4/11/2022 8:16 PM, James Nicoll wrote:
> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
> Default User <defaultuserbr@yahoo.com> wrote:
>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>
>>> vi could find the matching brace automatically. vim even highlights the
>> matching brace
>>> for you.
>>
>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>>
>> Brian
>>
>
> I still use vi...

I use vi on my dedicated FreeBSD web server. Vi really works well over
the intertubes as it is in Pittsburg and I am in Texas.

Lynn

In article <t32qv2$e43$1@dont-email.me>,
Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>On 4/11/2022 8:16 PM, James Nicoll wrote:
>> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
>> Default User <defaultuserbr@yahoo.com> wrote:
>>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>>
>>>> vi could find the matching brace automatically. vim even highlights the
>>> matching brace
>>>> for you.
>>>
>>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>>>
>>> Brian
>>>
>>
>> I still use vi...
>
>I use vi on my dedicated FreeBSD web server. Vi really works well over
>the intertubes as it is in Pittsburg and I am in Texas.
>
>Lynn
>

Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim nonsense
I have to use on Linux.
--
columbiaclosings.com
What's not in Columbia anymore..

On 4/11/2022 10:17 PM, Ted Nolan <tednolan> wrote:
> In article <t32qv2$e43$1@dont-email.me>,
> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>> On 4/11/2022 8:16 PM, James Nicoll wrote:
>>> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
>>> Default User <defaultuserbr@yahoo.com> wrote:
>>>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>>>
>>>>> vi could find the matching brace automatically. vim even highlights the
>>>> matching brace
>>>>> for you.
>>>>
>>>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>>>>
>>>> Brian
>>>>
>>>
>>> I still use vi...
>>
>> I use vi on my dedicated FreeBSD web server. Vi really works well over
>> the intertubes as it is in Pittsburg and I am in Texas.
>>
>> Lynn
>>
>
> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim nonsense
> I have to use on Linux.

Huh, my web server was Ubuntu when I went 64 bit the first time. It had
vi. I am back on FreeBSD when they finally came out with 64 bit version
several years ago.

I don't recall ever using vim. Back in the 1980s we had several serial
terminals tied into a Apollo Unix workstation. Vi rocked as it was such
a small footprint. I could get away with using bg and fg to create
several vi processes without the other programmers noticing me stealing
all the ram and cycles.

Lynn

On 4/11/2022 8:03 PM, Gary R. Schmidt wrote:
> On 12/04/2022 06:33, Scott Lurndal wrote:
>> ted@loft.tnolan.com (Ted Nolan <tednolan>) writes:
>>> In article <t31u8o$9g2$1@dont-email.me>,
>>> Lynn McGuire  <lynnmcguire5@gmail.com> wrote:
>>>> On 4/11/2022 4:25 AM, Default User wrote:
>>
>>>>>
>>>>> I used Whitesmiths indentation style for a long time until I started
>>>> working on a big software project at Megacorp and had to work to the
>>>> project coding style for C++ which used Allman style indentation. Then
>>>> the company devised a Coding Standard based on that so every C++ and C#
>>>> project I was on used that style. Which I suppose is the purpose of
>>>> having such a thing.
>>>>>
>>>>> https://en.wikipedia.org/wiki/Indentation_style#Whitesmiths_style
>>>>> https://en.wikipedia.org/wiki/Indentation_style#Allman_style
>>>>>
>>>>> Brian
>>>>
>>>> I use Allman style with indented comments.
>>>>
>>>> Lynn
>>>>
>>>
>>> I use Allman style with 30 minute extended jams..
>>
>> Which was followed by the excellent Trucks/Haynes style....
> Butch or ... ?????
>
Sundance.

--
I've done good in this world. Now I'm tired and just want to be a cranky
dirty old man.

Default User <defaultuserbr@yahoo.com> schrieb:
> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>
>> vi could find the matching brace automatically. vim even highlights the matching brace
>> for you.
>
> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.

Emacs has also done so for a long time.

I actually like Emacs syntax support better. Small texts (such
as this one) I usually type on vi (or vim, these days).

On 12/04/2022 14:14, Lynn McGuire wrote:
> On 4/11/2022 10:17 PM, Ted Nolan <tednolan> wrote:
>> In article <t32qv2$e43$1@dont-email.me>,
>> Lynn McGuire  <lynnmcguire5@gmail.com> wrote:
>>> On 4/11/2022 8:16 PM, James Nicoll wrote:
>>>> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
>>>> Default User  <defaultuserbr@yahoo.com> wrote:
>>>>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>>>>
>>>>>> vi could find the matching brace automatically. vim even
>>>>>> highlights the
>>>>> matching brace
>>>>>> for you.
>>>>>
>>>>> Okay. I didn't use vim ever and vi only for small edits on UNIX
>>>>> platforms.
>>>>>
>>>>> Brian
>>>>>
>>>>
>>>> I still use vi...
>>>
>>> I use vi on my dedicated FreeBSD web server.  Vi really works well over
>>> the intertubes as it is in Pittsburg and I am in Texas.
>>>
>>> Lynn
>>>
>>
>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim
>> nonsense
>> I have to use on Linux.
>
> Huh, my web server was Ubuntu when I went 64 bit the first time.  It had
> vi.
It probably had "vim". I don't know of any recent Linux distribution
that doesn't use vim in place of vi[1], although early on there were a
few half-arsed attempts by drongoes who'd never even read the BSD man
pages for vi.

Depending on how "vim" is/was built or what is set in the .exrc/.vimrc
files invoking it with the name "vi" (i.e. strcmp(argv[0], "vi") == 0)
turns off all the extensions and it behaves solely like "vi".

Cheers,
Gary B-)

1 - No doubt there are dozens, but I try to ignore as many as possible.
Fortunately our customers mainly use RedHat/Centos and the rare SLES[2],
we are looking to switch to Rocky internally, and Mint is my choice when
I must use a Linux variant at home.

2 - I've probably jinxed us by writing that. Sigh. Who knows what
horrors the salesdroids will dump on us next.

On 12/04/2022 15:34, Thomas Koenig wrote:
> Default User <defaultuserbr@yahoo.com> schrieb:
>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>
>>> vi could find the matching brace automatically. vim even highlights the matching brace
>>> for you.
>>
>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>
> Emacs has also done so for a long time.
>
> I actually like Emacs syntax support better. Small texts (such
> as this one) I usually type on vi (or vim, these days).

It always amuses me to see the words "small" and "EMACS" in the same
sentence, getting EMACS to load on the systems I was using back then
just wasn't going to happen. :-)

At least Prolog /would/ load, eventually. ;-)

Cheers,
Gary B-)

In article <7hgfii-6ei.ln1@paranoia.mcleod-schmidt.id.au>,
Gary R. Schmidt <grschmidt@acm.org> wrote:
>
>Depending on how "vim" is/was built or what is set in the .exrc/.vimrc
>files invoking it with the name "vi" (i.e. strcmp(argv[0], "vi") == 0)
>turns off all the extensions and it behaves solely like "vi".
>

Annoyingly not entirely true. You can get it closer by adding
set compatible
syntax off
autocmd FileChangedShell * echon ""

to your .exrc, but there are still glitches.
--
columbiaclosings.com
What's not in Columbia anymore..

On 12/04/2022 22:17, Ted Nolan <tednolan> wrote:
> In article <7hgfii-6ei.ln1@paranoia.mcleod-schmidt.id.au>,
> Gary R. Schmidt <grschmidt@acm.org> wrote:
>>
>> Depending on how "vim" is/was built or what is set in the .exrc/.vimrc
>> files invoking it with the name "vi" (i.e. strcmp(argv[0], "vi") == 0)
>> turns off all the extensions and it behaves solely like "vi".
>>
>
> Annoyingly not entirely true. You can get it closer by adding
>
> set compatible
> syntax off
> autocmd FileChangedShell * echon ""
>
> to your .exrc, but there are still glitches.

I'll take your word for it, but I've always put the people who can't
handle the differences in the, "Too stupid to bother about", bucket.

How they would have handled today's changes to TECO would have been...
entertaining??? ;-)

Cheers,
Gary B-)

Lynn McGuire <lynnmcguire5@gmail.com> writes:
>On 4/11/2022 10:17 PM, Ted Nolan <tednolan> wrote:
>> In article <t32qv2$e43$1@dont-email.me>,
>> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>>> On 4/11/2022 8:16 PM, James Nicoll wrote:
>>>> In article <ad785d30-de66-4269-ac8d-72b9b8bb7932n@googlegroups.com>,
>>>> Default User <defaultuserbr@yahoo.com> wrote:
>>>>> On Monday, April 11, 2022 at 6:41:22 PM UTC-5, Scott Lurndal wrote:
>>>>>
>>>>>> vi could find the matching brace automatically. vim even highlights the
>>>>> matching brace
>>>>>> for you.
>>>>>
>>>>> Okay. I didn't use vim ever and vi only for small edits on UNIX platforms.
>>>>>
>>>>> Brian
>>>>>
>>>>
>>>> I still use vi...
>>>
>>> I use vi on my dedicated FreeBSD web server. Vi really works well over
>>> the intertubes as it is in Pittsburg and I am in Texas.
>>>
>>> Lynn
>>>
>>
>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim nonsense
>> I have to use on Linux.
>
>Huh, my web server was Ubuntu when I went 64 bit the first time. It had
>vi. I am back on FreeBSD when they finally came out with 64 bit version
>several years ago.
>
>I don't recall ever using vim.

I expect the 'vi' you used on Ubuntu was really vim. If you link
'vi' to 'vim' (ln /usr/bin/vim /usr/bin/vi) then when vim is started
using 'vi' instead of 'vim', it will be fully vi-compatable with no
extensions (modulo a couple of very obscure corner cases).

"Gary R. Schmidt" <grschmidt@acm.org> writes:
>On 12/04/2022 06:33, Scott Lurndal wrote:
>> ted@loft.tnolan.com (Ted Nolan <tednolan>) writes:
>>> In article <t31u8o$9g2$1@dont-email.me>,
>>> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>>>> On 4/11/2022 4:25 AM, Default User wrote:
>>
>>>>>
>>>>> I used Whitesmiths indentation style for a long time until I started
>>>> working on a big software project at Megacorp and had to work to the
>>>> project coding style for C++ which used Allman style indentation. Then
>>>> the company devised a Coding Standard based on that so every C++ and C#
>>>> project I was on used that style. Which I suppose is the purpose of
>>>> having such a thing.
>>>>>
>>>>> https://en.wikipedia.org/wiki/Indentation_style#Whitesmiths_style
>>>>> https://en.wikipedia.org/wiki/Indentation_style#Allman_style
>>>>>
>>>>> Brian
>>>>
>>>> I use Allman style with indented comments.
>>>>
>>>> Lynn
>>>>
>>>
>>> I use Allman style with 30 minute extended jams..
>>
>> Which was followed by the excellent Trucks/Haynes style....
>Butch or ... ?????

Derek, of course (Butch's nephew). As good (and probably better) than
Duane, if only because Derek has had more time to learn.

_The Derek Trucks_ band was also quite good as is the
Trucks/Tedeschi band that followed.

On 11/04/2022 18.33, Default User wrote:
> On Monday, April 11, 2022 at 11:58:41 AM UTC-5, Thomas Koenig wrote:
>
>> At least, with clang-format, it is now possible to properly
>> re-indent code.
>
> Tools have definitely improved over the years. One of the reasons I liked Whitesmiths and disliked K&R when I was starting was that I would print out source and use a ruler to draw lines down the code blocks to look for missing, extra, or misaligned braces.

Yeah, K&R-style indentation is horrible human-factors engineering.

--
Michael F. Stemper
Psalm 94:3-6

On 11/04/2022 22.02, Gary R. Schmidt wrote:
> On 12/04/2022 11:16, James Nicoll wrote:

>> I still use vi...
>
> Some of my UNIX systems only have vi, but that's because $(CORPORATION)/$(BANK)/$(GOVERNMENT_DEPARTMENT) spent so very, very, very much with IBM or HP or Sun that they intend to run those machines until there is only rust left on the Data Centre floor.  (Not that they don't do the same with Linux or Winderrs, I have to keep RHEL5 and W2K3 boxes alive (and off the network) just for them.  At least I got rid of the Solaris 2.5 (yes, 2.5, not 2.5.1) boxes in 2015.)
>
> Although recent Solaris versions have vim as a replacement for vi:
> $ ll /bin/vi
>    1 lrwxrwxrwx   1 root     root           3 Jul 14  2019 /bin/vi -> vim*
>
> Anything that doesn't have vi/vim on it that will be around for more than five minutes gets vim installed quick smart!  (And Cygwin if it's Winderrs.)

I even used vi on DOS.

--
Michael F. Stemper
Psalm 94:3-6

On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:
> In article <t32qv2$e43$1@dont-email.me>,
> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>> On 4/11/2022 8:16 PM, James Nicoll wrote:

>>> I still use vi...
>>
>> I use vi on my dedicated FreeBSD web server. Vi really works well over
>> the intertubes as it is in Pittsburg and I am in Texas.
>
> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim nonsense
> I have to use on Linux.

What distro doesn't have vi? Ubuntu only has vi:

mstemper@parvicursor$ which vi
/usr/bin/vi
mstemper@parvicursor$ which vim
mstemper@parvicursor$

(Arguing about editors or tab settings is on-topic anywhere on USENET.)

--
Michael F. Stemper
Psalm 94:3-6

In article <t34pok$vau$4@dont-email.me>,
Michael F. Stemper <michael.stemper@gmail.com> wrote:
>On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:
>> In article <t32qv2$e43$1@dont-email.me>,
>> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>>> On 4/11/2022 8:16 PM, James Nicoll wrote:
>
>>>> I still use vi...
>>>
>>> I use vi on my dedicated FreeBSD web server. Vi really works well over
>>> the intertubes as it is in Pittsburg and I am in Texas.
>>
>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim
>nonsense
>> I have to use on Linux.
>
>What distro doesn't have vi? Ubuntu only has vi:
>

You may think that, but do

vi --version
--
columbiaclosings.com
What's not in Columbia anymore..

On 12/04/2022 16.12, Ted Nolan <tednolan> wrote:
> In article <t34pok$vau$4@dont-email.me>,
> Michael F. Stemper <michael.stemper@gmail.com> wrote:
>> On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:

>>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim
>> nonsense
>>> I have to use on Linux.
>>
>> What distro doesn't have vi? Ubuntu only has vi:
>>
>
> You may think that, but do
>
> vi --version

That's a rather lengthy "--version" text. And, yes, you're
right, it is vim. The fact that I've been using Ubuntu since
2009 without ever noticing any difference between it and the
vi that I started using on AIX in 1992 tells me that I don't
need to lose any sleep over the purity of its essence.

--
Michael F. Stemper
What happens if you play John Cage's "4'33" at a slower tempo?

"Michael F. Stemper" <michael.stemper@gmail.com> writes:
>On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:
>> In article <t32qv2$e43$1@dont-email.me>,
>> Lynn McGuire <lynnmcguire5@gmail.com> wrote:
>>> On 4/11/2022 8:16 PM, James Nicoll wrote:
>
>>>> I still use vi...
>>>
>>> I use vi on my dedicated FreeBSD web server. Vi really works well over
>>> the intertubes as it is in Pittsburg and I am in Texas.
>>
>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim nonsense
>> I have to use on Linux.
>
>What distro doesn't have vi? Ubuntu only has vi:
>
>mstemper@parvicursor$ which vi
>/usr/bin/vi

Which is vim in compatability mode.

>mstemper@parvicursor$ which vim

$ sudo apt -y install vim
$ sudo apt -y install vim-gtk

$ ls -l /usr/bin/vi* | grep alt
lrwxrwxrwx 1 root root 20 Sep 15 2021 /usr/bin/vi -> /etc/alternatives/vi
lrwxrwxrwx 1 root root 22 Sep 15 2021 /usr/bin/view -> /etc/alternatives/view
lrwxrwxrwx 1 root root 21 Sep 15 2021 /usr/bin/vim -> /etc/alternatives/vim
lrwxrwxrwx 1 root root 25 Sep 15 2021 /usr/bin/vimdiff -> /etc/alternatives/vimdiff

$ dpkg -l | grep vim
ii vim 2:8.0.1453-1ubuntu1.8 amd64 Vi IMproved - enhanced vi editor
ii vim-common 2:8.0.1453-1ubuntu1.8 all Vi IMproved - Common files
ii vim-gtk 2:8.0.1453-1ubuntu1.8 amd64 Vi IMproved - enhanced vi editor - with GTK2 GUI
ii vim-gui-common 2:8.0.1453-1ubuntu1.8 all Vi IMproved - Common GUI files
ii vim-runtime 2:8.0.1453-1ubuntu1.8 all Vi IMproved - Runtime files
ii vim-tiny 2:8.0.1453-1ubuntu1.8 amd64 Vi IMproved - enhanced vi editor - compact version

In article <t34qmq$9nc$1@dont-email.me>,
Michael F. Stemper <michael.stemper@gmail.com> wrote:
>On 12/04/2022 16.12, Ted Nolan <tednolan> wrote:
>> In article <t34pok$vau$4@dont-email.me>,
>> Michael F. Stemper <michael.stemper@gmail.com> wrote:
>>> On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:
>
>>>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim
>>> nonsense
>>>> I have to use on Linux.
>>>
>>> What distro doesn't have vi? Ubuntu only has vi:
>>>
>>
>> You may think that, but do
>>
>> vi --version
>
>That's a rather lengthy "--version" text. And, yes, you're
>right, it is vim. The fact that I've been using Ubuntu since
>2009 without ever noticing any difference between it and the
>vi that I started using on AIX in 1992 tells me that I don't
>need to lose any sleep over the purity of its essence.
>

If you're happy, that's great. I get perturbed when something I've
trained my fingers to do for 20 years gets a different result.
--
columbiaclosings.com
What's not in Columbia anymore..

On Tuesday, April 12, 2022 at 5:57:32 PM UTC-4, Ted Nolan <tednolan> wrote:
> In article <t34qmq$9nc$1...@dont-email.me>,
> Michael F. Stemper <michael...@gmail.com> wrote:
> >On 12/04/2022 16.12, Ted Nolan <tednolan> wrote:
> >> In article <t34pok$vau$4...@dont-email.me>,
> >> Michael F. Stemper <michael...@gmail.com> wrote:
> >>> On 11/04/2022 22.17, Ted Nolan <tednolan> wrote:
> >
> >>>> Yep, on a FreeBSD laptop right now using *real* vi -- none of this vim
> >>> nonsense
> >>>> I have to use on Linux.
> >>>
> >>> What distro doesn't have vi? Ubuntu only has vi:
> >>>
> >>
> >> You may think that, but do
> >>
> >> vi --version
> >
> >That's a rather lengthy "--version" text. And, yes, you're
> >right, it is vim. The fact that I've been using Ubuntu since
> >2009 without ever noticing any difference between it and the
> >vi that I started using on AIX in 1992 tells me that I don't
> >need to lose any sleep over the purity of its essence.
> >
> If you're happy, that's great. I get perturbed when something I've
> trained my fingers to do for 20 years gets a different result.

I've been using emacs for 40+ years. I can do a minimal level of
vi, but will put emacs on any system I use more than a day.

Unfortunately, a good chunk of my job involves VMs that live
a few hours, max.

Pt