News for hackers. Stuff that matters.
Re:A vi-centric family tree of editors (2000) by linksnapzz on Sunday November 27, 2016 @08:46PM (#13052861)
IIRC, it was the case that for commercial Unixen, the Single Unix Specification v.2 stated that amongst other things, the vi editor always had to be available.

So, vi gets dragged in as part of your vendor's commitment to "standards compliance". Also, for SUS purposes, vi means SysV vi, not vim. A far less domesticated creature.

In a base install of Solaris, Irix, HP-UX or Tru64, it'd be the only editor you get. Vim, emacs, nano, joe etc. would all be in a seperate "freeware tools" or somesuch sideloaded optional install set.

Re:A vi-centric family tree of editors (2000) by Spooky23 on Sunday November 27, 2016 @10:19PM (#13053184)
Not only that, but vendors would freeze those tools in time.

I worked for an employer who banned "freeware" tools so you were stuck with ancient, broken software on Solaris and other systems.

Post 9-11, we had to secure all of the things, including moving away from rsh and telnet. SSH was problematic due to the freeware thing -- no worry... we were able to buy "IBM SSH" for $900 per processor value unit. (IBM SSH was an out of date OpenSSH where someone did a find and replace substituting Open with IBM)

Re:A vi-centric family tree of editors (2000) by erelde on Monday November 28, 2016 @05:29AM (#13054566)
"Nobody ever got fired for buying IBM."

This entire thread makes me giggle, usually posts about editors are filled with bad temper, but not this one.

Re:A vi-centric family tree of editors (2000) by craigsmansion on Monday November 28, 2016 @07:59AM (#13055096)
> it'd be the only editor you get.

Slanderous and outrageous lies!

Ed, man! !man ed

Computer Scientists love ed, not just because it comes first alphabetically, but because it's the standard. Everyone else loves ed because it's ED!

“Ed is the standard text editor.”

But more historical and factual: Ed is actually "mandatory on systems conforming to the Single Unix Specification)" as well.

Re:A vi-centric family tree of editors (2000) by YeGoblynQueenne on Monday November 28, 2016 @09:49AM (#13055699)
Ah, ed. I have fond memories of being stuck in an ed command line inside the Unix mode of Z/OS on a mainframe.

  exit
  ?
  quit
  ?
  q
  ?
  bye
  ?
  help
  ?
  ohmygodgetmeouttaheeeeere
  ?
P.S. I'm not a native English speaker. "Fond" means "a vision of hell" right?
Re:A vi-centric family tree of editors (2000) by AimHere on Monday November 28, 2016 @11:23AM (#13056382)
Yes. Yes, that's exactly what it means.
Re:A vi-centric family tree of editors (2000) by macintux on Monday November 28, 2016 @08:23AM (#13055215)
I learned to program C in a crippled version of ed. Ed rocks!
Re:A vi-centric family tree of editors (2000) by codezero on Sunday November 27, 2016 @09:48PM (#13053061)
This is how I learned vi. I was a pico (now called nano) user but needed to edit the hosts file when Solaris was released for x86.
Re:A vi-centric family tree of editors (2000) by digi_owl on Wednesday November 30, 2016 @10:45AM (#13071614)
More correctly nano is a reimplementation of pico.

This, iirc, done because pico was part of the pine email client. And pine was covered by a iffy license.

Re:A vi-centric family tree of editors (2000) by codezero on Sunday December 04, 2016 @02:51PM (#13101451)
Ah, neat, I didn't realize it wasn't just renamed :)