Re: programming editor

["Eric M. Monsler" <emonsler beamreachnetworks com>]

XEmacs is what I use.

In fact, I right now have open files from my Solaris account,
SMB-mounted onto my NT machine, that I compile on NT from XEmacs using
cygwin make, I can edit the gtk files from my NT XEmacs that I compile
on Solaris (via xterm), and I am editing local drive files that I
compile with Green Hills tools on NT.  Having tasks on all three
platforms that share messages, and have similar code, it is really nice
to edit using the same tool, and in fact to have all three sets of files
open from within the same tool.

If I'm doing primarily gtk work, I run the Solaris XEmacs, can build
from within XEmacs, but have to switch to a cygwin bash shell to compile
the cygwin program, or to a dos shell to compile the Green Hills
program.  But then I can't  (currently) edit the GH files, since I don't
have those in my UNIX homedir.

If I could just get the Green Hills "dmake" to work from within NT
XEmacs, I'd be set, but dmake seems to inherit enough from NT XEmacs
(and/or my cygwin installation) to think it's running on a UNIX box, and
tries to use /bin/sh to run .ksh scripts, rather than cmd.exe to run
.bat files.

Eric

P.S.  Of course, your preference for 7) is not the default behavior, but
why have separate copies running, instead of multiple windows of the
same background program and set of open files?  You can do so, though,
if you want.