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:24AM -0500, Ted Unangst wrote: > Mark Kettenis wrote: > > > From: "Ted Unangst" <[email protected]> > > > 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't tmux supposed to be > > compatible with some standard terminal type? > > It could be. I don't know why tmux chooses a different set of bytes to > represent home/end than xterm. I mostly don't care. > > There was a thread on misc about this where it was suggested I either > reconfigure ksh or tmux. Or both. But that's silly. This should work out of > the box. > > If somebody would like to propose a diff for tmux, I'd be happy with that, but > I'm not sure where to begin myself. ksh already appears to be trying to > support a nonconflicting superset of terminal types without resorting to > termcap, so it seemed logical to fix here. > > http://marc.info/?l=openbsd-misc&m=144906064413240&w=2 >
