9fans - fans of the OS Plan 9 from Bell Labs
 help / color / mirror / Atom feed
From: David Hogan dhog@lore.plan9.cs.su.oz.au
Subject: porting linux programs and drivers to plan9
Date: Sat, 19 Apr 1997 11:51:40 +1000	[thread overview]
Message-ID: <19970419015140.s3erp8dPAsR9jDNc3ItZdzrXrHZe2dgCf7WU6umg5DA@z> (raw)

> >Actually, an X version of sam is available for Unix systems.
> >Look at http://plan9.bell-labs.com/plan9/unixsrc/sam.
> >
> You are quite correct, I did come across that. The problem is
> I can only really count on having an X terminal when I am at home.
> When I am working on a contract, I often have to make do with
> a serial terminal. I even use Microemacs in preference to Emacs,
> because that is all that is supported on OS-9 and a few other
> esoteric systems that I use. I just find it much more efficient
> to know one reasonable editor well, than a load of different
> (possibly very powerful), editors poorly.

> It is much the same argument as my wanting a C compiler on any
> system I am going to use, regardless of what new and better
> languages may be provided.. 

I guess it's about time someone posted this:


When I log into my Xenix system with my 110 baud teletype, both vi *and*
Emacs are just too damn slow.  They print useless messages like, 'C-h for
help' and '"foo" File is read only'.  So I use the editor that doesn't
waste my VALUABLE time.

Ed, man!  !man ed

ED(1)               UNIX Programmer's Manual                ED(1)

NAME
     ed - text editor

SYNOPSIS
     ed [ - ] [ -x ] [ name ]
DESCRIPTION
     Ed is the standard text editor.
=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=

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."

And ed doesn't waste space on my Timex Sinclair.  Just look:

- - -rwxr-xr-x  1 root          24 Oct 29  1929 /bin/ed
- - -rwxr-xr-t  4 root     1310720 Jan  1  1970 /usr/ucb/vi
- - -rwxr-xr-x  1 root  5.89824e37 Oct 22  1990 /usr/bin/emacs

Of course, on the system *I* administrate, vi is symlinked to ed.
Emacs has been replaced by a shell script which 1) Generates a syslog
message at level LOG_EMERG; 2) reduces the user's disk quota by 100K;
and 3) RUNS ED!!!!!!

"Ed is the standard text editor."

Let's look at a typical novice's session with the mighty ed:

golem> ed

?
help
?
?
?
quit
?
exit
?
bye
?
hello? 
?
eat flaming death
?
^C
?
^C
?
^D
?

=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=
Note the consistent user interface and error reportage.  Ed is
generous enough to flag errors, yet prudent enough not to overwhelm
the novice with verbosity.

"Ed is the standard text editor."

Ed, the greatest WYGIWYG editor of all.

ED IS THE TRUE PATH TO NIRVANA!  ED HAS BEEN THE CHOICE OF EDUCATED
AND IGNORANT ALIKE FOR CENTURIES!  ED WILL NOT CORRUPT YOUR PRECIOUS
BODILY FLUIDS!!  ED IS THE STANDARD TEXT EDITOR!  ED MAKES THE SUN
SHINE AND THE BIRDS SING AND THE GRASS GREEN!!

When I use an editor, I don't want eight extra KILOBYTES of worthless
help screens and cursor positioning code!  I just want an EDitor!!
Not a "viitor".  Not a "emacsitor".  Those aren't even WORDS!!!! ED!
ED! ED IS THE STANDARD!!!

TEXT EDITOR.

When IBM, in its ever-present omnipotence, needed to base their
"edlin" on a UNIX standard, did they mimic vi?  No.  Emacs?  Surely
you jest.  They chose the most karmic editor of all.  The standard.

Ed is for those who can *remember* what they are working on.  If you
are an idiot, you should use Emacs.  If you are an Emacs, you should
not be vi.  If you use ED, you are on THE PATH TO REDEMPTION.  THE
SO-CALLED "VISUAL" EDITORS HAVE BEEN PLACED HERE BY ED TO TEMPT THE
FAITHLESS.  DO NOT GIVE IN!!!  THE MIGHTY ED HAS SPOKEN!!!

?

------------------------------





             reply	other threads:[~1997-04-19  1:51 UTC|newest]

Thread overview: 51+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1997-04-19  1:51 David [this message]
  -- strict thread matches above, loose matches on Subject: below --
1997-04-21 20:59 miller
1997-04-21 16:27 Eric
1997-04-21 14:53 Milon
1997-04-21 12:50 miller
1997-04-21 11:29 Nigel
1997-04-21  8:05 Boyd
1997-04-21  7:16 chad
1997-04-21  3:36 presotto
1997-04-21  1:03 David
1997-04-20 16:12 miller
1997-04-19 16:49 Magnus
1997-04-19 10:22 Digby
1997-04-19  4:59 chad
1997-04-19  4:09 ozan
1997-04-19  3:52 Berry
1997-04-19  0:56 Rich
1997-04-19  0:41 Rich
1997-04-18 21:19 Paul
1997-04-18 21:01 Digby
1997-04-18 20:47 Digby
1997-04-18 16:39 presotto
1997-04-18 16:10 Eric
1997-04-18 16:07 Eric
1997-04-18 15:57 Eric
1997-04-18 15:51 Eric
1997-04-18 15:37 Dean
1997-04-18 15:14 forsyth
1997-04-18 13:54 Brandon
1997-04-18  9:50 Andrew
1997-04-18  8:10 Digby
1997-04-18  8:04 Digby
1997-04-18  7:58 Steve_Kilbane
1997-04-18  7:52 Steve_Kilbane
1997-04-18  7:15 Nigel
1997-04-18  5:57 Nickolay
1997-04-18  5:49 Brandon
1997-04-18  4:59 jmk
1997-04-18  3:15 Steve
1997-04-18  0:33 Pete
1997-04-17 23:43 Eric
1997-04-17 23:19 Eric
1997-04-17 21:55 Eric
1997-04-17 21:46 Rich
1997-04-17 21:45 Rich
1997-04-17 18:43 Eric
1997-04-17 18:17 forsyth
1997-04-17 18:13 forsyth
1997-04-17 17:59 Bodet
1997-04-17 17:07 Pete
1997-04-17 16:33 Rich

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=19970419015140.s3erp8dPAsR9jDNc3ItZdzrXrHZe2dgCf7WU6umg5DA@z \
    --to=9fans@9fans.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).