[comp.sys.amiga.tech] Arexx/dme

bdo8650@cec1.wustl.edu (Bryan Dennis O'Connor) (05/05/90)

	I have two slightly technical questions that are seemingly   
related.... here goes:

	1)  How can I change TABS in DME (v1.38) to be more Tab like.  
	    Such that when I hit tab in the middle of a line it moves the
	    line from that point over to the next tab stop?  I tried using
	    SPLIT TAB JOIN and it works except when there is white space
	    involved.  Any suggestions?

	2)  I used the EXECUTE function in v1.31 to call Lattice v5.05 by
	    doing a EXECUTE (LC -L ($filename)) and it would send the 
    	    output to the console window for reading error messages and
	    all.  In v1.38 it does not do this, it sends it to the NULL 
	    device.  (therefore I can't read the errors... not that I
	    ever have them :-)  ).
 	    Any ideas on how I could get it back to the console window?

	2b) What advantage would AREXX be in the above situation?  I know
	    that it is a macro script language but I have never heard of
	    any really awesome useful uses.  (Like in the above case).
	    Does anyone else use DME and Lattice?

	Thanks..  
		Bryan.


-- 
===============================================================================
Bryan O'Connor        |  ARPA:   bdo8650@cec2.wustl.edu | ******************** 
Washington University |  USENET: wucs1!cec2!bdo8650     | *UNDER CONSTRUCTION*
Saint Louis, MO       |                                 | ******************** 

a186@mindlink.UUCP (Harvey Taylor) (05/06/90)

In <1990May5.010147.16029@cec1.wustl.edu>, bdo8650@cec1.wustl.edu
                                        (Bryan Dennis O'Connor) writes:
>
>  1)  How can I change TABS in DME (v1.38) to be more Tab like.

        Put this in your .edrc.
# INSERT SPACES TYPE TAB
map tab (repeat tr `` '')

>       2)  [Problem where compiler errors are directed]
>       2b) What advantage would AREXX be in the above situation?
>           [...]

        Try this.
        Put this in your .edrc.
# Invoke your compiler
map a-c (RX1 LC.dme ($filename))
#

        Put this in Rexx:  as LC.dme

/*  LC.dme    */
/*  dme macro to invoke LC*/
parse arg fn
address command LC '-L' fn

>            Does anyone else use DME and Lattice?

        No actually. Just DME & A68k. I went back to 1.31 cause I didn't
    like the 1.35+ handling of pathnames & filenames. I want both in the
    menu bar so I know where saveold will go. Sometimes if you have 4 or 7
    files in different windows, it is too easy to lose track, for me at
    least. It seems that 1.31 thinks its $filename is only the original.
    At least, I think it does. I hacked around at it a bit & might have
    broken something.
        <-Harvey

 "Truth never set anyone free. It is only doubt which will bring
                                    mental emancipation." -Anton LaVey
  Harvey Taylor      Meta Media Productions
  uunet!van-bc!rsoft!mindlink!Harvey_Taylor
  a186@mindlink.UUCP

root@bcstarc.UUCP (Frank Pecher) (05/06/90)

In article <1990May5.010147.16029@cec1.wustl.edu> bdo8650@cec1.wustl.edu (Bryan Dennis O'Connor) writes:
>
>       1)  How can I change TABS in DME (v1.38) to be more Tab like.
>           Such that when I hit tab in the middle of a line it moves the
>           line from that point over to the next tab stop?  I tried using
>           SPLIT TAB JOIN and it works except when there is white space
>           involved.  Any suggestions?

Try the following macro definition:

    map (tab) (repeat tr (( )))

Every time you hit the TAB key, DME will write as blanks until it reaches
the next cursor position.

>       2)  I used the EXECUTE function in v1.31 to call Lattice v5.05 by
>           doing a EXECUTE (LC -L ($filename)) and it would send the
>           output to the console window for reading error messages and
>           all.  In v1.38 it does not do this, it sends it to the NULL
>           device.  (therefore I can't read the errors... not that I
>           ever have them :-)  ).
I think the newer versions of DME start programs as a background task (just
a guess). That's why you get no output on your current CON: window. But try
this:

    (execute (lc >ram:lcout -L ($filename))
     newwindow newfile ram:lcout
     execute (delete ram:lcout))

[Write all in ONE line, or better, map it to a key]
Now your compiler output should be written in a file named ram:lcout. The
next command will open a new window and will read this file into it. The
third command will delete it from your ram disk.

>       2b) What advantage would AREXX be in the above situation?  I know
>           that it is a macro script language but I have never heard of
>           any really awesome useful uses.  (Like in the above case).
>           Does anyone else use DME and Lattice?

I do. I use the DME for quite a long time, and yesterday, I bought Lattice.
The reason why very few people care about writing ARexx scrips for this
editor is, I think, because the DME macro language is itself powerful
enough. Not like ARexx, of course, but still, you can really do a lot with
it:-)

>       Thanks..
>               Bryan.

You're welcome
                Frank

--
\       "... and the universe will explode later for your pleasure!"       /
 \       -- Douglas Adams, The Restaurant at The End of The Universe      /
  \                            ADDRESS:            root@bcstarc.UUCP     /
   \____Frank Pecher___________BANG:____...!smurf!nadia!bcstarc!root____/