1. 11
  1.  

  2. 2

    sessions should be nested with care

    one of the funniest error message imho

    1. 1

      This seems a lot of effort. screen can do this simply by chaining the keys, e.g. an extra ‘a’ for commands to nested screen sessions, i.e. ‘^a-a-c’ to create a tab in the nested screen. Doesn’t require changing any settings locally or remote.

      1. 4

        The issue here is what to do with keys that do not need to be prefixed. If you have non-prefixed keybindings, then the outer tmux will always grab them unless told not to. That’s what this article shares: a way to tell TMUX to behave.

        1. 1

          Yeah, this is the tricky bit as I understood it too.

        2. 3

          Tmux of course can do that, too.

          1. 1

            That is exactly what I do in tmux.

          2. 1

            That’s cool, I suppose, but I always found it good enough to use a custom prefix on my local Tmux (Control-j), and leave the remote tmux the default. Therefore, it’s (Control-b) to do stuff on the inner, and (Control-j) to do stuff on the outer. Plus, I don’t have to replace the tmux conf on remote systems - I mostly connect to any one of dozens/hundreds of dynamically started and stopped systems, and usually only once or twice in a row.