My apologies for the lack of clarity. Based on these tests on the keypad before tput xterm numpad on sent 8 tmux numpad on sent 8 xterm numpad off sent \e[A tmux numpad off sent \e[A
after tput xterm numpad on sent 8 tmux numpad on sent 8 xterm numpad off sent \eOA tmux numpad off sent \eOA I believe this is approximately the expected behavior but it still doesn't perform the same once tintin++ is open. I'm almost guessing the tintin++ code is doing something weird with the TERM environment variable but that's just a wild guess since I'm not familiar with this level of detail on terminal things. On Saturday, February 22, 2020 at 5:58:25 PM UTC-5, Nicholas Marriott wrote: > It's not very clear what you are seeing inside and outside tmux. > > > tmux sends VT220 sequences when in application keypad mode, that means \eOo > for 0, \eOp for 1 and so on. This should be the same as xterm. > > > This is assuming tmux can itself recognise the keypad keys which depends on > the terminal outside sending VT220 sequences (tmux does not use terminfo for > this), but xterm should do so. > > > tmux won't be able to do this with numlock off because IIRC then xterm just > sends the normal key sequences, so a keypad Up looks the same as a normal Up > (\e[A like you are seeing). > > > If you are seeing \eOo etc in the application inside tmux, then it must be > turning on application keypad mode which makes tmux send these sequences. If > it isn't, you should see plain numbers 0-9. If you see \e[A then xterm must > be sending a normal Up key. > > > The tmux-256color terminfo entry doesn't include the keypad keys, so if the > application is relying on getting them from terminfo it won't work. > > > What do you see if you run "cat" then press Up, with numlock on, inside and > outside tmux? > > > What if you do "tput smkx" then do the same? > > > > > > > > > > On Sat, 22 Feb 2020, 22:30 , <[email protected]> wrote: > I just recently started working with tmux a bit. I'm currently specifically > working to get tintin++ working and have hit a few sticking points that I > assume are either related to the tmux config or the tmux/screen terminfo as > opposed to xterm. > > > > > > For profiles I have xterm-256color and tmux-256color. > > using ^v to look at what's being sent I see that: > > Directly in both terminals an up on the keypad with numlock off is sending > ^[[A > > > > However in tintin++ I see \eOx (I assume this is the same as ^[Ox ) when > directly from xterm and \e[A (which I assume is equivelant to ^[[A ). > > > > Is there any way for me to overcome this via tmux config/terminfo > configuration or does this more likely have something to do with the way > tintin++ is looking at the TERM variable or terminfo? > > > > I've not really ever done much with terminfo either so at a bit of a loss > currently. Thank you for any help! > > > > -- > > You received this message because you are subscribed to the Google Groups > "tmux-users" group. > > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > > To view this discussion on the web, visit > https://groups.google.com/d/msgid/tmux-users/059557af-8346-4793-b901-19a025ac79e1%40googlegroups.com. -- You received this message because you are subscribed to the Google Groups "tmux-users" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web, visit https://groups.google.com/d/msgid/tmux-users/7c079ff0-5e3e-4bb2-94f9-62da1b7d4738%40googlegroups.com.
