home *** CD-ROM | disk | FTP | other *** search
- Xref: sparky comp.os.ms-windows.misc:4754 comp.os.ms-windows.apps:5103
- Newsgroups: comp.os.ms-windows.misc,comp.os.ms-windows.apps
- Path: sparky!uunet!haven.umd.edu!purdue!mentor.cc.purdue.edu!noose.ecn.purdue.edu!gn.ecn.purdue.edu!mechalas
- From: mechalas@gn.ecn.purdue.edu (John P. Mechalas)
- Subject: Re: Vi for MS-Windows
- Message-ID: <1992Nov19.232533.2725@gn.ecn.purdue.edu>
- Organization: Purdue University Engineering Computer Network
- References: <BxvMCB.LMM@ansoft.com> <1992Nov19.224822.11623@wam.umd.edu>
- Date: Thu, 19 Nov 92 23:25:33 GMT
- Lines: 32
-
- In article <1992Nov19.224822.11623@wam.umd.edu> mmeltzer@wam.umd.edu writes:
- >In article <BxvMCB.LMM@ansoft.com> gupta@ansoft.com (Suvajit Gupta)
- >writes:
- >:-> Is there a good public domain UNIX-style vi editor that runs under
- >:-> Microsoft Windows? Ideally, it should allow resizing of the window
- >:-> it runs in. I currently have a PC vi that runs under DOS, but it
- >:-> is limited to run in DOS windows (24 lines only!).
- >
- >Pardon me if this sounds rude, but why would you want to use VI in
- >Windows? It makes no sense to me to use only the keyboard in a graphical
- >user interface. NotePad is a good editor, and if you don't think so, I'm
- >sure Write, or your other word processors can do a good job.
-
- Several reasons come to my mind:
-
- 1) Once you learn vi, it's hard to break the habit. And if you can
- have it on both Unix and DOS machines, why bother using a different
- editor each time?
-
- 2) Notepad and most other text editors store the entire file in RAM.
- This limits the maximum file size that they can handle. Proper
- VI clones use swap/temporary files for storage, so there is no
- limit on the size of the file that can be edited.
-
- 3) Word processors are larger programs and take longer to load. Of
- course, if speed isn't an issue, I guess it doesn't matter.
-
-
- --
- John Mechalas "I'm not an actor, but
- mechalas@gn.ecn.purdue.edu I play one on TV."
- Aero Engineering, Purdue University #include disclaimer.h
-