That couldn't possibly work. Even assuming that by "e" you mean the
Ascii-238 epsilon character, those [wX] SEarch wildcards will NOT do
the job!
So that's why I've been seeing prompts of: XX.
Plus, the placement of that code would mess up Enter key
functionality if the cursor is in text and a DEFAULT command is on the
CMline.
Yes, I see that that's true.
But you do have a point insofar as insulating *all* DEFAULT and VA/NV
commands from the EB and WA reset would simplify matters
Yes, that was the idea--that you can treat all D [XX]= and all VA/NV the
same way. I see you simplified the former to D . I suppose that is unique.
So now if the CMline begins with D{space], DEFAULT{space}, or VA/NV{space]
you null out S/G 02. Then only if 02 is non-null do you set EB and WA
before doing the XC. And the rest looks the same, to a cursory scan. Except
no SUbroutine, and only 3 S/Gs! Nifty.
Do you get, as I do, "Command is not recognized" when you do CA$ U2?
Harry Binswanger
hb@xxxxxxxx