Conversation
Notices
-
@p @sjw @m0xEE @tiskaan @gh0st @ins0mniak @mia @sysrq @lain @jeff @cjd @meso in many ways vim has morphed into the soup kitchen of emacs. i still use vim, but it's basic. but that brings up bigger thought. why do we need some massive configuration to write two lines of config/code?
-
@threat @cjd @gh0st @ins0mniak @jeff @lain @m0xEE @meso @mia @sjw @sysrq @tiskaan I don't think so, but that's me.
Apparently it is possible to get old, like really old, like "Written by Bill Joy", I mean old, like "Invoked as ex and if you want to use the visual mode, you have to hit `:vi` inside ex", vi working. vi (src/cmd/ex, it is old vi) from Research Unix v10 didn't build, but some dude named Gunnar Ritter has ported it and last updated it in 2005. I have attached his tarball because SourceForge is still making you sit through a 5-second timer just to download a fucking tarball. (I had flashbacks to the early 00s. They need the ad revenue, man, you can't just host a 215kB tarball for free.) Then I had to tweak the Makefile because it expects the CHARSET env var to not be set (and $current_anno_domini Unix uses it), then it built but I had to set a TERMCAP because by default it can't cope with just TERM, but you can link in ncurses by tweaking the Makefile again, but *this* time I was able to use the 80s vi in question to edit its own Makefile. `./ex Makefile` and then `:vi` to enter visual mode and keep in mind that it starts you at the bottom of the file because ex(1) is an extended ed.
At any rate, it works. Here's a screenshot of me using it to edit its Makefile. It enables cursor blinking, because everyone was using CRTs in the 80s and even when it was ported in 2005, I think CRTs were still normal. I had a CRT. If I still used vi much, maybe I'd try to use this as my main vi for a while.
YOUR DOWNLOAD WILL BEGIN SHORTLY
it_still_builds_fine.png
ex-050325.tar.bz2