RE: Anyone else needing this U2 updater?

["Harry Binswanger" hb@xxxxxxxx]

Boy, a lot to think about here. Thanks, Carl.

The reason for all the separate locations and filenames is to
avoid stepping on my own toes--doing something that messes things
up, which I've done many times. My frame breaks everything down
into baby steps that I can re-trace if something goes wrong
(though one could ask how could anything go wrong if I've got a
tested frame?--the errors come when I do it by hand).

U1? Who knew?

Could you please explain what this means:

LOAD DUMMY.U2; ==> COPY/NV EDITABLE.U2 HB.U2 <== ; LOAD HB.U2.

It's the arrows that particularly throw me, plus not knowing what
the three different filenames designate.

Regards,
Harry


-----Original Message-----
From: xywrite-bounce@xxxxxxxx
[mailto:xywrite-bounce@xxxxxxxx] On Behalf Of Carl Distefano
Sent: Saturday, December 31, 2016 5:32 PM
To: xywrite@xxxxxxxx
Subject: RE: Anyone else needing this U2 updater?

Reply to note from "Harry Binswanger"  Sat, 31
Dec
2016 14:10:29 -0500

Harry,

> What you recommend is the yang of my yin.

True, to a point. I was objecting to two things -- well, actually,
three: The need to put the new XYWWWEB.U2 in a specially-named and
-located directory. The futzing around with intermediate filenames
(new.u2, MYFRAMES.U2). The need to add special strings
(MyFramesStart,
MyFramesEnd) to demarcate personal frames. Too much complication
for a simple copy-and-paste operation.

My way requires two filenames (not three): HB.U2 (or whatever you
choose to call your U2 file) and XYWWWEB.U2. The new XYWWWEB.U2
stays in the directory where God intended it to be -- Editor's
directory. And there's no need to prep your U2 with special
boundary strings. Just download U2 (U2DL), unzip it into
Editor's dir, and RUN UPDATEU2.PM. And it takes 75% less code to
accomplish the task.

I have one other recommendation. If you're constantly tinkering
with U2, it's safer to edit a *copy* of your U2 file rather than
the loaded file itself. This requires an extra step when you
reload U2, but it's worth it: LOAD DUMMY.U2; ==> COPY/NV
EDITABLE.U2 HB.U2 <== ; LOAD HB.U2.

Alternatively, if none of your framenames clash with U2 names,
have you considered moving yours into a *U1* file? All you'd have
to do is change JM calls to your frames from JM 2.hbfooQ2 to JM
1.hbfooQ2 (while calls to U2 framenames would stay as JM
2.framenameQ2 ). You'd also have to add a trapname frame at the
end of U2 that redirects non-U2 framenames frames to U1, so that
you could still use  to launch your frames:

XPLeNCODE v2.0 (ENCODE.EXE)
b-gin [UNTITLED]
{123}{123}5*{125}{125} Trapname to redirect to U2[cr|lf]{002}{<}
SX00,{<}VA$FR{>}{>}[JM_]1.{<}PV00{>}[Q2_]{002}[cr|lf][cr|lf]
-nd
XPLeNCODE

That's a way of looking out for Number One, while using U2 too.

--
Carl Distefano
cld@xxxxxxxx