Path: utzoo!attcan!uunet!lll-winken!lll-tis!helios.ee.lbl.gov!nosc!ucsd!rutgers!umn-d-ub!umn-cs!randy From: randy@umn-cs.cs.umn.edu (Randy Orrison) Newsgroups: comp.unix.questions Subject: Re: Re: DWB ownership (was: vi vs emacs in a student environment) Message-ID: <6101@umn-cs.cs.umn.edu> Date: 7 Jul 88 16:06:56 GMT References: <8206@brl-smoke.ARPA> <810009@hpsemc.HP.COM> Reply-To: randy@umn-cs.UUCP (Randy Orrison) Organization: Control Data, Arden Hills, Minnesota Lines: 30 In article <810009@hpsemc.HP.COM> gph@hpsemc.HP.COM (Migration Engineer) writes: | I have found that not knowing VI in the UNIX world can | make life harder. | | Obviously, the two KEY editors in UNIXland are VI and EMACS. | Therefore, either of these editors is probably sufficient to | get around a little. Perhaps students should be taught an | introduction to both and let them make their own decision? What? When I bought my Unix-pc, it came with (of course...) UNIX*. This computer had only ONE editor on it. Which one? Not vi, not emacs, no... it was ed. That's right, ed. Fortunately, I know how to use ed (at least a little) and so was in a much better position than my friend who only knew vi (useless). I believe that students should be tought the editor that is most likely to be available on all Unix systems: ed. :-) :-) On the other hand, (almost) the first thing I did when I got my development kit was to compile MicroEmacs. I have ported MicroEmacs to every machine I've done serious work on. Here's what I really believe: teach them emacs, and give them a copy of the source for MicroEmacs. -randy *UNIX is a trademark of AT&T Bell Labs (or somebody with a similar name) and so should be taken as the definitive definition of what's exists. -- Randy Orrison, Control Data, Arden Hills, MN randy@ux.acss.umn.edu {bungia, uunet!hi-csc, rutgers, sun}!umn-cs!randy "I consulted all the sages I could find in Yellow Pages, but there aren't many of them." -APP