Path: utzoo!attcan!uunet!lll-winken!lll-tis!ames!ncar!oddjob!gargoyle!att!ihnp4!ihlpf!nevin1 From: nevin1@ihlpf.ATT.COM (00704a-Liber) Newsgroups: comp.unix.questions Subject: Re: vi vs emacs in a student environment Message-ID: <5270@ihlpf.ATT.COM> Date: 13 Jul 88 00:43:38 GMT References: <399@cantuar.UUCP> <11418@steinmetz.ge.com> <6056@megaron.arizona.edu> <1832@stpstn.UUCP> <449@jonlab.UUCP> Reply-To: nevin1@ihlpf.UUCP (00704a-Liber,N.J.) Organization: AT&T Bell Laboratories - Naperville, Illinois Lines: 25 In article <449@jonlab.UUCP> jon@jonlab.UUCP (Jon H. LaBadie) writes: >You may >prefer emacs and csh, but you better know vi and sh. The latter >properly prepares students for their post-collegiate days. Maybe. The problem is: there is so much to vi and so little that can be found out (did you ever try to find a manual around a college campus?). For instance: how many college students, after using Unix and vi for 4 years, could tell you how to substitute ALL occurrences of the word 'foo' with the word 'bar' in a given document? Or what a lowercase 'f' does? Or how to pipe output to a command? Not very many people. If they prefer emacs, let them use it! >The same argument is valid for edlin in the MS_DOS world (did I >really say that word ;-)?). You may not prefer edlin, but you >should know how to use it. Since both vi and emacs are available for MS-DOS, there really is no point in learning how to use edlin. Always try to get the best tools for the job! -- _ __ NEVIN J. LIBER ..!att!ihlpf!nevin1 (312) 510-6194 ' ) ) You are in a little maze of twisting / / _ , __o ____ email paths, all different. / (_