Neil Heller wrote in a message to Roy J. Tellason:

NH> Parse error before x.

RJ> I kept hitting that one a bit earlier,  then found that I'd 
RJ> inadvertently typed a ':' where I wanted a ';'...

RJ> Helps if you're using an editor that does syntax highlighing and
RJ> similar  stuff, which is a relatively new one for me,  too.  If I'd 
RJ> been paying better attention the different color would've 
RJ> made it more apparent to me.

NH> Syntax highlighting doesn't help in the situation of using ':'
NH> instead  of ';'. 

They sure did show up in different colors with the editor *I* was using...

NH> What _really_ got me though was the fact that the default character 
NH> size on the screen was reduced to fit a 50-line per screen size.

That's what I'm using now.

NH> I could never find any way to manually adjust that.  Drove me nuts.

Think that's bad,  try 60 lines by 132 characters.    I was doing
that for a while,  but it was a bit tough to deal with.

 NH> I was using Emacs.  Hopefully Rhide will be a bit more 
 NH> accommodating.

From what I see of emacs,  it appears to be very powerful,  but my needs in
an editor are fairly simple.  Under cp/m I used a product called VDO2
(Video Display (editor for the) Osborne),  later incarnated as VDE,  with
more features but somewhat clunkier to use.  And Wordstar,  3.3 and 4.0. 
Got 4.0 under dos,  but tend to only use that for situations when I don't
need hi-bit characters like box-drawing stuff (not much these days) and
want the formatting.  The rest of the time it's qedit,  or plain old edit
if it's a larger file and won't fit in the 400k plus that qedit will deal
with.  Under linux it's mcedit...

Does all I need for now.  And there are a bunch of other ones to try,  when
I have time to fiddle with editors.

---