<h1>i3 User’s Guide</h1>\r
<span id="author">Michael Stapelberg</span><br />\r
<span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />\r
-<span id="revdate">March 2013</span>\r
<div id="toc">
<div id="toctitle">Table of Contents</div>
<noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
<h2 id="_default_keybindings">1. Default keybindings</h2>\r
<div class="sectionbody">\r
<div class="paragraph"><p>For the "too long; didn’t read" people, here is an overview of the default\r
-keybindings (click to see the full size image):</p></div>\r
+keybindings (click to see the full-size image):</p></div>\r
<div class="paragraph"><p><strong>Keys to use with $mod (Alt):</strong></p></div>\r
<div class="paragraph"><p><span class="image">\r
<a class="image" href="keyboard-layer1.png">\r
<div class="sectionbody">\r
<div class="paragraph"><p>Throughout this guide, the keyword <tt>$mod</tt> will be used to refer to the\r
configured modifier. This is the Alt key (<tt>Mod1</tt>) by default, with the Windows\r
-key (<tt>Mod4</tt>) being a popular alternative.</p></div>\r
+key (<tt>Mod4</tt>) being a popular alternative that largely prevents conflicts with\r
+application-defined shortcuts.</p></div>\r
<div class="sect2">\r
<h3 id="_opening_terminals_and_moving_around">2.1. Opening terminals and moving around</h3>\r
<div class="paragraph"><p>One very basic operation is opening a new terminal. By default, the keybinding\r
out to be complicated to use (snapping), understand and implement.</p></div>\r
<div class="sect2">\r
<h3 id="_the_tree_consists_of_containers">3.1. The tree consists of Containers</h3>\r
-<div class="paragraph"><p>The building blocks of our tree are so called <tt>Containers</tt>. A <tt>Container</tt> can\r
+<div class="paragraph"><p>The building blocks of our tree are so-called <tt>Containers</tt>. A <tt>Container</tt> can\r
host a window (meaning an X11 window, one that you can actually see and use,\r
like a browser). Alternatively, it could contain one or more <tt>Containers</tt>. A\r
simple example is the workspace: When you start i3 with a single monitor, a\r
<div class="sect2">\r
<h3 id="floating_modifier">4.6. The floating modifier</h3>\r
<div class="paragraph"><p>To move floating windows with your mouse, you can either grab their titlebar\r
-or configure the so called floating modifier which you can then press and\r
+or configure the so-called floating modifier which you can then press and\r
click anywhere in the window itself to move it. The most common setup is to\r
use the same key you use for managing windows (Mod1 for example). Then\r
you can press Mod1, click into a window using your left mouse button, and drag\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_border_style_for_new_windows">4.10. Border style for new windows</h3>\r
+<h3 id="_default_border_style_for_new_windows">4.10. Default border style for new windows</h3>\r
<div class="paragraph"><p>This option determines which border style new windows will have. The default is\r
-<tt>normal</tt>. Note that new_float applies only to windows which are starting out as\r
+<tt>normal</tt>. Note that default_floating_border applies only to windows which are starting out as\r
floating windows, e.g., dialog windows, but not windows that are floated later on.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>new_window normal|none|pixel\r
-new_window normal|pixel <px>\r
-new_float normal|none|pixel\r
-new_float normal|pixel <px></tt></pre>\r
+<pre><tt>default_border normal|none|pixel\r
+default_border normal|pixel <px>\r
+default_floating_border normal|none|pixel\r
+default_floating_border normal|pixel <px></tt></pre>\r
</div></div>\r
+<div class="paragraph"><p>Please note that <tt>new_window</tt> and <tt>new_float</tt> have been deprecated in favor of the above options\r
+and will be removed in a future release. We strongly recommend using the new options instead.</p></div>\r
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>new_window pixel</tt></pre>\r
+<pre><tt>default_border pixel</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>The "normal" and "pixel" border styles support an optional border width in\r
pixels:</p></div>\r
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt># The same as new_window none\r
-new_window pixel 0\r
+<pre><tt># The same as default_border none\r
+default_border pixel 0\r
\r
# A 3 px border\r
-new_window pixel 3</tt></pre>\r
+default_border pixel 3</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
title change. As i3 will get the title as soon as the application maps the\r
window (mapping means actually displaying it on the screen), you’d need to have\r
to match on <em>Firefox</em> in this case.</p></div>\r
+<div class="paragraph"><p>You can also assign a window to show up on a specific output. You can use RandR\r
+names such as <tt>VGA1</tt> or names relative to the output with the currently focused\r
+workspace such as <tt>left</tt> and <tt>down</tt>.</p></div>\r
<div class="paragraph"><p>Assignments are processed by i3 in the order in which they appear in the config\r
file. The first one which matches the window wins and later assignments are not\r
considered.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>assign <criteria> [→] [workspace] <workspace></tt></pre>\r
+<pre><tt>assign <criteria> [→] [workspace] [number] <workspace>\r
+assign <criteria> [→] output left|right|up|down|primary|<output></tt></pre>\r
</div></div>\r
<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
# Assignment to a named workspace\r
assign [class="^URxvt$"] → work\r
\r
+# Assign to the workspace with number 2, regardless of name\r
+assign [class="^URxvt$"] → number 2\r
+\r
+# You can also specify a number + name. If the workspace with number 2 exists, assign will skip the text part.\r
+assign [class="^URxvt$"] → number "2: work"\r
+\r
# Start urxvt -name irssi\r
-assign [class="^URxvt$" instance="^irssi$"] → 3</tt></pre>\r
+assign [class="^URxvt$" instance="^irssi$"] → 3\r
+\r
+# Assign urxvt to the output right of the current one\r
+assign [class="^URxvt$"] → output right\r
+\r
+# Assign urxvt to the primary output\r
+assign [class="^URxvt$"] → output primary</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>Note that you might not have a primary output configured yet. To do so, run:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>xrandr --output <output> --primary</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>Note that the arrow is not required, it just looks good :-). If you decide to\r
+<div class="paragraph"><p>Also, the arrow is not required, it just looks good :-). If you decide to\r
use it, it has to be a UTF-8 encoded arrow, not <tt>-></tt> or something like that.</p></div>\r
<div class="paragraph"><p>To get the class and instance, you can use <tt>xprop</tt>. After clicking on the\r
window, you will see the following output:</p></div>\r
<div class="paragraph"><p>The first part of the WM_CLASS is the instance ("irssi" in this example), the\r
second part is the class ("URxvt" in this example).</p></div>\r
<div class="paragraph"><p>Should you have any problems with assignments, make sure to check the i3\r
-logfile first (see <a href="http://i3wm.org/docs/debugging.html">http://i3wm.org/docs/debugging.html</a>). It includes more\r
+logfile first (see <a href="https://i3wm.org/docs/debugging.html">https://i3wm.org/docs/debugging.html</a>). It includes more\r
details about the matching process and the window’s actual class, instance and\r
title when starting up.</p></div>\r
<div class="paragraph"><p>Note that if you want to start an application just once on a specific\r
<div class="paragraph"><p>The <em>output</em> is the name of the RandR output you attach your screen to. On a\r
laptop, you might have VGA1 and LVDS1 as output names. You can see the\r
available outputs by running <tt>xrandr --current</tt>.</p></div>\r
+<div class="paragraph"><p>If your X server supports RandR 1.5 or newer, i3 will use RandR monitor objects\r
+instead of output objects. Run <tt>xrandr --listmonitors</tt> to see a list. Usually,\r
+a monitor object contains exactly one output, and has the same name as the\r
+output; but should that not be the case, you may specify the name of either the\r
+monitor or the output in i3’s configuration. For example, the Dell UP2414Q uses\r
+two scalers internally, so its output names might be “DP1” and “DP2”, but the\r
+monitor name is “Dell UP2414Q”.</p></div>\r
+<div class="paragraph"><p>(Note that even if you specify the name of an output which doesn’t span the\r
+entire monitor, i3 will still use the entire area of the containing monitor\r
+rather than that of just the output’s.)</p></div>\r
<div class="paragraph"><p>If you use named workspaces, they must be quoted:</p></div>\r
<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
</div>\r
<div class="sect2">\r
<h3 id="_focus_wrapping">4.24. Focus wrapping</h3>\r
-<div class="paragraph"><p>When being in a tabbed or stacked container, the first container will be\r
-focused when you use <tt>focus down</tt> on the last container — the focus wraps. If\r
-however there is another stacked/tabbed container in that direction, focus will\r
-be set on that container. This is the default behavior so you can navigate to\r
-all your windows without having to use <tt>focus parent</tt>.</p></div>\r
+<div class="paragraph"><p>By default, when in a container with several windows or child containers, the\r
+opposite window will be focused when trying to move the focus over the edge of\r
+a container (and there are no other containers in that direction) — the focus\r
+wraps.</p></div>\r
+<div class="paragraph"><p>If desired, you can disable this behavior by setting the <tt>focus_wrapping</tt>\r
+configuration directive to the value <tt>no</tt>.</p></div>\r
+<div class="paragraph"><p>When enabled, focus wrapping does not occur by default if there is another\r
+window or container in the specified direction, and focus will instead be set\r
+on that window or container. This is the default behavior so you can navigate\r
+to all your windows without having to use <tt>focus parent</tt>.</p></div>\r
<div class="paragraph"><p>If you want the focus to <strong>always</strong> wrap and you are aware of using <tt>focus\r
-parent</tt> to switch to different containers, you can use the\r
-<tt>force_focus_wrapping</tt> configuration directive. After enabling it, the focus\r
-will always wrap.</p></div>\r
+parent</tt> to switch to different containers, you can instead set <tt>focus_wrapping</tt>\r
+to the value <tt>force</tt>.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>force_focus_wrapping yes|no</tt></pre>\r
+<pre><tt>focus_wrapping yes|no|force\r
+\r
+# Legacy syntax, equivalent to "focus_wrapping force"\r
+force_focus_wrapping yes</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>force_focus_wrapping yes</tt></pre>\r
+<pre><tt># Disable focus wrapping\r
+focus_wrapping no\r
+\r
+# Force focus wrapping\r
+focus_wrapping force</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_forcing_xinerama">4.25. Forcing Xinerama</h3>\r
-<div class="paragraph"><p>As explained in-depth in <a href="http://i3wm.org/docs/multi-monitor.html">http://i3wm.org/docs/multi-monitor.html</a>, some X11\r
+<div class="paragraph"><p>As explained in-depth in <a href="https://i3wm.org/docs/multi-monitor.html">https://i3wm.org/docs/multi-monitor.html</a>, some X11\r
video drivers (especially the nVidia binary driver) only provide support for\r
Xinerama instead of RandR. In such a situation, i3 must be told to use the\r
inferior Xinerama API explicitly and therefore don’t provide support for\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>bindsym button<n> <command></tt></pre>\r
+<pre><tt>bindsym [--release] button<n> <command></tt></pre>\r
</div></div>\r
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<pre><tt>bar {\r
# disable clicking on workspace buttons\r
bindsym button1 nop\r
+ # Take a screenshot by right clicking on the bar\r
+ bindsym --release button3 exec --no-startup-id import /tmp/latest-screenshot.png\r
# execute custom script when scrolling downwards\r
bindsym button5 exec ~/.i3/scripts/custom_wheel_down\r
}</tt></pre>\r
available:</p></div>\r
<div class="dlist"><dl>\r
<dt class="hdlist1">\r
+<criteria>\r
+</dt>\r
+<dd>\r
+<p>\r
+ Sets focus to the container that matches the specified criteria.\r
+ See <a href="#command_criteria">[command_criteria]</a>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
left|right|up|down\r
</dt>\r
<dd>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>focus left|right|down|up\r
+<pre><tt><criteria> focus\r
+focus left|right|down|up\r
focus parent|child|floating|tiling|mode_toggle\r
focus output left|right|up|down|primary|<output></tt></pre>\r
</div></div>\r
<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt># Focus container on the left, bottom, top, right\r
+<pre><tt># Focus firefox\r
+bindsym $mod+F1 [class="Firefox"] focus\r
+\r
+# Focus container on the left, bottom, top, right\r
bindsym $mod+j focus left\r
bindsym $mod+k focus down\r
bindsym $mod+l focus up\r
# Focus the primary output\r
bindsym $mod+x focus output primary</tt></pre>\r
</div></div>\r
+<div class="paragraph"><p>Note that you might not have a primary output configured yet. To do so, run:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>Note that you might not have a primary output configured yet. To do so, run:</tt></pre>\r
+<pre><tt>xrandr --output <output> --primary</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>xrandr --output <output> --primary</p></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_moving_containers">6.5. Moving containers</h3>\r
+<div class="paragraph"><p>Use the <tt>move</tt> command to move a container.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>=== Moving containers\r
-\r
-Use the +move+ command to move a container.\r
-\r
-*Syntax*:</tt></pre>\r
-</div></div>\r
-<div class="paragraph"><p># Moves the container into the given direction.\r
+<pre><tt># Moves the container into the given direction.\r
# The optional pixel argument specifies how far the\r
# container should be moved if it is floating and\r
# defaults to 10 pixels.\r
-move <left|right|down|up> [<px> px]</p></div>\r
-<div class="paragraph"><p># Moves the container either to a specific location\r
-# or to the center of the screen. If <em>absolute</em> is\r
+move <left|right|down|up> [<px> px]\r
+\r
+# Moves the container either to a specific location\r
+# or to the center of the screen. If 'absolute' is\r
# used, it is moved to the center of all outputs.\r
move [absolute] position <pos_x> [px] <pos_y> [px]\r
-move [absolute] position center</p></div>\r
-<div class="paragraph"><p># Moves the container to the current position of the\r
+move [absolute] position center\r
+\r
+# Moves the container to the current position of the\r
# mouse cursor. Only affects floating containers.\r
-move position mouse</p></div>\r
+move position mouse</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>*Examples*:</tt></pre>\r
-</div></div>\r
-<div class="paragraph"><p># Move container to the left, bottom, top, right\r
+<pre><tt># Move container to the left, bottom, top, right\r
bindsym $mod+j move left\r
bindsym $mod+k move down\r
bindsym $mod+l move up\r
-bindsym $mod+semicolon move right</p></div>\r
-<div class="paragraph"><p># Move container, but make floating containers\r
+bindsym $mod+semicolon move right\r
+\r
+# Move container, but make floating containers\r
# move more than the default\r
-bindsym $mod+j move left 20 px</p></div>\r
-<div class="paragraph"><p># Move floating container to the center of all outputs\r
-bindsym $mod+c move absolute position center</p></div>\r
-<div class="paragraph"><p># Move container to the current position of the cursor\r
-bindsym $mod+m move position mouse</p></div>\r
-<div class="listingblock">\r
-<div class="content">\r
-<pre><tt>=== Swapping containers\r
+bindsym $mod+j move left 20 px\r
\r
-Two containers can be swapped (i.e., move to each other's position) by using\r
-the +swap+ command. They will assume the position and geometry of the container\r
-they are swapped with.\r
+# Move floating container to the center of all outputs\r
+bindsym $mod+c move absolute position center\r
\r
-The first container to participate in the swapping can be selected through the\r
+# Move container to the current position of the cursor\r
+bindsym $mod+m move position mouse</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_swapping_containers">6.6. Swapping containers</h3>\r
+<div class="paragraph"><p>Two containers can be swapped (i.e., move to each other’s position) by using\r
+the <tt>swap</tt> command. They will assume the position and geometry of the container\r
+they are swapped with.</p></div>\r
+<div class="paragraph"><p>The first container to participate in the swapping can be selected through the\r
normal command criteria process with the focused window being the usual\r
fallback if no criteria are specified. The second container can be selected\r
-using one of the following methods:\r
-\r
-+id+:: The X11 window ID of a client window.\r
-+con_id+:: The i3 container ID of a container.\r
-+mark+:: A container with the specified mark, see <<vim_like_marks>>.\r
-\r
-Note that swapping does not work with all containers. Most notably, swapping\r
+using one of the following methods:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+<tt>id</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+The X11 window ID of a client window.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+<tt>con_id</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+The i3 container ID of a container.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+<tt>mark</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+A container with the specified mark, see <a href="#vim_like_marks">[vim_like_marks]</a>.\r
+</p>\r
+</dd>\r
+</dl></div>\r
+<div class="paragraph"><p>Note that swapping does not work with all containers. Most notably, swapping\r
floating containers or containers that have a parent-child relationship to one\r
-another does not work.\r
-\r
-*Syntax*:</tt></pre>\r
+another does not work.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>swap container with id|con_id|mark <arg></tt></pre>\r
</div></div>\r
-</div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="_swap_container_with_id_con_id_mark_lt_arg_gt">7. swap container with id|con_id|mark <arg></h2>\r
-<div class="sectionbody">\r
<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
# Swaps container marked »A« and »B«\r
[con_mark="^A$"] swap container with mark B</tt></pre>\r
</div></div>\r
+</div>\r
<div class="sect2">\r
-<h3 id="_sticky_floating_windows">7.1. Sticky floating windows</h3>\r
+<h3 id="_sticky_floating_windows">6.7. Sticky floating windows</h3>\r
<div class="paragraph"><p>If you want a window to stick to the glass, i.e., have it stay on screen even\r
if you switch to another workspace, you can use the <tt>sticky</tt> command. For\r
example, this can be useful for notepads, a media player or a video chat\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_changing_named_workspaces_moving_to_workspaces">7.2. Changing (named) workspaces/moving to workspaces</h3>\r
+<h3 id="_changing_named_workspaces_moving_to_workspaces">6.8. Changing (named) workspaces/moving to workspaces</h3>\r
<div class="paragraph"><p>To change to a specific workspace, use the <tt>workspace</tt> command, followed by the\r
number or name of the workspace. Pass the optional flag\r
<tt>--no-auto-back-and-forth</tt> to disable <a href="#back_and_forth">[back_and_forth]</a> for this specific call\r
bindsym $mod+F1 [class="Firefox"] move workspace current</tt></pre>\r
</div></div>\r
<div class="sect3">\r
-<h4 id="_named_workspaces">7.2.1. Named workspaces</h4>\r
+<h4 id="_named_workspaces">6.8.1. Named workspaces</h4>\r
<div class="paragraph"><p>Workspaces are identified by their name. So, instead of using numbers in the\r
workspace command, you can use an arbitrary name:</p></div>\r
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
specify a default name if there’s currently no workspace starting with a "1".</p></div>\r
</div>\r
<div class="sect3">\r
-<h4 id="_renaming_workspaces">7.2.2. Renaming workspaces</h4>\r
+<h4 id="_renaming_workspaces">6.8.2. Renaming workspaces</h4>\r
<div class="paragraph"><p>You can rename workspaces. This might be useful to start with the default\r
numbered workspaces, do your work, and rename the workspaces afterwards to\r
reflect what’s actually on them. You can also omit the old name to rename\r
</div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_moving_workspaces_to_a_different_screen">7.3. Moving workspaces to a different screen</h3>\r
+<h3 id="_moving_workspaces_to_a_different_screen">6.9. Moving workspaces to a different screen</h3>\r
<div class="paragraph"><p>See <a href="#move_to_outputs">[move_to_outputs]</a> for how to move a container/workspace to a different\r
RandR output.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_moving_containers_workspaces_to_randr_outputs">7.4. Moving containers/workspaces to RandR outputs</h3>\r
+<h3 id="_moving_containers_workspaces_to_randr_outputs">6.10. Moving containers/workspaces to RandR outputs</h3>\r
<div class="paragraph"><p>To move a container to another RandR output (addressed by names like <tt>LVDS1</tt> or\r
<tt>VGA1</tt>) or to a RandR output identified by a specific direction (like <tt>left</tt>,\r
<tt>right</tt>, <tt>up</tt> or <tt>down</tt>), there are two commands:</p></div>\r
# Put this window on the primary output.\r
bindsym $mod+x move container to output primary</tt></pre>\r
</div></div>\r
+<div class="paragraph"><p>Note that you might not have a primary output configured yet. To do so, run:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>Note that you might not have a primary output configured yet. To do so, run:</tt></pre>\r
+<pre><tt>xrandr --output <output> --primary</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>xrandr --output <output> --primary</p></div>\r
-<div class="listingblock">\r
-<div class="content">\r
-<pre><tt>=== Moving containers/windows to marks\r
-\r
-To move a container to another container with a specific mark (see <<vim_like_marks>>),\r
-you can use the following command.\r
-\r
-The window will be moved right after the marked container in the tree, i.e., it ends up\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_moving_containers_windows_to_marks">6.11. Moving containers/windows to marks</h3>\r
+<div class="paragraph"><p>To move a container to another container with a specific mark (see <a href="#vim_like_marks">[vim_like_marks]</a>),\r
+you can use the following command.</p></div>\r
+<div class="paragraph"><p>The window will be moved right after the marked container in the tree, i.e., it ends up\r
in the same position as if you had opened a new window when the marked container was\r
focused. If the mark is on a split container, the window will appear as a new child\r
-after the currently focused child within that container.\r
-\r
-*Syntax*:</tt></pre>\r
+after the currently focused child within that container.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>move window|container to mark <mark></tt></pre>\r
</div></div>\r
-</div>\r
-</div>\r
-</div>\r
-<div class="sect1">\r
-<h2 id="_move_window_container_to_mark_lt_mark_gt">8. move window|container to mark <mark></h2>\r
-<div class="sectionbody">\r
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>for_window [instance="tabme"] move window to mark target</tt></pre>\r
</div></div>\r
+</div>\r
<div class="sect2">\r
-<h3 id="resizingconfig">8.1. Resizing containers/windows</h3>\r
+<h3 id="resizingconfig">6.12. Resizing containers/windows</h3>\r
<div class="paragraph"><p>If you want to resize containers/windows using your keyboard, you can use the\r
<tt>resize</tt> command:</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>resize grow|shrink <direction> [<px> px [or <ppt> ppt]]\r
-resize set <width> [px] <height> [px]</tt></pre>\r
+resize set <width> [px | ppt] <height> [px | ppt]</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Direction can either be one of <tt>up</tt>, <tt>down</tt>, <tt>left</tt> or <tt>right</tt>. Or you can be\r
less specific and use <tt>width</tt> or <tt>height</tt>, in which case i3 will take/give\r
how many pixels a <strong>floating container</strong> should be grown or shrunk (the default\r
is 10 pixels). The ppt argument means percentage points and specifies by how\r
many percentage points a <strong>tiling container</strong> should be grown or shrunk (the\r
-default is 10 percentage points). Note that <tt>resize set</tt> will only work for\r
-floating containers.</p></div>\r
+default is 10 percentage points).</p></div>\r
+<div class="paragraph"><p>Notes about <tt>resize set</tt>: a value of 0 for <width> or <height> means "do\r
+not resize in this direction", and resizing a tiling container by <tt>px</tt> is not\r
+implemented.</p></div>\r
<div class="paragraph"><p>It is recommended to define bindings for resizing in a dedicated binding mode.\r
See <a href="#binding_modes">[binding_modes]</a> and the example in the i3\r
<a href="https://github.com/i3/i3/blob/next/etc/config.keycodes">default config</a> for more\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_jumping_to_specific_windows">8.2. Jumping to specific windows</h3>\r
+<h3 id="_jumping_to_specific_windows">6.13. Jumping to specific windows</h3>\r
<div class="paragraph"><p>Often when in a multi-monitor environment, you want to quickly jump to a\r
specific window. For example, while working on workspace 3 you may want to\r
jump to your mail client to email your boss that you’ve achieved some\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="vim_like_marks">8.3. VIM-like marks (mark/goto)</h3>\r
+<h3 id="vim_like_marks">6.14. VIM-like marks (mark/goto)</h3>\r
<div class="paragraph"><p>This feature is like the jump feature: It allows you to directly jump to a\r
specific window (this means switching to the appropriate workspace and setting\r
focus to the windows). However, you can directly mark a specific window with\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="pango_markup">8.4. Window title format</h3>\r
+<h3 id="pango_markup">6.15. Window title format</h3>\r
<div class="paragraph"><p>By default, i3 will simply print the X11 window title. Using <tt>title_format</tt>,\r
this can be customized by setting the format to the desired output. This\r
directive supports\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_changing_border_style">8.5. Changing border style</h3>\r
+<h3 id="_changing_border_style">6.16. Changing border style</h3>\r
<div class="paragraph"><p>To change the border of the current client, you can use <tt>border normal</tt> to use the normal\r
border (including window title), <tt>border pixel 1</tt> to use a 1-pixel border (no window title)\r
and <tt>border none</tt> to make the client borderless.</p></div>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="shmlog">8.6. Enabling shared memory logging</h3>\r
-<div class="paragraph"><p>As described in <a href="http://i3wm.org/docs/debugging.html">http://i3wm.org/docs/debugging.html</a>, i3 can log to a shared\r
+<h3 id="shmlog">6.17. Enabling shared memory logging</h3>\r
+<div class="paragraph"><p>As described in <a href="https://i3wm.org/docs/debugging.html">https://i3wm.org/docs/debugging.html</a>, i3 can log to a shared\r
memory buffer, which you can dump using <tt>i3-dump-log</tt>. The <tt>shmlog</tt> command\r
allows you to enable or disable the shared memory logging at runtime.</p></div>\r
<div class="paragraph"><p>Note that when using <tt>shmlog <size_in_bytes></tt>, the current log will be\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_enabling_debug_logging">8.7. Enabling debug logging</h3>\r
+<h3 id="_enabling_debug_logging">6.18. Enabling debug logging</h3>\r
<div class="paragraph"><p>The <tt>debuglog</tt> command allows you to enable or disable debug logging at\r
runtime. Debug logging is much more verbose than non-debug logging. This\r
command does not activate shared memory logging (shmlog), and as such is most\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_reloading_restarting_exiting">8.8. Reloading/Restarting/Exiting</h3>\r
+<h3 id="_reloading_restarting_exiting">6.19. Reloading/Restarting/Exiting</h3>\r
<div class="paragraph"><p>You can make i3 reload its configuration file with <tt>reload</tt>. You can also\r
restart i3 inplace with the <tt>restart</tt> command to get it out of some weird state\r
(if that should ever happen) or to perform an upgrade without having to restart\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_scratchpad">8.9. Scratchpad</h3>\r
+<h3 id="_scratchpad">6.20. Scratchpad</h3>\r
<div class="paragraph"><p>There are two commands to use any existing window as scratchpad window. <tt>move\r
scratchpad</tt> will move a window to the scratchpad workspace. This will make it\r
invisible until you show it again. There is no way to open that workspace.\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_nop">8.10. Nop</h3>\r
+<h3 id="_nop">6.21. Nop</h3>\r
<div class="paragraph"><p>There is a no operation command <tt>nop</tt> which allows you to override default\r
behavior. This can be useful for, e.g., disabling a focus change on clicks with\r
the middle mouse button.</p></div>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_i3bar_control">8.11. i3bar control</h3>\r
+<h3 id="_i3bar_control">6.22. i3bar control</h3>\r
<div class="paragraph"><p>There are two options in the configuration of each i3bar instance that can be\r
changed during runtime by invoking a command through i3. The commands <tt>bar\r
hidden_state</tt> and <tt>bar mode</tt> allow setting the current hidden_state\r
</div>\r
</div>\r
<div class="sect1">\r
-<h2 id="multi_monitor">9. Multiple monitors</h2>\r
+<h2 id="multi_monitor">7. Multiple monitors</h2>\r
<div class="sectionbody">\r
<div class="paragraph"><p>As you can see in the goal list on the website, i3 was specifically developed\r
with support for multiple monitors in mind. This section will explain how to\r
screens, you can have the "traditional" approach of having X workspaces per\r
screen by changing your configuration (using modes, for example).</p></div>\r
<div class="sect2">\r
-<h3 id="_configuring_your_monitors">9.1. Configuring your monitors</h3>\r
+<h3 id="_configuring_your_monitors">7.1. Configuring your monitors</h3>\r
<div class="paragraph"><p>To help you get going if you have never used multiple monitors before, here is\r
a short overview of the xrandr options which will probably be of interest to\r
you. It is always useful to get an overview of the current screen configuration.\r
<div class="paragraph"><p>See also <a href="#presentations">[presentations]</a> for more examples of multi-monitor setups.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_interesting_configuration_for_multi_monitor_environments">9.2. Interesting configuration for multi-monitor environments</h3>\r
+<h3 id="_interesting_configuration_for_multi_monitor_environments">7.2. Interesting configuration for multi-monitor environments</h3>\r
<div class="paragraph"><p>There are several things to configure in i3 which may be interesting if you\r
have more than one monitor:</p></div>\r
<div class="olist arabic"><ol class="arabic">\r
</div>\r
</div>\r
<div class="sect1">\r
-<h2 id="_i3_and_the_rest_of_your_software_world">10. i3 and the rest of your software world</h2>\r
+<h2 id="_i3_and_the_rest_of_your_software_world">8. i3 and the rest of your software world</h2>\r
<div class="sectionbody">\r
<div class="sect2">\r
-<h3 id="_displaying_a_status_line">10.1. Displaying a status line</h3>\r
+<h3 id="_displaying_a_status_line">8.1. Displaying a status line</h3>\r
<div class="paragraph"><p>A very common thing amongst users of exotic window managers is a status line at\r
some corner of the screen. It is an often superior replacement to the widget\r
approach you have in the task bar of a traditional desktop environment.</p></div>\r
see <a href="#i3bar_position">[i3bar_position]</a>.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="presentations">10.2. Giving presentations (multi-monitor)</h3>\r
+<h3 id="presentations">8.2. Giving presentations (multi-monitor)</h3>\r
<div class="paragraph"><p>When giving a presentation, you typically want the audience to see what you see\r
on your screen and then go through a series of slides (if the presentation is\r
simple). For more complex presentations, you might want to have some notes\r
which only you can see on your screen, while the audience can only see the\r
slides.</p></div>\r
<div class="sect3">\r
-<h4 id="_case_1_everybody_gets_the_same_output">10.2.1. Case 1: everybody gets the same output</h4>\r
+<h4 id="_case_1_everybody_gets_the_same_output">8.2.1. Case 1: everybody gets the same output</h4>\r
<div class="paragraph"><p>This is the simple case. You connect your computer to the video projector,\r
turn on both (computer and video projector) and configure your X server to\r
clone the internal flat panel of your computer to the video output:</p></div>\r
our example, this would be 1024x768 (my notebook has 1280x800).</p></div>\r
</div>\r
<div class="sect3">\r
-<h4 id="_case_2_you_can_see_more_than_your_audience">10.2.2. Case 2: you can see more than your audience</h4>\r
+<h4 id="_case_2_you_can_see_more_than_your_audience">8.2.2. Case 2: you can see more than your audience</h4>\r
<div class="paragraph"><p>This case is a bit harder. First of all, you should configure the VGA output\r
somewhere near your internal flat panel, say right of it:</p></div>\r
<div class="listingblock">\r
projects / i3 / i3.github.io / blobdiff