GDB> the only reason for all of the things that
   > you are doing is to display a message.
 Because displaying a message was the easiest useless way I saw
 to dispose of the string that the example I copied wanted to
 produce.  I never even see that message, since I shell out so
 fast.  But I'll trim back the macro, now that I know I can.
GDB> if you used PickFile(), you could internalize the whole
   > thing as a macro so you don't have to shell to 4DOS.
 Glancing at the Help for that, I don't see any sign that it can
 tag multiple files to be acted upon, as select can, but I'll
 check out the suggested macro in more detail later.
GDB> this was the only way I could think of handling this situation.
 I played with it, and found out that 'VidBorder(Color(Yellow))'
 was sufficient, that you didn't need to have it be
 'VidBorder(Color(Yellow on Black))' for it to work.  And I
 temped a little macro to play with various border colors by
 number, modifying some example from somewhere.
proc VidHue()
    string hue[3]=''
    integer tint, hist
    hist=GetFreeHistory("VidHue:hist")
    if AskNumeric("Color Number:",hue,hist) and Length(hue)
    tint=Val(hue) if tint VidBorder(tint) endif endif
end
GDB> That's really old code -- written for the 1.0 "Pre-Release" of TSE.
 I copied the macro last night and methodically went thru it,
 commenting out chunks of it.  I'm not sure which one actually
 did it, but eventually I got a trimmed version that worked, that
 I could build up as I wanted it to be.  I never (initially) changed
 my part that was supposed to call PickList, so it seems it was
 something in the engine that was just rejecting a calling macro
 faithfully copied according to the sample it gave to make one.
... Guns aren't lawful; / Nooses give; / Gas smells awful; /
 -- SR 2.00 #1019  -!-  You might as well live. * Parker
--- QScan/PCB v1.17b / 01-0175
---------------