>John Aldrich wrote:
>> 
>> On Sun, 27 Aug 2000, David A. De Graaf wrote:
>> > I've installed yet another RedHat 6.2 system and have again run afoul
>> > of the Great BackSpace Key Fiasco.
>> >      [snip]
>> I'm using 6.2 and here it only deletes the last character.
>> Perhaps your keyboard repeat rate is set too high?
>>      John
>
>I complained incorrectly that RedHat delivers a system with a broken
>Backspace key, and I apologize for my misstatements.  That's because I
>had installed some, but not all of my edits to change the Delete and
>Backspace key behaviour to be like UNIX SysV.
>
>It is true that Backspace seems to work in a freshly installed RedHat
>6.2 system.  But Delete doesn't, and fixing Delete makes Backspace
>not work. 

You didn't mis-speak.  With RH6.1, the backspace operated correctly
within applications that were started within an Xterm.  After the 6.2
upgrade IT DID NOT.  The backspace function WAS CHANGED.  As posted by
another user, the following had to be entered in my .Xdefaults:

        XTerm*backarrowKey:     true

Now, why adding the above fixes the backspace key is beyond me.  But it did.

I know that Xterm was changed because the bold text is now blue and
I DID NOT do it on purpose.  With 6.1 it was black.  Why was it changed
in 6.2?  Now I have to find out where that is set, or what it takes to
change it.

If you want to add new features to the program fine.  I like new features.
But damn, don't force them on me.  I certainly did not want backspace
drastically changed in how it functioned.  Change the program to add the
new features, but leave the new features OFF.  Change the documentation
for the program to explain the changes.

An error on my part was not reading the RELEASE-NOTES file.  But that
doesn't help much, as it says:

    Changes to termcap and terminfo entries -- The termcap and terminfo
    entries have been changed to make the actions of the following keys
    more consistent:

        o Backspace

        o Delete

        o Home

        o End

    Changes may be made by editing your .inputrc file.


OK, more consistant how?  How does the changes affect the user?  Change
the .inputrc file, how?  There isn't a man page for .inputrc, so where
are the instructions.  A reference would have been nice.  I'd like to
put things back to way the were for 6.1, but have no idea how.

BTW, I don't think that making the backspace key delete the character
under the cursor is correct.  That is NOT what backspace means.  Who the
Hell thought that turning backspace into "delete under cursor" was correct?
If you are in VI and you are entering a new line and hit backspace, it
deletes the newline and joins the two lines together.  BAD, BAD, REALLY BAD.

The RELEASE-NOTES did not explain the Xterm colorization.

>As delivered, in both console and xterm screens:
>
>$ stty -a
>speed 9600 baud; rows 24; columns 80; line = 0;
>intr = ^C; quit = ^\; erase = ^?; kill = ^U; eof = ^D; eol = <undef>;
>
>and running od -c to display what is actually emitted to stdin:
>  Backspace key                =>  nothing
>  Delete key           =>  \033[3~
>  ^C                   =>  kills the process
>
>This is not what I want.
>I want the Delete key to emit '0x7f' (often displayed as ^?), and
>the Backspace key to emit ^H, and the stty settings to be
>  stty  intr ^?  quit ^C  erase ^H  kill ^U
>
>With this setup, the Backspace key (^H) still removes the last typed
>character, but the Delete key (^?) terminates a running process.
>The ^C terminates a process AND produces a core dump.
>(You will recognize this as normal UNIX Sys V behaviour.)

Umm, no, ^C is NOT supposed to terminate the running process and produce
core.  Yuch!  Even under Sun Solaris, which is System V, a ^C does NOT
produce core.  The last thing I need is core files all over the place.
Even above you list quit as ^C.  Quit doesn't produce core.

>I've just discovered the documentation for  readline  while searching
>frantically for any information about /etc/inputrc (there isn't any!).

Great, the RELEASE-NOTES says to modify .inputrc and yet there is ZERO
documentation on how it is configured.  Lovely.

MB
-- 
e-mail: [EMAIL PROTECTED]
    Bart: Hey, why is it destroying other toys?  Lisa: They must have
    programmed it to eliminate the competition.  Bart: You mean like
    Microsoft?  Lisa: Exactly.  [The Simpsons - 12/18/99]
Visit - URL:http://www.vidiot.com/  (Your link to Star Trek and UPN)



_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to