-=> Quoting Stacy Smith to Carl Forester <=-

 SS>
 SS> CF| The thing that really bothered me about the new IDE is that it
 SS> | uses the epm editor which really sucks.  I end up using the
 SS> Windows ide,
 SS> See my preceding message that tells you how to change the editor to
 SS> whatever OS/2 editor you want by editing the IDE.CFG file in the
 SS> \WATCOM\BINB subdirectory.  I use QEdit/2 for my editor in the OS/2
 SS> host IDE.

I changed to the VI editor.  Thanx for the tip.

 SS> CF| can't even print from it.  Another complaint is I think the editor
 SS> | should be part of the IDE like Turbo C/C++.  IDE does stand for
 SS> | Integrated development environment doesn't it.
 SS>
 SS> I disagree...I want to be able to plug in whatever editor I choose.  I
 SS> hate being forced into someone else's editor, whose keystrokes are
 SS> non-standard and/or WordStar 3.3 format.

There could still be that option to use your own editor.  I like the
integrated editor, because it's a lot quicker than having to wait for
your editor to load every time you make a change.  I've tried to leave
the editor open and just save the file when I'm finished(which is also a
pain) but it seems like the IDE wants to open up another session of the
editor instead of calling the old session back to the foreground.  This
might have been fixed with the new release, but I'm kind of used to
closing the editor, and have not tried again.


 SS> IDE looks (to me) more like a graphical MAKE facility, which suits me
 SS> just fine... 

That's exactly what it is.  It's better than writing the make file by
hand, but I think they could have done a hell of a lot better job.  Maybe
in the next release they'll improve it instead of leaving it half done.

-Carl-





~~~ PGPBLUE 2.5 

... If you treat people right they will treat you right;90% of the time
--- Blue Wave/Max v2.20f Beta