HP3000-L Archives

September 2001, Week 4

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Stan Sieler <[log in to unmask]>
Reply To:
Stan Sieler <[log in to unmask]>
Date:
Fri, 28 Sep 2001 15:00:12 -0700
Content-Type:
text/plain
Parts/Attachments:
text/plain (49 lines)
Re:
> the PC's printer. Destructive backspace (where a backed-over character
> disappears) is simply something most people seem to find pleasant.
...
> the paper was obviously impossible (or at least difficult). Today, virtually
> everyone who uses a terminal emulator has grown up with PCs, where
> destructive backspace is the norm. Moreover, these same people have likely

But ... those PC-based terminal emulators seem to default to
*NON*destructive backspace.  I just tried the free Telnet client in Win98,
and it works that way, as does WRQ Reflection.

NONdestructive backspace is useful...if I start to type xuperbly, but realize
that I hit "x" instead of "s", I can back up to the "x", press "s",
and then do either of two things:

   1) type "uperbly" ... having the old text there as a guide!
      (I don't know about you, but having a guide to remind me of what I meant
      to type is getting more useful as I get older :)

   2) press up-arrow, control-X, and then <ENTER> to transmit the entire
      now-correct line on the screen.

...neither can be done with a destructive backspace.

In short...if QCTerm is a *TERMINAL* emulator, then there is no choice: the
backspace must default to non-destructive, like the rest of the emulators.

Doesn't Reflection offer an escape sequence to change modes?
If so, I'd recommend using that.

If not, I'd recommend either making it configurable, or making it only non-
destructive.

Also, don't forget that a backspace might not originate from the *keyboard*...
it might be sent by the computer to move the cursor, and the computer might not
expect (nor the user appreciate) text disappearing from the screen!  Sure...
you can say "okay, we'll differentiate based on the origin of the backspace",
but then you have a simple character sequence acting differently based on the
origin...imagine having to explain that to users and programmers!

Stan

Stan Sieler                                           [log in to unmask]
www.allegro.com/sieler/wanted/index.html          www.allegro.com/sieler

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *

ATOM RSS1 RSS2