• Subject: Re: 0.15.7 released.
  • From: Linux Server <everidge@xxxxxxxx>
  • Date: Sun, 13 Feb 2000 20:24:24 -0500

Sean Porterfield wrote:

> I was going to agree, but my backspace functions as the delete key!  Scary...
> Also, the cursor isn't positioning as it should and will go back to the first
> field on the screen after a break message is received.
> (My xterm does resize now when I go to 132 char mode, though!)
> Jeff Volckaert wrote:
> > I also noticed the backspace doesn't seem to work on mine.
> >
> > Jeff Volckaert
> >

There seems to be a comflict in ideas concerning the 'backspace' key.  In Client
Access/400 the
Backspace key is a 'destructive' backspace.  In the 3476, 3477, 3486, 3487
world, it's a
'backspace' non-destructive.  It all depends on the implementation
desired/used.  Some like the
non-destructive, I like the destructive backspace.  What it boils down to is
personal preference
and a programmers nightmare and long nights of lost sleep.  I guess that's why
software emulators
have a keyboard mapping files.  I guess there could be an improvement here by
allowing an easy
way to configure the keymaps via software.  I'm sure you guys have this in your

I will have to admit, even with the emulators odities, it's a great product
worthy of a pricetag.  I've
paid good money for less software.

Mike Everidge,
IS Director/CNE
Lakeway Regional Hospital

| This is the LINUX5250 Mailing List!
| To submit a new message, send your mail to LINUX5250@midrange.com.
| To subscribe to this list send email to LINUX5250-SUB@midrange.com.
| To unsubscribe from this list send email to LINUX5250-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2020 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].