[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Backspace/Delete Issues?

From: Alain Bench
Subject: Re: Backspace/Delete Issues?
Date: Sat, 13 May 2006 15:27:24 +0200 (CEST)
User-agent: Mutt/1.4i-ja.1

Hello Michael,

 On Saturday, May 13, 2006 at 1:03:47 +0200, Michael Schroeder wrote:

> Actually I don't know a single application that looks at kbs.

    Mutt: To be able to bind the <BackSpace> key to a function, kbs has
to be right. Example try "bind index <BackSpace> show-version" and press
the key: It shouts either "Mutt 1.4i-ja.1 (2002-05-29)" if kbs is OK, or
"Key is not bound. Press '?' for help." otherwise.

> The right way is to check the ERASE stty setting.

    Not the only way, apparently.

    I wonder: On the principle Screen translates all special keys it
manages from the real terminal (as described by upstream TERM terminfo)
to the virtual terminal (Screen's fixed sequences). And TERM=screen
terminfo entry documents those Screen virtual keys for the downstream
applications. Example PuTTY's [F1] sends ESC[11~ but apps under Screen
receive ESCOP. Detach and reattach on an IBM 3151, where [F1] sends
ESCaCR, and apps still receive ESCOP. Screen's magic.

    But in Screen 4.0.2 the [backspace] key doesn't seem to be so
translated. Why?

    I understand that keys like [F42], [backtab], or [undo] are not in
the minimal common set of keys managed by Screen. Those are sent as they
are, untranslated. Not portably usable by apps. But [backspace]?

Bye!    Alain.
« Be liberal in what you accept, and conservative in what you send. »
        Jon Postel / Robustness Principle / RFC 1122

reply via email to

[Prev in Thread] Current Thread [Next in Thread]