Path: utzoo!attcan!utgpu!jarvis.csri.toronto.edu!mailrus!csd4.csd.uwm.edu!gem.mps.ohio-state.edu!ginosko!cg-atla!fredex
From: fredex@cg-atla.UUCP (Fred Smith)
Newsgroups: comp.lang.c
Subject: Re: BEST MSDOS C EDITOR?
Message-ID: <7618@cg-atla.UUCP>
Date: 5 Sep 89 13:16:09 GMT
References: <21743@cup.portal.com> <1191@starfish.Convergent.COM>
Reply-To: fredex@cg-atla.UUCP (Fred Smith)
Organization: Agfa Compugraphic Division
Lines: 33

In article <1191@starfish.Convergent.COM> jerry@starfish.Convergent.COM (Gerald Hawkins) writes:
>cliffhanger@cup.portal.com (Cliff C Heyer) writes:
>>I'm about to start some C programming
>>on MSDOS and was wondering what
>>the best editor was to use.
>>Cliff
>
>The ideal editor would have excellent multiple window features, great
>mouse support, and understand c and other styles.  It might warn you of
>imbalanced quotes, parenthesis, braces, etc., if it was REALLY good.  If
>it was OUTSTANDING it would even offer warnings about possible subtle
>errors like braces, semicolons, etc., inside comments.  Also any
>warnings, features, tabsize, substitution of spaces for tabs, etc., would
>be user selectable in a setup file (like qedit's).
>




Well, for what its worth, I use PC/VI, sold by the now-defunct
custom Software Systems , formerly of Natick MA (There is also a PC
version of vi from MKS which is said to be (virtually)complete), and I
find that it even has the same bugs which appear in VI on the
system V machine I used to work on. When I am not using PC/VI, I am
using MicroEmacs because it allows multiple windows, works with a mouse,
and also has many of the features requested in the previous posting.

The trouble with MicroEmacs (nay, ALL emacs's) is that my fingers are
well-trained for the vi command keys, and when using some other editor
I find that my files tend to have oddcollections of h, j, k, or l's
interspersed in them!

Fred