Re: ksh another home/end pair

2015-12-30 Thread Theo de Raadt
>> In tmux, home and end send different bytes. I don't know why, but I want >> things to just work. We already have two different keys here, so what's one >> more? (how many can there be...?) > >We shouldn't have any there. That's what termcap(3) is for. If >you don't link to termcap, you don't g

Re: ksh another home/end pair

2015-12-30 Thread Christian Weisgerber
On 2015-12-29, "Ted Unangst" wrote: > In tmux, home and end send different bytes. I don't know why, but I want > things to just work. We already have two different keys here, so what's one > more? (how many can there be...?) We shouldn't have any there. That's what termcap(3) is for. If you do

Re: ksh another home/end pair

2015-12-30 Thread Nicholas Marriott
tmux is doing the right thing and changing what it generates would break other programs. ksh should use terminfo to work out what to expect, but we have always resisted linking ksh against ncurses. Your change is the best we can do without making ksh use ncurses. On Wed, Dec 30, 2015 at 01:19:

Re: ksh another home/end pair

2015-12-29 Thread Ted Unangst
Mark Kettenis wrote: > > From: "Ted Unangst" > > Date: Tue, 29 Dec 2015 12:11:25 -0500 > > > > In tmux, home and end send different bytes. I don't know why, but I want > > things to just work. We already have two different keys here, so what's one > > more? (how many can there be...?) > > Isn't

Re: ksh another home/end pair

2015-12-29 Thread Todd Mortimer
On Tue, Dec 29, 2015 at 10:02:48PM +0100, Mark Kettenis wrote: > > From: "Ted Unangst" > > Date: Tue, 29 Dec 2015 12:11:25 -0500 > > > > In tmux, home and end send different bytes. I don't know why, but I want > > things to just work. We already have two different keys here, so what's one > > mor

Re: ksh another home/end pair

2015-12-29 Thread Mark Kettenis
> From: "Ted Unangst" > Date: Tue, 29 Dec 2015 12:11:25 -0500 > > In tmux, home and end send different bytes. I don't know why, but I want > things to just work. We already have two different keys here, so what's one > more? (how many can there be...?) Isn't that somehowa tmux bug? I mean, isn'

Re: ksh another home/end pair

2015-12-29 Thread Brandon Mercer
On Tue, Dec 29, 2015 at 12:16 PM Ted Unangst wrote: > In tmux, home and end send different bytes. I don't know why, but I want > things to just work. We already have two different keys here, so what's one > more? (how many can there be...?) > > > Index: emacs.c > =

ksh another home/end pair

2015-12-29 Thread Ted Unangst
In tmux, home and end send different bytes. I don't know why, but I want things to just work. We already have two different keys here, so what's one more? (how many can there be...?) Index: emacs.c === RCS file: /cvs/src/bin/ksh/emac