[comp.sys.amiga] DME Executing make, is it possible?

anthes@geocub.UUCP (Franklin Anthes) (02/27/88)

 I wanted to rebuild my applications by just hitting a function key in
dme (version 1.29). So I mapped f3 to (execute (make >ram:result)), but
it doesn't work: dme gurus somewhere along the way, or just sits there
dead once the compiler and linker are done. BTW the compiler,assembler,linker
and make are all Aztec 3.4b versions.

 So what gives? Is it possible for these tools to work together?

 
 While I'm at it I'll air my latest "feature" craving for dme:

	When DME iconifies a window, I'd like to have the "icon"
    be visibly different (different color?) when a file has been 
    modified, but not saved yet!

 And also the last bug I've found: The modify flag (m) is only updated
once you move the cursor. So you canmodify your file, hit your nifty
save-only-when-modified-and-then-exit command, and dme will exit
without saving your mods (annoying!).
-- 

	Frank Anthes-Harper
Usenet: ....!ucbvax!decvax!uunet!mcvax!inria!geocub!anthes

dillon@CORY.BERKELEY.EDU (Matt Dillon) (02/29/88)

:
: I wanted to rebuild my applications by just hitting a function key in
:dme (version 1.29). So I mapped f3 to (execute (make >ram:result)), but
:it doesn't work: dme gurus somewhere along the way, or just sits there
:dead once the compiler and linker are done. BTW the compiler,assembler,linker
:and make are all Aztec 3.4b versions.
:
: So what gives? Is it possible for these tools to work together?
:

	Did you run DME from the workbench or the CLI?  DME simply
calls Execute() to implement execute, and that doesn't work if DME was
started up from the workbench.

: 
: While I'm at it I'll air my latest "feature" craving for dme:
:
:	When DME iconifies a window, I'd like to have the "icon"
:    be visibly different (different color?) when a file has been 
:    modified, but not saved yet!
:

	Probably won't happen, unless you can suggest an easy way to do
it.  The 'icon' is just a title-bar-high window.

: And also the last bug I've found: The modify flag (m) is only updated
:once you move the cursor. So you canmodify your file, hit your nifty
:save-only-when-modified-and-then-exit command, and dme will exit
:without saving your mods (annoying!).
:-- 

	This is a feature.  The bug is in the IF and QUIT commands.  The
feature allows you to fix a line you accidently typed something in while
the file is still unmodified, and have it still say it's unmodified when
you finally cursor off the (fixed) line.  It would be trivial for me to
add a 'line restore' to take even further advantage of this, I suppose.

					-Matt

peter@nuchat.UUCP (Peter da Silva) (03/03/88)

In article ... dillon@CORY.BERKELEY.EDU (Matt Dillon) writes:
> 	Did you run DME from the workbench or the CLI?  DME simply
> calls Execute() to implement execute, and that doesn't work if DME was
> started up from the workbench.

Browser and Eceute get along just fine if it's started from the Workbench.
But not if it's RunBack-ed. I'm in the process of doing up a replacement
for RunBack that should solve that problem. Anyway, what I do is create
a command file and Execute "NewCLI CON:whatever FROM file".
-- 
-- a clone of Peter (have you hugged your wolf today) da Silva  `-_-'
-- normally  ...!hoptoad!academ!uhnix1!sugar!peter                U
-- Disclaimer: These aren't mere opinions... these are *values*.