diff options
author | Nicholas Marriott <nicholas.marriott@gmail.com> | 2017-04-25 14:31:05 +0100 |
---|---|---|
committer | Nicholas Marriott <nicholas.marriott@gmail.com> | 2017-04-25 14:31:05 +0100 |
commit | accaff8ac0c73ed20ee01a98d863f4e63d7d40d4 (patch) | |
tree | 06923306bb473fa82244134b4e020549000cfd34 | |
parent | 45965fb020522896752d3d5e27dea2f062b45dba (diff) | |
download | rtmux-accaff8ac0c73ed20ee01a98d863f4e63d7d40d4.tar.gz rtmux-accaff8ac0c73ed20ee01a98d863f4e63d7d40d4.tar.bz2 rtmux-accaff8ac0c73ed20ee01a98d863f4e63d7d40d4.zip |
Remove stuff from TODO.
-rw-r--r-- | TODO | 24 |
1 files changed, 0 insertions, 24 deletions
@@ -120,27 +120,3 @@ * multiple hooks with the same name? * finish hooks for notifys * for session_closed, if no sessions at all, perhaps fake up a temporary one - -- current target resolution is still confusing and probably wrong: - * what if I - bind -n DoubleClick1Pane selectp -U\; resizep -Z - and click on a pane that isn't the active pane? It should make the - pane above the one I clicked on active and zoom it - * bind q select-pane -U\; resize-pane -Z should do the obvious - * bind q neww\; splitw as well - * should we always start with a "current target" and commands can - update it? - * a few cases: - 1) normal key bindings - fine, we always know the full target - but it is important that commands like neww and selectp - use the updated active window or pane; - 2) mouse key binding - same, but needs to be the mouse target; - 3) from a new client ("tmux whatever") - we may know the best - s,wl,wp from the pty, guess the client, or guess all if - we don't know; - 4) hooks - we may know or we may not; - 5) control mode - same as a key binding really, and not - specifying a target is stupid anyway; - 6) if-shell/run-shell - may be able to preserve its target, - else guess. - * of course -t and -s override the current target as now. |