Forum unknown
· Talk to the Trade
Blitz Disk – Where?
5 messages in this thread
That example, the problem is actually that the WORDWRAP command should be
just WRAP, which is the proper keyword. In general, I recommend getting
the full AREXX package if you're doing serious macro programming and not
just using other people's macros – things like the quoting syntax are much
better explained in the AREXX manual. I should have more macros available
on the V2.02 TxEd Plus diskette, which should help – that will be going out
to folks with the V2.0 diskette "some time next month"- …cheath
I have the full Arexx, Charlie. I think I understand the quoting syntax. But
what had occurred was that I had several menu commands in my startup.txed to
shrink and expand the window. I found that the WI command would not work
unless the whole thing was in double quotes within the single quotes used for
the command. Furthermore, I found that the sequence of commands used to
configure TxEd were not recognized unless the command and following parameter
was in single quotes. The commands were ignored when the startup was
executed unless the quotes were included.
Steve
If you're having trouble getting a particular command-line thing to work
within an AREXX macro for TxEd Plus, often the easiest thing to do is try
the command outside of AREXX, just as a simple command line thing, and then
once you've got that working go back to the macro and figure out what you
need to do to Quote it. I think there's also an AREXX trace mode which
will display the commands exactly as they are sent to the TxEd message
port, though I forget what it might be- …cheath
If you're having trouble getting a particular command-line thing to work
within an AREXX macro for TxEd Plus, often the easiest thing to do is try
the command outside of AREXX, just as a simple command line thing, and then
once you've got that working go back to the macro and figure out what you
need to do to Quote it. I think there's also an AREXX trace mode which
will display the commands exactly as they are sent to the TxEd message
port, though I forget what it might be- …cheath
I have the full Arexx, Charlie. I think I understand the quoting syntax. But
what had occurred was that I had several menu commands in my startup.txed to
shrink and expand the window. I found that the WI command would not work
unless the whole thing was in double quotes within the single quotes used for
the command. Furthermore, I found that the sequence of commands used to
configure TxEd were not recognized unless the command and following parameter
was in single quotes. The commands were ignored when the startup was
executed unless the quotes were included.
Steve