tbabej / vit

Placeholder to demostrate issue porting for VIT.
0 stars 0 forks source link

[VT-62] Backspace doesn't work in vit (xterm) #62

Closed tbabej closed 6 years ago

tbabej commented 6 years ago

Ben Boeckel on 2012-11-28T22:27:13Z says:

In xterm, backspace just outputs '^?'. In tmux (screen-256color), the same thing happens.

tbabej commented 6 years ago

Migrated metadata:

Created: 2012-11-28T22:27:13Z
Modified: 2014-02-09T02:23:41Z
tbabej commented 6 years ago

steve rader on 2012-11-29T00:22:52Z says:

Brian - could you please try v0.4 and change line 885 from...

     if ( $ch eq "\ch" ) {

to...

     if ( $ch eq "\b" || $ch eq "\c?" ) {

and report back? If you can't, no biggie. I'm about 99% sure that's the workaround and this will be fixed in v0.5 due out on Friday, Nov 30 2012.

tbabej commented 6 years ago

steve rader on 2012-11-29T00:23:37Z says:

steve rader wrote:

Brian - could you please try v0.4 and change line 885 from... [...] to... [...] and report back? If you can't, no biggie. I'm about 99% sure that's the workaround and this will be fixed in v0.5 due out on Friday, Nov 30 2012.

Umm, yeah, BEN!
Sorry for getting your name wrong.

tbabej commented 6 years ago

Ben Boeckel on 2012-11-29T00:42:21Z says:

Nope. Other keys don't work as well (^W is one I've gotten used to by now). Any reason for not using Term::ReadLine-Gnu (or equivalent)?

tbabej commented 6 years ago

Ben Boeckel on 2012-11-29T02:56:25Z says:

Oops, it does work (missed the h -> ? change). At least my ^W typos can be deleted now :) .

tbabej commented 6 years ago

steve rader on 2012-11-30T17:57:37Z says:

So backspace and delete both work now. And I added ^w, which was also on the todo list. I assume you know about ^u.

tbabej commented 6 years ago

steve rader on 2012-11-30T18:05:35Z says:

Btw, you might consider adding...

    stty erase +h

...to our environment, where "+h" is RAW. In bash and/or vi, you can do that by doing...

     stty erase ^v^h

...because ^v allows you to "enter" raw characters. That will/should "unify" backspace and delete. Then you should find there's very VERY few contexts ^h WON'T work. (Old telnet and RCS commands come to mind as the only examples.) If it doesn't, then you can use +.