🚀 go-pugleaf

I am a devoted and fanatical Emacs/Epsilon user, recently returned
from Unix to do some PC programming after a 4-5 year hiatus.  I was
always able to be extremely productive using Epsilon's
compile-in-a-window feature from DOS.  This allowed me to continue to
edit while running Lattice, Microsoft, or Metaware compilers in the
background, with error messages going to a window.  I was able to
concurrently examine and fix errors in files while a long Make was
transpiring, using the emacs-like next-error feature.

I cannot imagine being a productive programmer without this level
of integration.

I know that some of this functionality is offered by Borland C++ 3.1's
integrated development environment, but I have several problems with
it:
        1.      I don't want to use their editor.  I want to use
                Epsilon, because I know it inside and out, I've spent
                a lot of time programming it with EEL to make
                it an ideal environment for me, it's lightning
                fast, and it's got the same UI (modulo a few tweaks)
                as Gnu Emacs on Unix, which I continue to use extensively.
                I'm not interested in learning Borland's editor.  I'd
                prefer not to work with an Epsilon "emulation", because
                it wouldn't have my mondo-nifty enhancements for doing
                my style of C indentation, comments, Gnu Emacs-like
                interactions, etc.  It probably wouldn't have kill-ring
                or incremental search support, either.

        2.      It doesn't let me examine errors until after the whole
                build process is complete.  Compiling in IDE locks up your
                quasi-multitasking Windows 3.1 system for the duration.

        3.      It's a graphics-mode text editor, and my graphics card
                (Diamon Speedstar SVGA) is much faster in text mode, and
                lets me see more of my text at once.  In fact, my
                graphics card has really pathetic text scrolling
                performance when operating in graphics mode.  It's slower
                on a 386/33 than an IBM XT running Epsilon.

        4.      I can't seem to figure out how to build non-windows
                executables from inside the IDE.

Borland supplied a command-line interface to their compiler, BCC, but
it seems to crash my PC whenever I run it from inside Epsilon 5.03.
So my guess is that BCC is doing something dirty that is messing up
Epsilon.  Anyone have any idea?  Is there a new version of Epsilon
that fixes this?  Is there a BCC command-line switch that causes it
to work better in an Epsilon window?

Thanks in Advance,
-Josh
-- 
Joshua Marantz                          You make my life and times
Viewlogic Systems,                        a book of bluesy Saturdays
josh@viewlogic.com                      And I have to choose...