-# created. Doing it after a window is created allows you to move a
-# window into the split that only has 1 window, whereas the other way
-# doesn't. For my use cases, I think I don't really want to move it into
-# the split if it is a tabbed split.
+# created.
+#
+# * Doing it after a window is created allows you to move a window into
+# the split that only has 1 window, whereas the other way doesn't. For
+# my use cases, I think I don't really want to move it into the split if
+# it is a tabbed split. upon further reflection, I've determined that
+# single window containers are inherently confusing because they tend to
+# exist and get nested at unexpected times and then it is unclear how to
+# get rid of them and what is going on and the benefit is generally not
+# worth it. This command helps identify single window containers during
+# testing: /a/opt/i3ipc-python/examples/i3-debug-console.py
+#
+# * Doing it just before a windows is created, you need to call this
+# script, which means wrapping launch of a program, which I have no way
+# to do for all cases, I just do it for the common programs I have bound
+# to keys in i3.
+#
+# * Doing it after a window is created also leaves that split behind if
+# the window is closed. I partially deal with that below.