-=> /* Quoting James Mckenzie to Mike Bilow */ <=-

 MB> The OS/2-hosted IDE for Watcom comes with IBM's EPM editor, which
 MB> is a fairly basic PM editor that omits niceties such as color
 MB> syntax highlighting. However, Watcom also ships a rather nice Vio
 MB> editor, vi, that does have color syntax highlighting and is
 MB> actually pretty good, although its existence seems to be
 MB> undocumented.

 JM> And how do we replace EPM with this (EPM comes with OS/2 not Watcom. 
 JM> Watcom calls it as the default.)  However, Watcom does come with a
 JM> messy Windows editor.

I changed mine to QEDIT/2.  It works just peachy:-)!  Love
it!  Here's the message I used for reference as I set it
up.  BTW, the new QEDIT/2 v4.0 (now called TSEJr/2 v4.0) is
GREAT!

-Frank

======== snip =========

Ä Area: FIDO-OS/2-Programming ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
  Msg#: 3177                                         Date: 31 Oct 94  12:13
  From: Michael Duffy                                Read: Yes    Replied: Yes
    To: Preston Smith                                Mark:                     
  Subj: Re: WATCOM C++ Editor
ÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄÄ
{at}MSGID: 1:147/3006.0 2eb533b5
{at}PID: BWRA 3.02 [Reg]
{at}TID: GE 1.1+
 -=> Quoting Preston Smith to Peter Fitzsimmons <=-

 [quoted message deleted]
 ...
 PS> - can you tell me how i could integrate another
 PS> editor (like Boxer) into the IDE 
 PS> thanks

 PS> Preston

To do this you have to go dinking around with the ide.cfg file.  Be warned
that the patch upgrades only work on the original file, so if you ever want
to patch the .cfg files, you have to restore the old version, patch it, and
then go back in and re-make all of your alterations by hand.

To get something like Boxer to integrate into the IDE, you have to find
the instances in the ide.cfg file where the DLL "!Editor" is run.  For 
example, if you replace the line in the section "Rule TXT":
Command "!Editor Editfile ${at}"
with
Command "c:\\box_path\\b2.exe ${at}"
you will launch BoxerOS2 instead of the default editor.  You can add any 
command line options that you want.  Of course, you will want to replace
"box_path" with your own path.  The "${at}" expands to the
path and filename of
the file to edit.  This alteration will affect double clicking on a file in
the target window.  I think you have to edit other lines to get it to launch
from the icon on the toolbar.  You can also make alterations to use your own
text editor for viewing/editing a disassembly.  

You cannot use your own editor for when you double click on Warning and 
Error messages in the Log, as the launching of the editor was hard coded 
in this situation.  I have no idea why.

Also, since boxer is being passed a specific filename, it does not load up
the list of previously edited files (Shift F1).  Bummer.

I also wish that OS/2 would expand the size of the window when text mode 
editors like Boxer go to a higher row resolution. *sigh*

Hope this helps,
Michael Duffy

... Yes, I program PCs.  Stop laughing.
-!- GEcho 1.10+
 ! Origin: Knight Mare 405 672 5644 (1:147/3006)
{at}PATH: 147/3006 1032 3615/50 104/1 512 525

======= snip ========


--- Blue Wave/RA v2.12 OS/2