What is open mode?

I have come 11 days after your comment and I was looking for this exact thread within algolia until I suddenly remembered that it had sourceforge link and then remembered vim as well and I searched on algolia "vim" "sourceforge" to find it.

So its so elegant and modern that I came back to the website by searching for it so deeply xD

I do wish as voidUpdate has said that I wish for it to be a bit more centered but its overall great!

I wish it took up more than 640 pixels on the left of my 1920 pixel screen. I changed the CSS of the body to be 900pt instead of 480, and it renders at 1200px wide, which looks a lot nicer to my eyes. Didn't bother trying to center it though, which would have improved it even more

Lacks centering, other than that I also found it enjoyable to look at.

To me, the justified text makes it an effortful read.

Breaks Firefox's reader mode.

Looks like dog shit on mobile.

I agree that this general style is good, just without some of this page's fuckups.

It's been years since I heard the term "Throwback Thursday", funny that reading it here felt like a throwback in its own right ^_^

See infobox.

* https://jdebp.uk/FGA/vi-family.html#elvis (https://news.ycombinator.com/item?id=48132452)

Is still around, at least for some values of "around".

Elvis, at its latest release (2.2.0) is a required part of Slackware, part of the A (essential system) package series. I have it installed on my system, alongside Plasma 6.7 and kernel 7.1.

> Of course, if you're implementing POSIX vi, there are quite a few features that have aged poorly, like roff/troff macros and line-editing

What do you mean by "roff/troff macros"?

EDIT: Ah, you're probably talking about the "section-wise" movements, defined in POSIX with language like "A line whose first character is a <period> and whose second and third characters match a two-character pair in the 'sections' edit option (see ex)" - that's the first time I've stumbled upon the 'sections' and 'paragraphs' options in the Vim manual ... Very quaint!

`set compatible`?

Incorrect.

:x is a vi feature, that was introduced by Mary Ann Horton to actual Joy+Horton vi in February 1980.

* https://code.illumos.org/plugins/gitiles/illumos-gate/+/refs...

Ritter's vi is derived from Joy+Horton vi. Illumos has the original.

or ZZ to save and exit

I can't think of any, but I can share some examples.

When shredding things like log files, or raw data file, being able to do things like:

  :g/bad line/d

To delete all of the "bad lines". When manually paring down some files, you can use `ma` to do "Mark A" (vs `mb`, which is Mark B). So, I can be scrolling through the file, do the mark when I get to the top of a garbage section, and page or scroll or search to the next "keep" section, and then do `d'a` which means "delete to A", and so it removes all of the stuff I've skipped through.

Doing simple things like:

   !Gformat (! to shell out, G for "the entire buffer", format is the program)

Which runs the entire buffer through the `format` command to wrap paragraphs. I don't necessarily need that feature in my editor, I have a utility that I can use instead.

Of course, you can use `!'a` to a mark. or `!/thing` to run current line to the next "thing" (use `?` for previous).

Banging to utilities is a nice way to develop a pipeline, you basically get to see stuff step by step. So instead of:

    grep thing file | cut -f 1 | sort 

You can vi the file, `!Ggrep thing`, "Yup!", `!G cut -f 1`, "Ok!", `!G sort` and easily see the intermediate steps. (Not recommended on enormous files, since the entire region is replaced.)

The `.` is great for `/word` to find a "word", `cwnew-word`, and apply it selectively. `n` to "search next", and it you like it, `.` to do the `cw` again. Otherwise, keep using `n` until you find the one you like.

And I have no problem running a chunk through a bang command to see what's what, only to just `u`ndo it. (With modern `vim`, you can undo that all the way back to the start if you're doing that pipeline thing.)

And, I would routinely do something like:

  ma$%:'aw/tmp/x.x!vi other.txt then /wherever, :r /tmp/x.x

Mark A, `$` to EOL, `%` to closing brace (imagine a C function header), write from mark A to current line to /tmp/x.x, `!` to shell out to a new `vi` session, then read in the snippet.

Old school, single session, copy and paste. My /tmp is scattered with x.x, x.y, x.1, etc. files.

Along with regex replaces, this is 95% of how I use `vi`. I'm sure there's a bunch of other features, especially in `vim`, but these few bits are flexible and powerful enough to cover my needs. Since I haven't really been found "wanting", I'm not really "looking".

And it started because `vi` was a singular common denominator across all of the disparate UNIX minis I used to work on, so I just managed to work with what was available wherever I went.