Xref: utzoo comp.sys.atari.st.tech:1361 comp.sys.atari.st:34816
Path: utzoo!utgpu!news-server.csri.toronto.edu!cs.utexas.edu!uwm.edu!spool.mu.edu!sdd.hp.com!zaphod.mps.ohio-state.edu!pacific.mps.ohio-state.edu!linac!unixhub!slacvm!reeves
From: REEVES@SLACVM.SLAC.STANFORD.EDU (Terry Reeves)
Newsgroups: comp.sys.atari.st.tech,comp.sys.atari.st
Subject: Re: Uniterm 2.0e help
Message-ID: <91039.155450REEVES@SLACVM.SLAC.STANFORD.EDU>
Date: 8 Feb 91 23:54:49 GMT
References: <1991Feb1.152325.4730@ncsuvx.ncsu.edu>
 <91032.112332REEVES@SLACVM.SLAC.STANFORD.EDU> <4fb2916e.20b6d@apollo.HP.COM>
Organization: Stanford Linear Accelerator Center
Lines: 13

In article 4fb2916e.20b6d, Walt Weber points out how I may have given incorrect
advice for programming Uniterm to send the string "vax*" followed by a
carriage return when the F1 key was pressed. He then presents an example of
how to use macros within function key definitions to achieve the desired
effect. However, my solution does work and is simplier if all you want to do is
send the string "vax*" followed by a carriage return. There is no need to imbed
the string in a macro. Now if you need some real smarts in the characters sent,
then a macro is essential.

                                                Terry

Disclaimer: The above are my opinions and are not the opinions of SLAC,
            Stanford University, or the DOE.