Re: How to separate backspace and control-J functions?

[Eric Blake <ebb9 at byu dot net>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to airplays55@yahoo.com on 5/15/2005 9:40 AM:
> On my Debian Linux bash shell, the backspace key kills
> the current character ("backward-delete-char" function
> in .inputrc) and my ctrl-H key simply moves the cursor
> left ("backward-char" function in .inputrc)
> 
> However, in cygwin's bash shell, whenever I use
> .inputrc to assign a function to control-J, then the
> backspace key gets the same function.  (the .inputrc
> line is  "\C-H": backward-char )

Huh? control-J and control-H are distinct characters, and backspace only
ever interferes with control-H.  Usually, control-J is synonymous with the
Enter key.  I don't know what question you were trying to ask, but assume
that you are really trying to separate backspace from control-H.

With that assumption, if you are using $TERM of cygwin, there is no way to
perform the separation.  Backspace IS control-H, and you must live with it
(or else submit a patch that creates a new terminal type, perhaps called
cygwin-bs, with different key-mappings and new termcap/terminfo database
entries, and a way for the user to select which of the two cygwin terminal
types they want).  But if you are using rxvt or xterm, see this recent
post for the trick to turn backspace into ^? instead of ^H, and for a web
page with more details about changing your keyboard layout:
http://sourceware.org/ml/cygwin/2005-05/msg00472.html

- --
Life is short - so eat dessert first!

Eric Blake             ebb9@byu.net
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org

iD8DBQFCiJZ584KuGfSFAYARAg2dAJ4wA2K2TWAqDZUJEHiNCpkgunKw7ACgw8C1
8MNo9pOym0kkUIvlYXsk0GU=
=KTPv
-----END PGP SIGNATURE-----

--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://cygwin.com/docs.html
FAQ:                   http://cygwin.com/faq/