+<div class="paragraph"><p>The bar at the bottom of your monitor is drawn by a separate process called\r
+i3bar. Having this part of "the i3 user interface" in a separate process has\r
+several advantages:</p></div>\r
+<div class="olist arabic"><ol class="arabic">\r
+<li>\r
+<p>\r
+It is a modular approach. If you don’t need a workspace bar at all, or if\r
+ you prefer a different one (dzen2, xmobar, maybe even gnome-panel?), you can\r
+ just remove the i3bar configuration and start your favorite bar instead.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+It follows the UNIX philosophy of "Make each program do one thing well".\r
+ While i3 manages your windows well, i3bar is good at displaying a bar on\r
+ each monitor (unless you configure it otherwise).\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
+It leads to two separate, clean codebases. If you want to understand i3, you\r
+ don’t need to bother with the details of i3bar and vice versa.\r
+</p>\r
+</li>\r
+</ol></div>\r
+<div class="paragraph"><p>That said, i3bar is configured in the same configuration file as i3. This is\r
+because it is tightly coupled with i3 (in contrary to i3lock or i3status which\r
+are useful for people using other window managers). Therefore, it makes no\r
+sense to use a different configuration place when we already have a good\r
+configuration infrastructure in place.</p></div>\r
+<div class="paragraph"><p>Configuring your workspace bar starts with opening a <tt>bar</tt> block. You can have\r
+multiple bar blocks to use different settings for different outputs (monitors):</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ status_command i3status\r
+}</tt></pre>\r
+</div></div>\r
+<div class="sect2">\r
+<h3 id="_i3bar_command">5.1. i3bar command</h3>\r
+<div class="paragraph"><p>By default i3 will just pass <tt>i3bar</tt> and let your shell handle the execution,\r
+searching your <tt>$PATH</tt> for a correct version.\r
+If you have a different <tt>i3bar</tt> somewhere or the binary is not in your <tt>$PATH</tt> you can\r
+tell i3 what to execute.</p></div>\r
+<div class="paragraph"><p>The specified command will be passed to <tt>sh -c</tt>, so you can use globbing and\r
+have to have correct quoting etc.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>i3bar_command <command></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ i3bar_command /home/user/bin/i3bar\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="status_command">5.2. Statusline command</h3>\r
+<div class="paragraph"><p>i3bar can run a program and display every line of its <tt>stdout</tt> output on the\r
+right hand side of the bar. This is useful to display system information like\r
+your current IP address, battery status or date/time.</p></div>\r
+<div class="paragraph"><p>The specified command will be passed to <tt>sh -c</tt>, so you can use globbing and\r
+have to have correct quoting etc. Note that for signal handling, depending on\r
+your shell (users of dash(1) are known to be affected), you have to use the\r
+shell’s exec command so that signals are passed to your program, not to the\r
+shell.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>status_command <command></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ status_command i3status --config ~/.i3status.conf\r
+\r
+ # For dash(1) users who want signal handling to work:\r
+ status_command exec ~/.bin/my_status_command\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_display_mode">5.3. Display mode</h3>\r
+<div class="paragraph"><p>You can either have i3bar be visible permanently at one edge of the screen\r
+(<tt>dock</tt> mode) or make it show up when you press your modifier key (<tt>hide</tt> mode).\r
+It is also possible to force i3bar to always stay hidden (<tt>invisible</tt>\r
+mode). The modifier key can be configured using the <tt>modifier</tt> option.</p></div>\r
+<div class="paragraph"><p>The mode option can be changed during runtime through the <tt>bar mode</tt> command.\r
+On reload the mode will be reverted to its configured value.</p></div>\r
+<div class="paragraph"><p>The hide mode maximizes screen space that can be used for actual windows. Also,\r
+i3bar sends the <tt>SIGSTOP</tt> and <tt>SIGCONT</tt> signals to the statusline process to\r
+save battery power.</p></div>\r
+<div class="paragraph"><p>Invisible mode allows to permanently maximize screen space, as the bar is never\r
+shown. Thus, you can configure i3bar to not disturb you by popping up because\r
+of an urgency hint or because the modifier key is pressed.</p></div>\r
+<div class="paragraph"><p>In order to control whether i3bar is hidden or shown in hide mode, there exists\r
+the hidden_state option, which has no effect in dock mode or invisible mode. It\r
+indicates the current hidden_state of the bar: (1) The bar acts like in normal\r
+hide mode, it is hidden and is only unhidden in case of urgency hints or by\r
+pressing the modifier key (<tt>hide</tt> state), or (2) it is drawn on top of the\r
+currently visible workspace (<tt>show</tt> state).</p></div>\r
+<div class="paragraph"><p>Like the mode, the hidden_state can also be controlled through i3, this can be\r
+done by using the <tt>bar hidden_state</tt> command.</p></div>\r
+<div class="paragraph"><p>The default mode is dock mode; in hide mode, the default modifier is Mod4 (usually\r
+the windows key). The default value for the hidden_state is hide.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>mode dock|hide|invisible\r
+hidden_state hide|show\r
+modifier <Modifier>|none</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ mode hide\r
+ hidden_state hide\r
+ modifier Mod1\r
+}</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>Available modifiers are Mod1-Mod5, Shift, Control (see <tt>xmodmap(1)</tt>). You can\r
+also use "none" if you don’t want any modifier to trigger this behavior.</p></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_mouse_button_commands">5.4. Mouse button commands</h3>\r
+<div class="paragraph"><p>Specifies a command to run when a button was pressed on i3bar to override the\r
+default behavior. This is useful, e.g., for disabling the scroll wheel action\r
+or running scripts that implement custom behavior for these buttons.</p></div>\r
+<div class="paragraph"><p>A button is always named <tt>button<n></tt>, where 1 to 5 are default buttons as follows and higher\r
+numbers can be special buttons on devices offering more buttons:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+button1\r
+</dt>\r
+<dd>\r
+<p>\r
+ Left mouse button.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+button2\r
+</dt>\r
+<dd>\r
+<p>\r
+ Middle mouse button.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+button3\r
+</dt>\r
+<dd>\r
+<p>\r
+ Right mouse button.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+button4\r
+</dt>\r
+<dd>\r
+<p>\r
+ Scroll wheel up.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+button5\r
+</dt>\r
+<dd>\r
+<p>\r
+ Scroll wheel down.\r
+</p>\r
+</dd>\r
+</dl></div>\r
+<div class="paragraph"><p>Please note that the old <tt>wheel_up_cmd</tt> and <tt>wheel_down_cmd</tt> commands are deprecated\r
+and will be removed in a future release. We strongly recommend using the more general\r
+<tt>bindsym</tt> with <tt>button4</tt> and <tt>button5</tt> instead.</p></div>\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
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ # disable clicking on workspace buttons\r
+ bindsym button1 nop\r
+ # execute custom script when scrolling downwards\r
+ bindsym button5 exec ~/.i3/scripts/custom_wheel_down\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_bar_id">5.5. Bar ID</h3>\r
+<div class="paragraph"><p>Specifies the bar ID for the configured bar instance. If this option is missing,\r
+the ID is set to <em>bar-x</em>, where x corresponds to the position of the embedding\r
+bar block in the config file (<em>bar-0</em>, <em>bar-1</em>, …).</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>id <bar_id></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ id bar-1\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="i3bar_position">5.6. Position</h3>\r
+<div class="paragraph"><p>This option determines in which edge of the screen i3bar should show up.</p></div>\r
+<div class="paragraph"><p>The default is bottom.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>position top|bottom</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ position top\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_output_s">5.7. Output(s)</h3>\r
+<div class="paragraph"><p>You can restrict i3bar to one or more outputs (monitors). The default is to\r
+handle all outputs. Restricting the outputs is useful for using different\r
+options for different outputs by using multiple <em>bar</em> blocks.</p></div>\r
+<div class="paragraph"><p>To make a particular i3bar instance handle multiple outputs, specify the output\r
+directive multiple times.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>output <output></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># big monitor: everything\r
+bar {\r
+ # The display is connected either via HDMI or via DisplayPort\r
+ output HDMI2\r
+ output DP2\r
+ status_command i3status\r
+}\r
+\r
+# laptop monitor: bright colors and i3status with less modules.\r
+bar {\r
+ output LVDS1\r
+ status_command i3status --config ~/.i3status-small.conf\r
+ colors {\r
+ background #000000\r
+ statusline #ffffff\r
+ }\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_tray_output">5.8. Tray output</h3>\r
+<div class="paragraph"><p>i3bar by default provides a system tray area where programs such as\r
+NetworkManager, VLC, Pidgin, etc. can place little icons.</p></div>\r
+<div class="paragraph"><p>You can configure on which output (monitor) the icons should be displayed or\r
+you can turn off the functionality entirely.</p></div>\r
+<div class="paragraph"><p>You can use mutliple <tt>tray_output</tt> directives in your config to specify a list\r
+of outputs on which you want the tray to appear. The first available output in\r
+that list as defined by the order of the directives will be used for the tray\r
+output.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>tray_output none|primary|<output></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># disable system tray\r
+bar {\r
+ tray_output none\r
+}\r
+\r
+# show tray icons on the primary monitor\r
+bar {\r
+ tray_output primary\r
+}\r
+\r
+# show tray icons on the big monitor\r
+bar {\r
+ tray_output HDMI2\r
+}</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 when you use multiple bar configuration blocks, either specify\r
+<tt>tray_output primary</tt> in all of them or explicitly specify <tt>tray_output none</tt>\r
+in bars which should not display the tray, otherwise the different instances\r
+might race each other in trying to display tray icons.</p></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_tray_padding">5.9. Tray padding</h3>\r
+<div class="paragraph"><p>The tray is shown on the right-hand side of the bar. By default, a padding of 2\r
+pixels is used for the upper, lower and right-hand side of the tray area and\r
+between the individual icons.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>tray_padding <px> [px]</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Obey Fitts's law\r
+tray_padding 0</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_font">5.10. Font</h3>\r
+<div class="paragraph"><p>Specifies the font to be used in the bar. See <a href="#fonts">[fonts]</a>.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>font <font></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1\r
+ font pango:DejaVu Sans Mono 10\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_custom_separator_symbol">5.11. Custom separator symbol</h3>\r
+<div class="paragraph"><p>Specifies a custom symbol to be used for the separator as opposed to the vertical,\r
+one pixel thick separator.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>separator_symbol <symbol></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ separator_symbol ":|:"\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_workspace_buttons">5.12. Workspace buttons</h3>\r
+<div class="paragraph"><p>Specifies whether workspace buttons should be shown or not. This is useful if\r
+you want to display a statusline-only bar containing additional information.</p></div>\r
+<div class="paragraph"><p>The default is to show workspace buttons.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>workspace_buttons yes|no</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ workspace_buttons no\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_strip_workspace_numbers">5.13. Strip workspace numbers</h3>\r
+<div class="paragraph"><p>Specifies whether workspace numbers should be displayed within the workspace\r
+buttons. This is useful if you want to have a named workspace that stays in\r
+order on the bar according to its number without displaying the number prefix.</p></div>\r
+<div class="paragraph"><p>When <tt>strip_workspace_numbers</tt> is set to <tt>yes</tt>, any workspace that has a name of\r
+the form "[n]:[NAME]" will display only the name. You could use this, for\r
+instance, to display Roman numerals rather than digits by naming your\r
+workspaces to "1:I", "2:II", "3:III", "4:IV", …</p></div>\r
+<div class="paragraph"><p>The default is to display the full name within the workspace button.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>strip_workspace_numbers yes|no</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ strip_workspace_numbers yes\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_binding_mode_indicator">5.14. Binding Mode indicator</h3>\r
+<div class="paragraph"><p>Specifies whether the current binding mode indicator should be shown or not.\r
+This is useful if you want to hide the workspace buttons but still be able\r
+to see the current binding mode indicator. See <a href="#binding_modes">[binding_modes]</a> to learn what\r
+modes are and how to use them.</p></div>\r
+<div class="paragraph"><p>The default is to show the mode indicator.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>binding_mode_indicator yes|no</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ binding_mode_indicator no\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_colors">5.15. Colors</h3>\r
+<div class="paragraph"><p>As with i3, colors are in HTML hex format (#rrggbb). The following colors can\r
+be configured at the moment:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+background\r
+</dt>\r
+<dd>\r
+<p>\r
+ Background color of the bar.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+statusline\r
+</dt>\r
+<dd>\r
+<p>\r
+ Text color to be used for the statusline.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+separator\r
+</dt>\r
+<dd>\r
+<p>\r
+ Text color to be used for the separator.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+focused_background\r
+</dt>\r
+<dd>\r
+<p>\r
+ Background color of the bar on the currently focused monitor output. If\r
+ not used, the color will be taken from <tt>background</tt>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+focused_statusline\r
+</dt>\r
+<dd>\r
+<p>\r
+ Text color to be used for the statusline on the currently focused\r
+ monitor output. If not used, the color will be taken from <tt>statusline</tt>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+focused_separator\r
+</dt>\r
+<dd>\r
+<p>\r
+ Text color to be used for the separator on the currently focused\r
+ monitor output. If not used, the color will be taken from <tt>separator</tt>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+focused_workspace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Border, background and text color for a workspace button when the workspace\r
+ has focus.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+active_workspace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Border, background and text color for a workspace button when the workspace\r
+ is active (visible) on some output, but the focus is on another one.\r
+ You can only tell this apart from the focused workspace when you are\r
+ using multiple monitors.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+inactive_workspace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Border, background and text color for a workspace button when the workspace\r
+ does not have focus and is not active (visible) on any output. This\r
+ will be the case for most workspaces.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+urgent_workspace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Border, background and text color for a workspace button when the workspace\r
+ contains a window with the urgency hint set.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+binding_mode\r
+</dt>\r
+<dd>\r
+<p>\r
+ Border, background and text color for the binding mode indicator. If not used,\r
+ the colors will be taken from <tt>urgent_workspace</tt>.\r
+</p>\r
+</dd>\r
+</dl></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>colors {\r
+ background <color>\r
+ statusline <color>\r
+ separator <color>\r
+\r
+ <colorclass> <border> <background> <text>\r
+}</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example (default colors)</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar {\r
+ colors {\r
+ background #000000\r
+ statusline #ffffff\r
+ separator #666666\r
+\r
+ focused_workspace #4c7899 #285577 #ffffff\r
+ active_workspace #333333 #5f676a #ffffff\r
+ inactive_workspace #333333 #222222 #888888\r
+ urgent_workspace #2f343a #900000 #ffffff\r
+ binding_mode #2f343a #900000 #ffffff\r
+ }\r
+}</tt></pre>\r
+</div></div>\r
+</div>\r
+</div>\r
+</div>\r
+<div class="sect1">\r
+<h2 id="_list_of_commands">6. List of commands</h2>\r
+<div class="sectionbody">\r
+<div class="paragraph"><p>Commands are what you bind to specific keypresses. You can also issue commands\r
+at runtime without pressing a key by using the IPC interface. An easy way to\r
+do this is to use the <tt>i3-msg</tt> utility:</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># execute this on your shell to make the current container borderless\r
+i3-msg border none</tt></pre>\r
+</div></div>\r
+<div class="paragraph" id="command_chaining"><p>Commands can be chained by using <tt>;</tt> (a semicolon). So, to move a window to a\r
+specific workspace and immediately switch to that workspace, you can configure\r
+the following keybinding:</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym $mod+x move container to workspace 3; workspace 3</tt></pre>\r
+</div></div>\r
+<div class="paragraph" id="command_criteria"><p>Furthermore, you can change the scope of a command - that is, which containers\r
+should be affected by that command, by using various criteria. The criteria\r
+are specified before any command in a pair of square brackets and are separated\r
+by space.</p></div>\r
+<div class="paragraph"><p>When using multiple commands, separate them by using a <tt>,</tt> (a comma) instead of\r
+a semicolon. Criteria apply only until the next semicolon, so if you use a\r
+semicolon to separate commands, only the first one will be executed for the\r
+matched window(s).</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># if you want to kill all windows which have the class Firefox, use:\r
+bindsym $mod+x [class="Firefox"] kill\r
+\r
+# same thing, but case-insensitive\r
+bindsym $mod+x [class="(?i)firefox"] kill\r
+\r
+# kill only the About dialog from Firefox\r
+bindsym $mod+x [class="Firefox" window_role="About"] kill\r
+\r
+# enable floating mode and move container to workspace 4\r
+for_window [class="^evil-app$"] floating enable, move container to workspace 4</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>The criteria which are currently implemented are:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+class\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the window class (the second part of WM_CLASS). Use the\r
+ special value <tt>__focused__</tt> to match all windows having the same window\r
+ class as the currently focused window.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+instance\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the window instance (the first part of WM_CLASS). Use the\r
+ special value <tt>__focused__</tt> to match all windows having the same window\r
+ instance as the currently focused window.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+window_role\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the window role (WM_WINDOW_ROLE). Use the special value\r
+ <tt>__focused__</tt> to match all windows having the same window role as the\r
+ currently focused window.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+window_type\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compare the window type (_NET_WM_WINDOW_TYPE). Possible values are\r
+ <tt>normal</tt>, <tt>dialog</tt>, <tt>utility</tt>, <tt>toolbar</tt>, <tt>splash</tt>, <tt>menu</tt>, <tt>dropdown_menu</tt>,\r
+ <tt>popup_menu</tt>, <tt>tooltip</tt> and <tt>notification</tt>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+id\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the X11 window ID, which you can get via <tt>xwininfo</tt> for example.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+title\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the X11 window title (_NET_WM_NAME or WM_NAME as fallback).\r
+ Use the special value <tt>__focused__</tt> to match all windows having the\r
+ same window title as the currently focused window.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+urgent\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the urgent state of the window. Can be "latest" or "oldest".\r
+ Matches the latest or oldest urgent window, respectively.\r
+ (The following aliases are also available: newest, last, recent, first)\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+workspace\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the workspace name of the workspace the window belongs to. Use\r
+ the special value <tt>__focused__</tt> to match all windows in the currently\r
+ focused workspace.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+con_mark\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the marks set for this container, see <a href="#vim_like_marks">[vim_like_marks]</a>. A\r
+ match is made if any of the container’s marks matches the specified\r
+ mark.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+con_id\r
+</dt>\r
+<dd>\r
+<p>\r
+ Compares the i3-internal container ID, which you can get via the IPC\r
+ interface. Handy for scripting. Use the special value <tt>__focused__</tt>\r
+ to match only the currently focused window.\r
+</p>\r
+</dd>\r
+</dl></div>\r
+<div class="paragraph"><p>The criteria <tt>class</tt>, <tt>instance</tt>, <tt>role</tt>, <tt>title</tt>, <tt>workspace</tt> and <tt>mark</tt> are\r
+actually regular expressions (PCRE). See <tt>pcresyntax(3)</tt> or <tt>perldoc perlre</tt> for\r
+information on how to use them.</p></div>\r
+<div class="sect2">\r
+<h3 id="exec">6.1. Executing applications (exec)</h3>\r
+<div class="paragraph"><p>What good is a window manager if you can’t actually start any applications?\r
+The exec command starts an application by passing the command you specify to a\r
+shell. This implies that you can use globbing (wildcards) and programs will be\r
+searched in your <tt>$PATH</tt>.</p></div>\r
+<div class="paragraph"><p>See <a href="#command_chaining">[command_chaining]</a> for details on the special meaning of <tt>;</tt> (semicolon)\r
+and <tt>,</tt> (comma): they chain commands together in i3, so you need to use quoted\r
+strings (as shown in <a href="#exec_quoting">[exec_quoting]</a>) if they appear in your command.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>exec [--no-startup-id] <command></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Start the GIMP\r
+bindsym $mod+g exec gimp\r
+\r
+# Start the terminal emulator urxvt which is not yet startup-notification-aware\r
+bindsym $mod+Return exec --no-startup-id urxvt</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>The <tt>--no-startup-id</tt> parameter disables startup-notification support for this\r
+particular exec command. With startup-notification, i3 can make sure that a\r
+window appears on the workspace on which you used the exec command. Also, it\r
+will change the X11 cursor to <tt>watch</tt> (a clock) while the application is\r
+launching. So, if an application is not startup-notification aware (most GTK\r
+and Qt using applications seem to be, though), you will end up with a watch\r
+cursor for 60 seconds.</p></div>\r
+<div class="paragraph" id="exec_quoting"><p>If the command to be executed contains a <tt>;</tt> (semicolon) and/or a <tt>,</tt> (comma),\r
+the entire command must be quoted. For example, to have a keybinding for the\r
+shell command <tt>notify-send Hello, i3</tt>, you would add an entry to your\r
+configuration file like this:</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Execute a command with a comma in it\r
+bindsym $mod+p exec "notify-send Hello, i3"</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>If however a command with a comma and/or semicolon itself requires quotes, you\r
+must escape the internal quotation marks with double backslashes, like this:</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Execute a command with a comma, semicolon and internal quotes\r
+bindsym $mod+p exec "notify-send \\"Hello, i3; from $USER\\""</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_splitting_containers">6.2. Splitting containers</h3>\r
+<div class="paragraph"><p>The split command makes the current window a split container. Split containers\r
+can contain multiple windows. Depending on the layout of the split container,\r
+new windows get placed to the right of the current one (splith) or new windows\r
+get placed below the current one (splitv).</p></div>\r
+<div class="paragraph"><p>If you apply this command to a split container with the same orientation,\r
+nothing will happen. If you use a different orientation, the split container’s\r
+orientation will be changed (if it does not have more than one window).\r
+The <tt>toggle</tt> option will toggle the orientation of the split container if it\r
+contains a single window. Otherwise it makes the current window a split\r
+container with opposite orientation compared to the parent container.\r
+Use <tt>layout toggle split</tt> to change the layout of any split container from\r
+splitv to splith or vice-versa.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>split vertical|horizontal|toggle</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym $mod+v split vertical\r
+bindsym $mod+h split horizontal\r
+bindsym $mod+t split toggle</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_manipulating_layout">6.3. Manipulating layout</h3>\r
+<div class="paragraph"><p>Use <tt>layout toggle split</tt>, <tt>layout stacking</tt>, <tt>layout tabbed</tt>, <tt>layout splitv</tt>\r
+or <tt>layout splith</tt> to change the current container layout to splith/splitv,\r
+stacking, tabbed layout, splitv or splith, respectively.</p></div>\r
+<div class="paragraph"><p>To make the current window (!) fullscreen, use <tt>fullscreen enable</tt> (or\r
+<tt>fullscreen enable global</tt> for the global mode), to leave either fullscreen\r
+mode use <tt>fullscreen disable</tt>, and to toggle between these two states use\r
+<tt>fullscreen toggle</tt> (or <tt>fullscreen toggle global</tt>).</p></div>\r
+<div class="paragraph"><p>Likewise, to make the current window floating (or tiling again) use <tt>floating\r
+enable</tt> respectively <tt>floating disable</tt> (or <tt>floating toggle</tt>):</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>layout default|tabbed|stacking|splitv|splith\r
+layout toggle [split|all]</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>bindsym $mod+s layout stacking\r
+bindsym $mod+l layout toggle split\r
+bindsym $mod+w layout tabbed\r
+\r
+# Toggle between stacking/tabbed/split:\r
+bindsym $mod+x layout toggle\r
+\r
+# Toggle between stacking/tabbed/splith/splitv:\r
+bindsym $mod+x layout toggle all\r
+\r
+# Toggle fullscreen\r
+bindsym $mod+f fullscreen toggle\r
+\r
+# Toggle floating/tiling\r
+bindsym $mod+t floating toggle</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_focusing_moving_containers">6.4. Focusing containers</h3>\r
+<div class="paragraph"><p>To change focus, you can use the <tt>focus</tt> command. The following options are\r
+available:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+left|right|up|down\r
+</dt>\r
+<dd>\r
+<p>\r
+ Sets focus to the nearest container in the given direction.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+parent\r
+</dt>\r
+<dd>\r
+<p>\r
+ Sets focus to the parent container of the current container.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+child\r
+</dt>\r
+<dd>\r
+<p>\r
+ The opposite of <tt>focus parent</tt>, sets the focus to the last focused\r
+ child container.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+floating\r
+</dt>\r
+<dd>\r
+<p>\r
+ Sets focus to the last focused floating container.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+tiling\r
+</dt>\r
+<dd>\r
+<p>\r
+ Sets focus to the last focused tiling container.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+mode_toggle\r
+</dt>\r
+<dd>\r
+<p>\r
+ Toggles between floating/tiling containers.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+output\r
+</dt>\r
+<dd>\r
+<p>\r
+ Followed by a direction or an output name, this will focus the\r
+ corresponding output.\r
+</p>\r
+</dd>\r
+</dl></div>\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
+focus parent|child|floating|tiling|mode_toggle\r
+focus output left|right|up|down|<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
+bindsym $mod+j focus left\r
+bindsym $mod+k focus down\r
+bindsym $mod+l focus up\r
+bindsym $mod+semicolon focus right\r
+\r
+# Focus parent container\r
+bindsym $mod+u focus parent\r
+\r
+# Focus last floating/tiling container\r
+bindsym $mod+g focus mode_toggle\r
+\r
+# Focus the output right to the current one\r
+bindsym $mod+x focus output right\r
+\r
+# Focus the big output\r
+bindsym $mod+x focus output HDMI-2</tt></pre>\r
+</div></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># 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]\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 [[<px> px] [<px> px]|center]\r
+\r
+# Moves the container to the current position of the\r
+# mouse cursor. Only affects floating containers.\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># 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\r
+\r
+# Move container, but make floating containers\r
+# move more than the default\r
+bindsym $mod+j move left 20 px\r
+\r
+# Move floating container to the center of all outputs\r
+bindsym $mod+c move absolute position center\r
+\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="_sticky_floating_windows">6.6. 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
+window.</p></div>\r
+<div class="paragraph"><p>Note that while any window can be made sticky through this command, it will\r
+only take effect if the window is floating.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>sticky enable|disable|toggle</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># make a terminal sticky that was started as a notepad\r
+for_window [instance=notepad] sticky enable</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_changing_named_workspaces_moving_to_workspaces">6.7. 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
+only.</p></div>\r
+<div class="paragraph"><p>To move containers to specific workspaces, use <tt>move container to workspace</tt>.</p></div>\r
+<div class="paragraph"><p>You can also switch to the next and previous workspace with the commands\r
+<tt>workspace next</tt> and <tt>workspace prev</tt>, which is handy, for example, if you have\r
+workspace 1, 3, 4 and 9 and you want to cycle through them with a single key\r
+combination. To restrict those to the current output, use <tt>workspace\r
+next_on_output</tt> and <tt>workspace prev_on_output</tt>. Similarly, you can use <tt>move\r
+container to workspace next</tt>, <tt>move container to workspace prev</tt> to move a\r
+container to the next/previous workspace and <tt>move container to workspace current</tt>\r
+(the last one makes sense only when used with criteria).</p></div>\r
+<div class="paragraph"><p><tt>workspace next</tt> cycles through either numbered or named workspaces. But when it\r
+reaches the last numbered/named workspace, it looks for named workspaces after\r
+exhausting numbered ones and looks for numbered ones after exhausting named ones.</p></div>\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 class="paragraph"><p>Workspace names are parsed as\r
+<a href="https://developer.gnome.org/pango/stable/PangoMarkupFormat.html">Pango markup</a>\r
+by i3bar.</p></div>\r
+<div class="paragraph" id="back_and_forth"><p>To switch back to the previously focused workspace, use <tt>workspace\r
+back_and_forth</tt>; likewise, you can move containers to the previously focused\r
+workspace using <tt>move container to workspace back_and_forth</tt>.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>workspace next|prev|next_on_output|prev_on_output\r
+workspace back_and_forth\r
+workspace [--no-auto-back-and-forth] <name>\r
+workspace [--no-auto-back-and-forth] number <name>\r
+\r
+move [--no-auto-back-and-forth] [window|container] [to] workspace <name>\r
+move [--no-auto-back-and-forth] [window|container] [to] workspace number <name>\r
+move [window|container] [to] workspace prev|next|current</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>bindsym $mod+1 workspace 1\r
+bindsym $mod+2 workspace 2\r
+bindsym $mod+3 workspace 3:<span foreground="red">vim</span>\r
+...\r
+\r
+bindsym $mod+Shift+1 move container to workspace 1\r
+bindsym $mod+Shift+2 move container to workspace 2\r
+...\r
+\r
+# switch between the current and the previously focused one\r
+bindsym $mod+b workspace back_and_forth\r
+bindsym $mod+Shift+b move container to workspace back_and_forth\r
+\r
+# move the whole workspace to the next output\r
+bindsym $mod+x move workspace to output right\r
+\r
+# move firefox to current workspace\r
+bindsym $mod+F1 [class="Firefox"] move workspace current</tt></pre>\r
+</div></div>\r
+<div class="sect3">\r
+<h4 id="_named_workspaces">6.7.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
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym $mod+1 workspace mail\r
+...</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>If you want the workspace to have a number <strong>and</strong> a name, just prefix the\r
+number, like this:</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym $mod+1 workspace 1: mail\r
+bindsym $mod+2 workspace 2: www\r
+...</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>Note that the workspace will really be named "1: mail". i3 treats workspace\r
+names beginning with a number in a slightly special way. Normally, named\r
+workspaces are ordered the way they appeared. When they start with a number, i3\r
+will order them numerically. Also, you will be able to use <tt>workspace number 1</tt>\r
+to switch to the workspace which begins with number 1, regardless of which name\r
+it has. This is useful in case you are changing the workspace’s name\r
+dynamically. To combine both commands you can use <tt>workspace number 1: mail</tt> to\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">6.7.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
+the currently focused workspace. This is handy if you want to use the\r
+rename command with <tt>i3-input</tt>.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>rename workspace <old_name> to <new_name>\r
+rename workspace to <new_name></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>i3-msg 'rename workspace 5 to 6'\r
+i3-msg 'rename workspace 1 to "1: www"'\r
+i3-msg 'rename workspace "1: www" to "10: www"'\r
+i3-msg 'rename workspace to "2: mail"'\r
+bindsym $mod+r exec i3-input -F 'rename workspace to "%s"' -P 'New name: '</tt></pre>\r
+</div></div>\r
+</div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_moving_workspaces_to_a_different_screen">6.8. 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="move_to_outputs">6.9. 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
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>move container to output left|right|down|up|<output>\r
+move workspace to output left|right|down|up|<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># Move the current workspace to the next output\r
+# (effectively toggles when you only have two outputs)\r
+bindsym $mod+x move workspace to output right\r
+\r
+# Put this window on the presentation output.\r
+bindsym $mod+x move container to output VGA1</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_moving_containers_windows_to_marks">6.10. 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.</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 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">6.11. 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
+</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
+space from all the other containers. The optional pixel argument specifies by\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
+<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/i3.config.keycodes">default config</a> for more\r
+context.</p></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>for_window [class="urxvt"] resize set 640 480</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_jumping_to_specific_windows">6.12. 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
+important goal. Instead of figuring out how to navigate to your mail client,\r
+it would be more convenient to have a shortcut. You can use the <tt>focus</tt> command\r
+with criteria for that.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>[class="class"] focus\r
+[title="title"] focus</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># Get me to the next open VIM instance\r
+bindsym $mod+a [class="urxvt" title="VIM"] focus</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="vim_like_marks">6.13. 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
+an arbitrary label and use it afterwards. You can unmark the label in the same\r
+way, using the unmark command. If you don’t specify a label, unmark removes all\r
+marks. You do not need to ensure that your windows have unique classes or\r
+titles, and you do not need to change your configuration file.</p></div>\r
+<div class="paragraph"><p>As the command needs to include the label with which you want to mark the\r
+window, you cannot simply bind it to a key. <tt>i3-input</tt> is a tool created\r
+for this purpose: It lets you input a command and sends the command to i3. It\r
+can also prefix this command and display a custom prompt for the input dialog.</p></div>\r
+<div class="paragraph"><p>The additional <tt>--toggle</tt> option will remove the mark if the window already has\r
+this mark or add it otherwise. Note that you may need to use this in\r
+combination with <tt>--add</tt> (see below) as any other marks will otherwise be\r
+removed.</p></div>\r
+<div class="paragraph"><p>By default, a window can only have one mark. You can use the <tt>--add</tt> flag to\r
+put more than one mark on a window.</p></div>\r
+<div class="paragraph"><p>Refer to <a href="#show_marks">[show_marks]</a> if you don’t want marks to be shown in the window decoration.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>mark [--add|--replace] [--toggle] <identifier>\r
+[con_mark="identifier"] focus\r
+unmark <identifier></tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example (in a terminal)</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># marks the focused container\r
+mark irssi\r
+\r
+# focus the container with the mark "irssi"\r
+'[con_mark="irssi"] focus'\r
+\r
+# remove the mark "irssi" from whichever container has it\r
+unmark irssi\r
+\r
+# remove all marks on all firefox windows\r
+[class="(?i)firefox"] unmark</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="pango_markup">6.14. 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
+<a href="https://developer.gnome.org/pango/stable/PangoMarkupFormat.html">Pango markup</a>\r
+and the following placeholders which will be replaced:</p></div>\r
+<div class="dlist"><dl>\r
+<dt class="hdlist1">\r
+<tt>%title</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+ For normal windows, this is the X11 window title (_NET_WM_NAME or WM_NAME\r
+ as fallback). When used on containers without a window (e.g., a split\r
+ container inside a tabbed/stacked layout), this will be the tree\r
+ representation of the container (e.g., "H[xterm xterm]").\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+<tt>%class</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+ The X11 window class (second part of WM_CLASS). This corresponds to the\r
+ <tt>class</tt> criterion, see <a href="#command_criteria">[command_criteria]</a>.\r
+</p>\r
+</dd>\r
+<dt class="hdlist1">\r
+<tt>%instance</tt>\r
+</dt>\r
+<dd>\r
+<p>\r
+ The X11 window instance (first part of WM_CLASS). This corresponds to the\r
+ <tt>instance</tt> criterion, see <a href="#command_criteria">[command_criteria]</a>.\r
+</p>\r
+</dd>\r
+</dl></div>\r
+<div class="paragraph"><p>Using the <a href="#for_window">[for_window]</a> directive, you can set the title format for any window\r
+based on <a href="#command_criteria">[command_criteria]</a>.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>title_format <format></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># give the focused window a prefix\r
+bindsym $mod+p title_format "Important | %title"\r
+\r
+# print all window titles bold\r
+for_window [class=".*"] title_format "<b>%title</b>"\r
+\r
+# print window titles of firefox windows red\r
+for_window [class="(?i)firefox"] title_format "<span foreground='red'>%title</span>"</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_changing_border_style">6.15. 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 class="paragraph"><p>There is also <tt>border toggle</tt> which will toggle the different border styles.</p></div>\r
+<div class="paragraph"><p>Note that "pixel" refers to logical pixel. On HiDPI displays, a logical pixel\r
+may be represented by multiple physical pixels, so <tt>pixel 1</tt> might not\r
+necessarily translate into a single pixel row wide border.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>border normal|pixel [<n>]\r
+border none|toggle\r
+\r
+# legacy syntax, equivalent to "border pixel 1"\r
+border 1pixel</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># use window title, but no border\r
+bindsym $mod+t border normal 0\r
+# use no window title and a thick border\r
+bindsym $mod+y border pixel 3\r
+# use neither window title nor border\r
+bindsym $mod+u border none</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="shmlog">6.16. 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
+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
+discarded and a new one will be started.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>shmlog <size_in_bytes>\r
+shmlog on|off|toggle</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># Enable/disable logging\r
+bindsym $mod+x shmlog toggle\r
+\r
+# or, from a terminal:\r
+# increase the shared memory log buffer to 50 MiB\r
+i3-msg shmlog $((50*1024*1024))</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_enabling_debug_logging">6.17. 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
+likely useful in combination with the above-described <a href="#shmlog">[shmlog]</a> command.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>debuglog on|off|toggle</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># Enable/disable logging\r
+bindsym $mod+x debuglog toggle</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_reloading_restarting_exiting">6.18. 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
+your X session. To exit i3 properly, you can use the <tt>exit</tt> command,\r
+however you don’t need to (simply killing your X session is fine as well).</p></div>\r
+<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym $mod+Shift+r restart\r
+bindsym $mod+Shift+w reload\r
+bindsym $mod+Shift+e exit</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_scratchpad">6.19. 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
+Instead, when using <tt>scratchpad show</tt>, the window will be shown again, as a\r
+floating window, centered on your current workspace (using <tt>scratchpad show</tt> on\r
+a visible scratchpad window will make it hidden again, so you can have a\r
+keybinding to toggle). Note that this is just a normal floating window, so if\r
+you want to "remove it from scratchpad", you can simple make it tiling again\r
+(<tt>floating toggle</tt>).</p></div>\r
+<div class="paragraph"><p>As the name indicates, this is useful for having a window with your favorite\r
+editor always at hand. However, you can also use this for other permanently\r
+running applications which you don’t want to see all the time: Your music\r
+player, alsamixer, maybe even your mail client…?</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>move scratchpad\r
+\r
+scratchpad show</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># Make the currently focused window a scratchpad\r
+bindsym $mod+Shift+minus move scratchpad\r
+\r
+# Show the first scratchpad window\r
+bindsym $mod+minus scratchpad show\r
+\r
+# Show the sup-mail scratchpad window, if any.\r
+bindsym mod4+s [title="^Sup ::"] scratchpad show</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_nop">6.20. 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 class="paragraph"><p>The optional <tt>comment</tt> argument is ignored, but will be printed to the log file\r
+for debugging purposes.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>nop [<comment>]</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Disable focus change for clicks on titlebars\r
+# with the middle mouse button\r
+bindsym button2 nop</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_i3bar_control">6.21. 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
+respectively mode option of each bar. It is also possible to toggle between\r
+hide state and show state as well as between dock mode and hide mode. Each\r
+i3bar instance can be controlled individually by specifying a bar_id, if none\r
+is given, the command is executed for all bar instances.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bar hidden_state hide|show|toggle [<bar_id>]\r
+\r
+bar mode dock|hide|invisible|toggle [<bar_id>]</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># Toggle between hide state and show state\r
+bindsym $mod+m bar hidden_state toggle\r
+\r
+# Toggle between dock mode and hide mode\r
+bindsym $mod+n bar mode toggle\r
+\r
+# Set the bar instance with id 'bar-1' to switch to hide mode\r
+bindsym $mod+b bar mode hide bar-1\r
+\r
+# Set the bar instance with id 'bar-1' to always stay hidden\r
+bindsym $mod+Shift+b bar mode invisible bar-1</tt></pre>\r
+</div></div>\r
+</div>\r
+</div>\r
+</div>\r
+<div class="sect1">\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
+handle multiple monitors.</p></div>\r
+<div class="paragraph"><p>When you have only one monitor, things are simple. You usually start with\r
+workspace 1 on your monitor and open new ones as you need them.</p></div>\r
+<div class="paragraph"><p>When you have more than one monitor, each monitor will get an initial\r
+workspace. The first monitor gets 1, the second gets 2 and a possible third\r
+would get 3. When you switch to a workspace on a different monitor, i3 will\r
+switch to that monitor and then switch to the workspace. This way, you don’t\r
+need shortcuts to switch to a specific monitor, and you don’t need to remember\r
+where you put which workspace. New workspaces will be opened on the currently\r
+active monitor. It is not possible to have a monitor without a workspace.</p></div>\r
+<div class="paragraph"><p>The idea of making workspaces global is based on the observation that most\r
+users have a very limited set of workspaces on their additional monitors.\r
+They are often used for a specific task (browser, shell) or for monitoring\r