“normal” state will also be set and reset by interactive or full-screen programs (e.g. This is not a very good workaround, however, because the “application” vs.

This happens because smkx sends a sequence to tmux that causes it to send smkx to the client (which switches the client into “application cursor keys” mode, which sends sequences for Home and End that tmux will be able to match against the sequences from khome and kend). As long as that pane is active, tmux should recognize Home and End. There is a kind of loop-hole here that you can use to verify that this is happening: run tput smkx (or start Emacs or Vim) in your active pane. This incompatibility with xterm-style terminals results in the key not being recognized properly 2. This ends up meaning that tmux will not recognize End because the terminal sends the “normal cursor keys” sequence but tmux only knows about the “application cursor keys” sequence (from kend).īasically, tmux seems to expect that Home and End are not affected by the cursor key mode. By default, tmux switches the client terminal to “normal cursor keys” mode 1. Versions of tmux prior to 1.8 only recognize End when sees the sequence provided in the kend capability of your attached terminal’s terminfo entry (as specified by TERM when you attach to a tmux session). The rest of this post describes a way to get these keys working work tmux versions prior to 1.8. no need for the terminal-overrides hack described below). Tmux 1.8 recognizes both of these sequences by default, so you should not need to do anything special have tmux 1.8 reliably recognize xterm-style Home and End sequences (i.e. The sequence for End ends with F, so it is ^[[F under “normal cursor keys” mode and ^[OF under “application cursor keys” mode.

In “normal cursor keys” mode, the sequences start with ^[[ (ESC [) in “application cursor keys” mode, the sequences start with ^[O (ESC O). Xterm-style terminals send two different sequences for each of Up, Down, Right, Left, Home, and End.

How to create an end key on mac