From | MIKE COPELAND
/---------------------------------------
| That's exactly my problem: how/why did _anyone_ think of when
|they wanted to use a macro. You've given me some things to
|consider, and I will ponder the actions I do often. I appreciate
|your answer, and I assure you, I'll be back for more... 8<}}
\---------------------------------------
To | GEORGE DE BRUIN
There are certain things that automatically suggest themselves as
macros. For example: compiling a program. When you are writing code,
you compile it often. It is easy to see that shutting down the editor,
or shelling to DOS to compile a program is a process that you do a lot,
therefore might lend itself to being written as a macro.
Mostly it really comes form identifying what you do. That's the only
way I know to come up with ideas for writing a macro.
George J. De Bruin
SemWare Technical Support
-- SPEED 2.0c #10: SemWare: QEdit Adv., TSR, OS/2 and The SemWare Editor
--- FidoPCB v1.4 [ff151/a]
---------------
* Origin: SemWare Support BBS * 404-641-8968 * (1:133/314)
|