<strong>swallowed</strong> by the placeholder container, hence the term.</p></div>\r
<div class="paragraph"><p>Note: Swallowing windows into unsatisfied placeholder windows takes precedence\r
over\r
-<a href="http://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces">assignment\r
+<a href="https://i3wm.org/docs/userguide.html#_automatically_putting_clients_on_specific_workspaces">assignment\r
rules</a>. For example, if you assign all Emacs windows to workspace 1 in your i3\r
configuration file, but there is a placeholder window on workspace 2 which\r
matches Emacs as well, your newly started Emacs window will end up in the\r
</a>\r
</span></p></div>\r
<div class="paragraph"><p>The structure of this JSON file looks a lot like the <tt>TREE</tt> reply, see\r
-<a href="http://build.i3wm.org/docs/ipc.html#_tree_reply">http://build.i3wm.org/docs/ipc.html#_tree_reply</a> for documentation on that. Some\r
+<a href="https://build.i3wm.org/docs/ipc.html#_tree_reply">https://build.i3wm.org/docs/ipc.html#_tree_reply</a> for documentation on that. Some\r
properties are excluded because they are not relevant when restoring a layout.</p></div>\r
<div class="paragraph"><p>Most importantly, look at the "swallows" section of each window. This is where\r
you need to be more or less specific. As an example, remember the section about\r
easier. In case you are writing a more elaborate tool for manipulating these\r
layouts, you can either use a JSON parser that supports these deviations (for\r
example libyajl), transform the layout file to a JSON-conforming file, or\r
-<a href="http://cr.i3wm.org/">submit a patch</a> to make <tt>i3-save-tree(1)</tt> optionally\r
-output standard-conforming JSON.</p></div>\r
+<a href="https://github.com/i3/i3/blob/next/.github/CONTRIBUTING.md">submit a patch</a>\r
+to make <tt>i3-save-tree(1)</tt> optionally output standard-conforming JSON.</p></div>\r
</div>\r
</div>\r
</div>\r