Re: Sending XyWrite Files ... Adding a cue at the top

[Eric Van Tassel 101233.342@xxxxxxxx]

As noted yesterday, when I "simplify" a XyWrite file by inserting
plain-ASCII strings in place of guillemet'd commands, I put at the *top* of
the file a short line telling the recipient what I've done. RvR asked how.
Below is my (probably clunky) way of doing it; but I'm hoping that over the
next day or two some of my betters in this group offer some neater methods.

Cheers
Eric Van Tassel


Since I still haven't mastered e-mail attachments or zipping/unzipping, for
this purpose I use the following substitutions:
  < and > appear thus in the program (and in the text file I'm coding)
    (they could also be -- and sometimes are -- { and })
  in this case, { } correspond to guillemets in the program file
  [BC], [XC] and [TF] are 3-character function calls in the program

The following is extracted from a longer program -- in this case, the macro
that I run before I e-mail a XyWrite text file that includes mode commands.

The program starts with a whole string of SaveGets; in the extract here,
the SaveGets are those that explain the codes for beginning and ending
superscripting.
Each SaveGet ends with a hard return: therefore, when the SaveGet is
inserted at the top of the file it will appear on a line by itself.

The program gives these SaveGets in a counter-intuitive order: in this
extract, for instance, it codes a mode-cancelling string before the mode
that it cancels. This is so that any SaveGets that the program picks up and
inserts at the top of the file *will* be in intuitive order: in this
instance, if the file does include both MD+SU and MD-SU, the line
    <+SU>=...
will appear just above the line
    <-SU>=...

Incidentally, since the macro relies entirely on "if error" arguments, it
gets very tedious to be beeped at by a whole succession of error messages;
and each error message then requires an AnyKey stroke. To avoid that (so I
can go away and do something quietly irrelevant while the macro runs) the
program file begins with
             [BC]es 1[XC]
which suppresses error messages (although, crucially, XyWrite still
triggers error messages and the macro still recognizes them as such). The
corresponding
             [BC]es 0[XC]
is input at the end of the file just before {EX}.



{SV015,<-SU>=end superscript
}{SV005,<+SU>=begin superscript
}


{LBsupx}[BC]cia |{MD-SU}|<-SU>|[XC]{IF{ER}}[TF]{GLsup}
{EI}[TF]{GT015}{GLsup}

{LBsup}[BC]cia |{MD+SU}|<+SU>|[XC]{IF{ER}}[TF]{GLboldx}
{EI}[TF]{GT005}{GLboldx}

{LBboldx}[BC]cia |{MD-BO}|<-BO>|[XC]{IF{ER}}...
etc.