That looks OK but if the terminal is sending \033OA even after smkx, tmux won't be able to send \033Ox and friends because \033OA is a cursor key sequence not a keypad key.
But it is mysterious that tt++ is able to get it to send keypad sequences unless it is ignoring smkx and sending something else. Can you run tt++ inside script, outside tmux? Just start it, press a key to make sure you get \033Ox or whatever then quit it and exit script and send me the typescript file. On Sun, 23 Feb 2020, 16:05 , <[email protected]> wrote: > both output ^[[?1h^[= > version 2.6 > > I should probably also mention I'm using WSL with mintty so it's not > actual xterm. Not sure if this could be a factor or not. > > > > On Sunday, February 23, 2020 at 2:51:29 AM UTC-5, Nicholas Marriott wrote: > > Hmm that is very strange. What does "tput smkx|cat -v" show inside and > outside tmux? > > > > > > What tmux version are you using? > > > > > > On Sun, 23 Feb 2020, 07:46 , <[email protected]> wrote: > > I may have misspoke. In tintin++ I want \eOx which is sent without tmux > but not with. However this doesn't match anything in either set of cat > output but I'm obviously not super familiar with escape codes so my > apologies if I'm still not being very clear. > > > > > > > > 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/d5f24621-0e9d-4e6f-80ba-6295d41ab080%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/51bd5348-0747-4574-a7a6-3314c525897b%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/CAEdLfcF6J05Jtf1_VtHToYRGw4Zht2nm47i3EBxsVsjsvSfRGA%40mail.gmail.com.
