Re: XPL shortcuts etc. [long]

[Robert Holmgren holmgren@xxxxxxxx]

** Reply to note from "..."  Mon, 6 Jan 1997 20:18:35 -0500 (EST)

>> ...in 3+, impossible to get all three with accuracy.

> Oh, yeah? Well, {is101}, {is102}, and frame $3 just did it...

Now now Annie! No premature gloating! It's not just me; it's Annie
against EVERYBODY. Seriously, if you can really solve it, you get full
credit. But a lot of people tinkered with this problem, and somebody
always poked a hole in every solution. I haven't used 3+ since Sig was
born, and I've forgotten more than I ever knew -- but that's my
recollection of the bottom line. Believe me, your solutions have occurred
to people in the past; there aren't unlimited ways to skin these critters.
For example, I can see at least one blatant situation where your solution
bombs (and this is just looking at the first third of it, i.e. S/G 101 in
text file FURTHER), namely on an open but empty text window: cursor ends
up on CMline no matter where it was originally located. (What *are* those
10 other files comprising 9951 bytes in FURTHER.ZIP, anyway? No, wait,
don't answer that...)

As for working around 3-byte characters on input, why do we need to? Why
do you have functions assigned to the alphanumeric keys in your lower case
TABLE? The accepted wisdom is that NI is only necessary if the Alt
shifting key is part of a TABLE= definition, and then generally only on the
number pad plus a few of the extended keyboard keys >84 (because Alt
otherwise bleeds through the Xywalls to DOS). Func AR on an alphanumeric
key in the lower case table?? How pray do you type lower case letters?
Don't tell me you've upgraded to Warp v4 in order to control XyWrite with
OS/2 voice recognition? Wow! That's how I'm dictating this note! Ain't
it neat?

> 4. The original leaves pfun XX on the CMline; my version leaves the arg
> going in, with the symbol at the CMline cursor location--not necessarily
> the last char in the arg.

So does mine. LDPM it. No change whatsoever to the pre-existing CMline.
Inserts the true func where the cursor was, within pre-existing CMline
string. Or puts the func in Text window, if that's where the cursor was on
entry. Am I misunderstanding you?

As for $A and those others, frankly I saw an old note to myself, next
to my PFUN routine in v3 .HLP, which said that they require workarounds.
Didn't look into it... OK, sure, various problems: Ascii 253 wants to
bind with two characters to its right; funcs that end with Ascii-13 are
hard to parse -- or some damn thing, I dunno; funcs like WC that end with
Ascii-0 can't be SAved by Xy3; etc etc etc. As you say, it's always
*something* with Xy3.



-----------
Robert Holmgren
holmgren@xxxxxxxx
-----------