🚀 go-pugleaf

In article <C7JBKK.Hn3@hpwin052.uksr.hp.com> bill@hppsde.mayfield.hp.com (Bill Gray) writes:
>In article <1tgocm$qr9@chnews.intel.com>, sberger@sedona.intel.com (Scott Berger) says:
>>
>>
>>I'm interested in reccommendations for MS Windows based programmer
>>oriented editors. 
>>
>
>Codewrite from Premia!
>

I USED to use Codewrite. It had so many bugs that I decided that I would 
use PFE even though it doesn't have an UNDO. Let's count the bugs in Codewrite:

Brief regular expression matching is missing the 'not' operation.
When the 'file changed' warning comes up DO NOT pick the reload option.
  The file has to be removed from the buffer then re-opened to avoid
  screwing it up.
Appropriate path setting is done 'randomly'. Sometimes the paths for
  makefiles, etc, are set - sometimes they aren't.

All of that nonsense I can live with. However:

If you edit a file on the C: drive and on the D: drive with the same
  name, buffer corruption occurs. I had assumed that my new hard drive
  had bit the dust when it was actually the editor screwing up.

This last problem caused me to panic for almost two days as I re-re-re
formated my new drive, re-re-re-installed NT, compilers, etc, etc, and lost
that much productive time.

I have since concluded that I am better off using Brief in a DOS box or
writing my own Windows editor.

tima@sequent.com