This idea (nested sessions) is fraught with too many problems to do it sanely;

for example, in order not to be annoying, previous-window would have to work
as expected (jump back to previous session) but what if you enter the same
session from different parent sessions? What is the previous window? It
would have to be tied to the client. There are other issues as well, and I
don't see it as terribly useful (you can bind a switch-client command to any
key anyway), so it is off the list.

1 files changed, 0 insertions, 2 deletions

diff --git a/TODO b/TODO
index 10ce8a82..37e5ed22 100644
--- a/TODO
+++ b/TODO
@@ -9,8 +9,6 @@
 - could use bsearch all over the place or get rid of smaller tables (clientmsg)
 - better errors when creating new windows/sessions (how?)
 - Implicitly add exec to the commands for new windows (switch to disable it)
-- nested sessions, ie session as window - moving to it moves into session
-  (remembering parent)
 - it would be nice to have multichar commands so you could have C-b K K for
   kill-window to limit accidental presses
 - status-fg/status-bg should be able to set attributes: bold, etc