#144 [REGRESSION] Shift-F1 through Shift-F8 no longer handled correctly by tmux 1.9

closed
nobody
None
2014-10-02
2014-07-31
Dustin Kirkland
No

There seems to be a regression with the release of tmux 1.9, which we are experiencing in Debian and Ubuntu 14.10 (utopic) systems which have merged the new tmux release.

Shift-F1 - Shift-F8 are no longer being handled properly by Tmux. A tilda, ~, is simply printed to the terminal, rather than the keypress being handled properly as defined in my ~/.tmuxrc with a bindkey -n S-F2 command, for example.

Commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09 looks suspect.

Discussion

  • rlblaster
    rlblaster
    2014-08-08

    Commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09 looks suspect.

    I don't think that commit affects this as it was committed after 1.9a
    was released.

    Shift-F1 - Shift-F8 are no longer being handled properly by Tmux. A
    tilda, ~, is simply printed to the terminal, rather than the keypress
    being handled properly as defined in my ~/.tmuxrc with a bindkey -n
    S-F2 command, for example.

    I can't reproduce this in my setup, binding S-F2 works for me in my
    xterm. On the other hand using terminal like urxvt it doesn't work
    because for some reason S-F1, S-F2 generate the same sequences as F11
    and F12 (and I get the ~ character in bash as described in your report).

    Which terminal are you using? What character sequences do you get when
    you run "cat" in the terminal (without tmux) and press S-F1?

    There seems to be a regression with the release of tmux 1.9, which we
    are experiencing in Debian and Ubuntu 14.10 (utopic) systems which
    have merged the new tmux release.

    Just to be sure: Have you tried both 1.8 and 1.9a in the same terminal?

    Thanks!

    --
    Balazs

     
    • On Fri, Aug 8, 2014 at 1:19 PM, rlblaster rlblaster@users.sf.net wrote:

      Commit 193b6bcf36dda3754c99beb0dcc3dfdfceebdb09 looks suspect.

      I don't think that commit affects this as it was committed after 1.9a
      was released.

      Shift-F1 - Shift-F8 are no longer being handled properly by Tmux. A
      tilda, ~, is simply printed to the terminal, rather than the keypress
      being handled properly as defined in my ~/.tmuxrc with a bindkey -n
      S-F2 command, for example.

      I can't reproduce this in my setup, binding S-F2 works for me in my
      xterm. On the other hand using terminal like urxvt it doesn't work
      because for some reason S-F1, S-F2 generate the same sequences as F11
      and F12 (and I get the ~ character in bash as described in your report).

      Which terminal are you using? What character sequences do you get when
      you run "cat" in the terminal (without tmux) and press S-F1?

      I'm using gnome-terminal in Ubuntu 14.404 LTS.

      <Shift-F1> through <Shift-F8>
      kirkland@x230:~$ cat >/dev/null
      ^[O1;2P
      ^[O1;2Q
      ^[O1;2R
      ^[O1;2S
      ^[[15;2~
      ^[[17;2~
      ^[[18;2~
      ^[[19;2~

      There seems to be a regression with the release of tmux 1.9, which we
      are experiencing in Debian and Ubuntu 14.10 (utopic) systems which
      have merged the new tmux release.

      Just to be sure: Have you tried both 1.8 and 1.9a in the same terminal?

      Yes, absolutely. 1.8 works perfectly fine. 1.9a does not.

      Actually, I've submitted a related patch a few years back, 2011-06-19.
      Is it possible this got dropped or reverted?

      https://sourceforge.net/p/tmux/mailman/tmux-users/thread/20110623100330.GA19031@yelena.nicm.ath.cx/

       
    • status: open --> closed