#LCTERM script ^C send?
30-Jul-90 15:12:42
Sb: #21109-#LCTERM script ^C send?
Fm: brian treadway 76116,3711
To: David Cressey 73230,1665
Dave: I guess I don't understand your assertion that CIS requires a "BS"
character to erase the previous character. When I want to erase the
character I've just typed I always hit the key above "Return" labeled with
an "X" inside a pentagonal "arrow" outline pointing to the left. I believe
that is the one you call RUBOUT, or at least equivalent to it. My "Rainbow
Owner's Manual" calls it the "delete" key. I assume, but have not checked,
that it generates the ASCII "DEL" character (octal 177), and that LCTERM
sends that character to Compuserve.
It has the effect of erasing the last character I typed. But what
Compuserve sends back is: a backslash, then the character being erased
from the input stream. If I continue "deleting" characters, the erased
characters continue to be echoed in reverse order as they are erased. A
second backslash ("\") is sent back when I stop deleting and start typing
again. For example, if I type
"go mail<DEL><DEL><DEL><DEL>charges"
in response to a "Messages !" prompt, what appears on my screen is
Messages !go mail\liam\charges
and Compuserve takes me to the CHARGES area.
I haven't tried putting a "DEL" character in a script file, but now that I
know LCTERM will send a Control-C in a script file I wouldn't be surprised
if it will send a "DEL" too. But why would I want to?
My keyboard has a "(BS)" label on the F12 key, but I don't think it sends
the ASCII "BS" character (octal 10). When I have to send a "BS" (for
example to erase a character in a command sent to my modem) I type
Control-H. LCTERM sends it just fine.
I can't see why an ASCII character with the name "DEL" shouldn't serve to
"erase" previously typed characters. What else can it do? ASCII "BS", on
the other hand, can be used to back up and overstrike on a hard copy. Why
should it be given the additional (and incompatible) job of erasing
characters?
BFT