"http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">\r
<html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">\r
<head>\r
-<link rel="icon" type="image/png" href="/favicon.png">\r
+<link rel="icon" type="image/x-icon" href="/favicon.ico">\r
<meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />\r
-<meta name="generator" content="AsciiDoc 8.6.4" />\r
+<meta name="generator" content="AsciiDoc 8.6.8" />\r
<title>i3: i3 User’s Guide</title>\r
<link rel="stylesheet" href="/css/style.css" type="text/css" />\r
<link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />\r
<script type="text/javascript">\r
/*<![CDATA[*/\r
-window.onload = function(){asciidoc.footnotes(); asciidoc.toc(2);}\r
+document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); asciidoc.toc(2);}, false);\r
/*]]>*/\r
</script>\r
<script type="text/javascript" src="/js/asciidoc-xhtml11.js"></script>\r
<ul id="nav">\r
<li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>\r
<li><a href="/screenshots">Screens</a></li>\r
+ <li><a href="https://faq.i3wm.org/">FAQ</a></li>\r
<li><a href="/contact">Contact</a></li>\r
- <li><a href="http://bugs.i3wm.org/">Bugs</a></li>\r
+ <li><a href="https://github.com/i3/i3/issues">Bugs</a></li>\r
</ul>\r
<br style="clear: both">\r
<div id="content">\r
<div id="header">\r
<h1>i3 User’s Guide</h1>\r
<span id="author">Michael Stapelberg</span><br />\r
-<span id="email"><tt><<a href="mailto:michael+i3@stapelberg.de">michael+i3@stapelberg.de</a>></tt></span><br />\r
-<span id="revdate">October 2011</span>\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>
<div id="preamble">\r
<div class="sectionbody">\r
<div class="paragraph"><p>This document contains all the information you need to configure and use the i3\r
-window manager. If it does not, please contact us on IRC (preferred) or post your\r
-question(s) on the mailing list.</p></div>\r
+window manager. If it does not, please check <a href="http://faq.i3wm.org/">http://faq.i3wm.org/</a> first, then\r
+contact us on IRC (preferred) or post your question(s) on the mailing list.</p></div>\r
</div>\r
</div>\r
<div class="sect1">\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
-<div class="paragraph"><p><strong>Keys to use with mod (alt):</strong></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
-<img src="keyboard-layer1.png" alt="Keys to use with mod (alt)" width="600" />\r
+<img src="keyboard-layer1.png" alt="Keys to use with $mod (Alt)" width="600" />\r
</a>\r
</span></p></div>\r
-<div class="paragraph"><p><strong>Keys to use with Shift+mod:</strong></p></div>\r
+<div class="paragraph"><p><strong>Keys to use with Shift+$mod:</strong></p></div>\r
<div class="paragraph"><p><span class="image">\r
<a class="image" href="keyboard-layer2.png">\r
-<img src="keyboard-layer2.png" alt="Keys to use with Shift+mod" width="600" />\r
+<img src="keyboard-layer2.png" alt="Keys to use with Shift+$mod" width="600" />\r
</a>\r
</span></p></div>\r
<div class="paragraph"><p>The red keys are the modifiers you need to press (by default), the blue keys\r
<div class="sect1">\r
<h2 id="_using_i3">2. Using i3</h2>\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 (Mod1) by default, with windows (Mod4)\r
-being a popular alternative.</p></div>\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 (Mod1) by default, with the Windows\r
+key (Mod4) being a popular alternative.</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
-for this is mod+Enter, that is Alt+Enter in the default configuration. By\r
-pressing mod+Enter, a new terminal will be opened. It will fill the whole\r
+for this is $mod+Enter, that is Alt+Enter in the default configuration. By\r
+pressing $mod+Enter, a new terminal will be opened. It will fill the whole\r
space available on your screen.</p></div>\r
<div class="paragraph"><p><span class="image">\r
<img src="single_terminal.png" alt="Single terminal" />\r
<div class="paragraph"><p>To move the focus between the two terminals, you can use the direction keys\r
which you may know from the editor <tt>vi</tt>. However, in i3, your homerow is used\r
for these keys (in <tt>vi</tt>, the keys are shifted to the left by one for\r
-compatibility with most keyboard layouts). Therefore, <tt>mod+J</tt> is left, <tt>mod+K</tt>\r
-is down, <tt>mod+L</tt> is up and <tt>mod+;</tt> is right. So, to switch between the\r
-terminals, use <tt>mod+K</tt> or <tt>mod+L</tt>. Of course, you can also use the arrow keys.</p></div>\r
+compatibility with most keyboard layouts). Therefore, <tt>$mod+J</tt> is left, <tt>$mod+K</tt>\r
+is down, <tt>$mod+L</tt> is up and <tt>$mod+;</tt> is right. So, to switch between the\r
+terminals, use <tt>$mod+K</tt> or <tt>$mod+L</tt>. Of course, you can also use the arrow keys.</p></div>\r
<div class="paragraph"><p>At the moment, your workspace is split (it contains two terminals) in a\r
specific direction (horizontal by default). Every window can be split\r
horizontally or vertically again, just like the workspace. The terminology is\r
or browser) and "split container" for containers that consist of one or more\r
windows.</p></div>\r
<div class="paragraph"><p>TODO: picture of the tree</p></div>\r
-<div class="paragraph"><p>To split a window vertically, press <tt>mod+v</tt>. To split it horizontally, press\r
-<tt>mod+h</tt>.</p></div>\r
+<div class="paragraph"><p>To split a window vertically, press <tt>$mod+v</tt> before you create the new window.\r
+To split it horizontally, press <tt>$mod+h</tt>.</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_changing_the_container_layout">2.2. Changing the container layout</h3>\r
<div class="paragraph"><p>A split container can have one of the following layouts:</p></div>\r
<div class="dlist"><dl>\r
<dt class="hdlist1">\r
-default\r
+splith/splitv\r
</dt>\r
<dd>\r
<p>\r
Windows are sized so that every window gets an equal amount of space in the\r
-container.\r
+container. splith distributes the windows horizontally (windows are right next\r
+to each other), splitv distributes them vertically (windows are on top of each\r
+other).\r
</p>\r
</dd>\r
<dt class="hdlist1">\r
</p>\r
</dd>\r
</dl></div>\r
-<div class="paragraph"><p>To switch modes, press <tt>mod+e</tt> for default, <tt>mod+s</tt> for stacking and\r
-<tt>mod+w</tt> for tabbed.</p></div>\r
+<div class="paragraph"><p>To switch modes, press <tt>$mod+e</tt> for splith/splitv (it toggles), <tt>$mod+s</tt> for\r
+stacking and <tt>$mod+w</tt> for tabbed.</p></div>\r
<div class="paragraph"><p><span class="image">\r
<img src="modes.png" alt="Container modes" />\r
</span></p></div>\r
<div class="sect2">\r
<h3 id="_toggling_fullscreen_mode_for_a_window">2.3. Toggling fullscreen mode for a window</h3>\r
<div class="paragraph"><p>To display a window in fullscreen mode or to go out of fullscreen mode again,\r
-press <tt>mod+f</tt>.</p></div>\r
+press <tt>$mod+f</tt>.</p></div>\r
<div class="paragraph"><p>There is also a global fullscreen mode in i3 in which the client will span all\r
-available outputs.</p></div>\r
+available outputs (the command is <tt>fullscreen toggle global</tt>).</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_opening_other_applications">2.4. Opening other applications</h3>\r
<div class="paragraph"><p>Aside from opening applications from a terminal, you can also use the handy\r
-<tt>dmenu</tt> which is opened by pressing <tt>mod+d</tt> by default. Just type the name\r
+<tt>dmenu</tt> which is opened by pressing <tt>$mod+d</tt> by default. Just type the name\r
(or a part of it) of the application which you want to open. The corresponding\r
application has to be in your <tt>$PATH</tt> for this to work.</p></div>\r
<div class="paragraph"><p>Additionally, if you have applications you open very frequently, you can\r
<h3 id="_closing_windows">2.5. Closing windows</h3>\r
<div class="paragraph"><p>If an application does not provide a mechanism for closing (most applications\r
provide a menu, the escape key or a shortcut like <tt>Control+W</tt> to close), you\r
-can press <tt>mod+Shift+q</tt> to kill a window. For applications which support\r
+can press <tt>$mod+Shift+q</tt> to kill a window. For applications which support\r
the WM_DELETE protocol, this will correctly close the application (saving\r
any modifications or doing other cleanup). If the application doesn’t support\r
the WM_DELETE protocol your X server will kill the window and the behaviour\r
<h3 id="_using_workspaces">2.6. Using workspaces</h3>\r
<div class="paragraph"><p>Workspaces are an easy way to group a set of windows. By default, you are on\r
the first workspace, as the bar on the bottom left indicates. To switch to\r
-another workspace, press <tt>mod+num</tt> where <tt>num</tt> is the number of the workspace\r
+another workspace, press <tt>$mod+num</tt> where <tt>num</tt> is the number of the workspace\r
you want to use. If the workspace does not exist yet, it will be created.</p></div>\r
<div class="paragraph"><p>A common paradigm is to put the web browser on one workspace, communication\r
applications (<tt>mutt</tt>, <tt>irssi</tt>, …) on another one, and the ones with which you\r
</div>\r
<div class="sect2">\r
<h3 id="_moving_windows_to_workspaces">2.7. Moving windows to workspaces</h3>\r
-<div class="paragraph"><p>To move a window to another workspace, simply press <tt>mod+Shift+num</tt> where\r
+<div class="paragraph"><p>To move a window to another workspace, simply press <tt>$mod+Shift+num</tt> where\r
<tt>num</tt> is (like when switching workspaces) the number of the target workspace.\r
Similarly to switching workspaces, the target workspace will be created if\r
it does not yet exist.</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_restarting_i3_inplace">2.9. Restarting i3 inplace</h3>\r
-<div class="paragraph"><p>To restart i3 inplace (and thus get into a clean state if there is a bug, or\r
-to upgrade to a newer version of i3) you can use <tt>mod+Shift+r</tt>.</p></div>\r
+<div class="paragraph"><p>To restart i3 in place (and thus get into a clean state if there is a bug, or\r
+to upgrade to a newer version of i3) you can use <tt>$mod+Shift+r</tt>.</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_exiting_i3">2.10. Exiting i3</h3>\r
-<div class="paragraph"><p>To cleanly exit i3 without killing your X server, you can use <tt>mod+Shift+e</tt>.</p></div>\r
+<div class="paragraph"><p>To cleanly exit i3 without killing your X server, you can use <tt>$mod+Shift+e</tt>.\r
+By default, a dialog will ask you to confirm if you really want to quit.</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_floating">2.11. Floating</h3>\r
-<div class="paragraph"><p>Floating mode is the opposite of tiling mode. The position and size of a window\r
-are not managed by i3, but by you. Using this mode violates the tiling\r
-paradigm but can be useful for some corner cases like "Save as" dialog\r
-windows, or toolbar windows (GIMP or similar). Those windows usually set the\r
-appropriate hint and are opened in floating mode by default.</p></div>\r
-<div class="paragraph"><p>You can toggle floating mode for a window by pressing <tt>mod+Shift+Space</tt>. By\r
+<div class="paragraph"><p>Floating mode is the opposite of tiling mode. The position and size of\r
+a window are not managed automatically by i3, but manually by\r
+you. Using this mode violates the tiling paradigm but can be useful\r
+for some corner cases like "Save as" dialog windows, or toolbar\r
+windows (GIMP or similar). Those windows usually set the appropriate\r
+hint and are opened in floating mode by default.</p></div>\r
+<div class="paragraph"><p>You can toggle floating mode for a window by pressing <tt>$mod+Shift+Space</tt>. By\r
dragging the window’s titlebar with your mouse you can move the window\r
around. By grabbing the borders and moving them you can resize the window. You\r
-can also do that by using the <a href="#floating_modifier">[floating_modifier]</a>.</p></div>\r
+can also do that by using the <a href="#floating_modifier">[floating_modifier]</a>. Another way to resize\r
+floating windows using the mouse is to right-click on the titlebar and drag.</p></div>\r
<div class="paragraph"><p>For resizing floating windows with your keyboard, see <a href="#resizingconfig">[resizingconfig]</a>.</p></div>\r
<div class="paragraph"><p>Floating windows are always on top of tiling windows.</p></div>\r
</div>\r
<div class="paragraph"><p>i3 stores all information about the X11 outputs, workspaces and layout of the\r
windows on them in a tree. The root node is the X11 root window, followed by\r
the X11 outputs, then dock areas and a content container, then workspaces and\r
-finally the windows themselve. In previous versions of i3 we had multiple lists\r
+finally the windows themselves. In previous versions of i3 we had multiple lists\r
(of outputs, workspaces) and a table for each workspace. That approach turned\r
out to be complicated to use (snapping), understand and implement.</p></div>\r
<div class="sect2">\r
<h3 id="_orientation_and_split_containers">3.2. Orientation and Split Containers</h3>\r
<div class="paragraph" id="OrientationSplit"><p>It is only natural to use so-called <tt>Split Containers</tt> in order to build a\r
layout when using a tree as data structure. In i3, every <tt>Container</tt> has an\r
-orientation (horizontal, vertical or unspecified). So, in our example with the\r
-workspace, the default orientation of the workspace <tt>Container</tt> is horizontal\r
-(most monitors are widescreen nowadays). If you change the orientation to\r
-vertical (<tt>mod+v</tt> in the default config) and <strong>then</strong> open two terminals, i3 will\r
-configure your windows like this:</p></div>\r
+orientation (horizontal, vertical or unspecified) and the orientation depends\r
+on the layout the container is in (vertical for splitv and stacking, horizontal\r
+for splith and tabbed). So, in our example with the workspace, the default\r
+layout of the workspace <tt>Container</tt> is splith (most monitors are widescreen\r
+nowadays). If you change the layout to splitv (<tt>$mod+v</tt> in the default config)\r
+and <strong>then</strong> open two terminals, i3 will configure your windows like this:</p></div>\r
<div class="imageblock">\r
<div class="content">\r
<img src="tree-shot2.png" alt="shot2" />\r
</div>\r
<div class="title">Figure 2. Vertical Workspace Orientation</div>\r
</div>\r
-<div class="paragraph"><p>An interesting new feature of the tree branch is the ability to split anything:\r
-Let’s assume you have two terminals on a workspace (with horizontal\r
-orientation), focus is on the right terminal. Now you want to open another\r
-terminal window below the current one. If you would just open a new terminal\r
-window, it would show up to the right due to the horizontal workspace\r
-orientation. Instead, press <tt>mod+v</tt> to create a <tt>Vertical Split Container</tt> (to\r
-open a <tt>Horizontal Split Container</tt>, use <tt>mod+h</tt>). Now you can open a new\r
+<div class="paragraph"><p>An interesting new feature of i3 since version 4 is the ability to split anything:\r
+Let’s assume you have two terminals on a workspace (with splith layout, that is\r
+horizontal orientation), focus is on the right terminal. Now you want to open\r
+another terminal window below the current one. If you would just open a new\r
+terminal window, it would show up to the right due to the splith layout.\r
+Instead, press <tt>$mod+v</tt> to split the container with the splitv layout (to\r
+open a <tt>Horizontal Split Container</tt>, use <tt>$mod+h</tt>). Now you can open a new\r
terminal and it will open below the current one:</p></div>\r
<div class="imageblock" style="float:right;">\r
<div class="content">\r
<div class="title">Figure 4. Focus parent, then open new terminal</div>\r
</div>\r
</div>\r
+<div class="sect2">\r
+<h3 id="_implicit_containers">3.4. Implicit containers</h3>\r
+<div class="paragraph"><p>In some cases, i3 needs to implicitly create a container to fulfill your\r
+command.</p></div>\r
+<div class="paragraph"><p>One example is the following scenario: You start i3 with a single monitor and a\r
+single workspace on which you open three terminal windows. All these terminal\r
+windows are directly attached to one node inside i3’s layout tree, the\r
+workspace node. By default, the workspace node’s orientation is <tt>horizontal</tt>.</p></div>\r
+<div class="paragraph"><p>Now you move one of these terminals down (<tt>$mod+Shift+k</tt> by default). The\r
+workspace node’s orientation will be changed to <tt>vertical</tt>. The terminal window\r
+you moved down is directly attached to the workspace and appears on the bottom\r
+of the screen. A new (horizontal) container was created to accommodate the\r
+other two terminal windows. You will notice this when switching to tabbed mode\r
+(for example). You would end up having one tab called "another container" and\r
+the other one being the terminal window you moved down.</p></div>\r
+</div>\r
</div>\r
</div>\r
<div class="sect1">\r
<h2 id="configuring">4. Configuring i3</h2>\r
<div class="sectionbody">\r
-<div class="paragraph"><p>This is where the real fun begins ;-). Most things are very dependant on your\r
+<div class="paragraph"><p>This is where the real fun begins ;-). Most things are very dependent on your\r
ideal working environment so we can’t make reasonable defaults for them.</p></div>\r
<div class="paragraph"><p>While not using a programming language for the configuration, i3 stays\r
quite flexible in regards to the things you usually want your window manager\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_fonts">4.2. Fonts</h3>\r
-<div class="paragraph"><p>i3 uses X core fonts (not Xft) for rendering window titles. You can use\r
-<tt>xfontsel(1)</tt> to generate such a font description. To see special characters\r
-(Unicode), you need to use a font which supports the ISO-10646 encoding.</p></div>\r
+<h3 id="fonts">4.2. Fonts</h3>\r
+<div class="paragraph"><p>i3 has support for both X core fonts and FreeType fonts (through Pango) to\r
+render window titles.</p></div>\r
+<div class="paragraph"><p>To generate an X core font description, you can use <tt>xfontsel(1)</tt>. To see\r
+special characters (Unicode), you need to use a font which supports the\r
+ISO-10646 encoding.</p></div>\r
+<div class="paragraph"><p>A FreeType font description is composed by a font family, a style, a weight,\r
+a variant, a stretch and a size.\r
+FreeType fonts support right-to-left rendering and contain often more\r
+Unicode glyphs than X core fonts.</p></div>\r
<div class="paragraph"><p>If i3 cannot open the configured font, it will output an error in the logfile\r
and fall back to a working font.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>font <X core font description></tt></pre>\r
+<pre><tt>font <X core font description>\r
+font pango:[family list] [style options] [size]</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>font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1</tt></pre>\r
+<pre><tt>font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1\r
+font pango:DejaVu Sans Mono 10\r
+font pango:DejaVu Sans Mono, Terminus Bold Semi-Condensed 11\r
+font pango:Terminus 11px</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
A keysym (key symbol) is a description for a specific symbol, like "a"\r
or "b", but also more strange ones like "underscore" instead of "_". These\r
are the ones you use in Xmodmap to remap your keys. To get the current\r
- mapping of your keys, use <tt>xmodmap -pke</tt>.\r
+ mapping of your keys, use <tt>xmodmap -pke</tt>. To interactively enter a key and\r
+ see what keysym it is configured to, use <tt>xev</tt>.\r
</p>\r
</li>\r
<li>\r
your bindings in the same physical location on the keyboard, use keycodes.\r
If you don’t switch layouts, and want a clean and simple config file, use\r
keysyms.</p></div>\r
+<div class="paragraph"><p>Some tools (such as <tt>import</tt> or <tt>xdotool</tt>) might be unable to run upon a\r
+KeyPress event, because the keyboard/pointer is still grabbed. For these\r
+situations, the <tt>--release</tt> flag can be used, which will execute the command\r
+after the keys have been released.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>bindsym [Modifiers+]keysym command\r
-bindcode [Modifiers+]keycode command</tt></pre>\r
+<pre><tt>bindsym [--release] [Modifiers+]keysym command\r
+bindcode [--release] [Modifiers+]keycode command</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># Fullscreen\r
-bindsym mod+f f\r
+bindsym $mod+f fullscreen toggle\r
\r
# Restart\r
-bindsym mod+Shift+r restart\r
+bindsym $mod+Shift+r restart\r
\r
# Notebook-specific hotkeys\r
-bindcode 214 exec /home/michael/toggle_beamer.sh</tt></pre>\r
+bindcode 214 exec --no-startup-id /home/michael/toggle_beamer.sh\r
+\r
+# Simulate ctrl+v upon pressing $mod+x\r
+bindsym --release $mod+x exec --no-startup-id xdotool key --clearmodifiers ctrl+v\r
+\r
+# Take a screenshot upon pressing $mod+x (select an area)\r
+bindsym --release $mod+x exec --no-startup-id import /tmp/latest-screenshot.png</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Available Modifiers:</p></div>\r
<div class="dlist"><dl>\r
</dl></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="floating_modifier">4.4. The floating modifier</h3>\r
+<h3 id="mousebindings">4.4. Mouse bindings</h3>\r
+<div class="paragraph"><p>A mouse binding makes i3 execute a command upon pressing a specific mouse\r
+button in the scope of the clicked container (see <a href="#command_criteria">[command_criteria]</a>). You\r
+can configure mouse bindings in a similar way to key bindings.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>bindsym [--release] [--whole-window] [Modifiers+]button[n] command</tt></pre>\r
+</div></div>\r
+<div class="paragraph"><p>By default, the binding will only run when you click on the titlebar of the\r
+window. If the <tt>--whole-window</tt> flag is given, it will run when any part of the\r
+window is clicked. If the <tt>--release</tt> flag is given, it will run when the mouse\r
+button is released.</p></div>\r
+<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># The middle button over a titlebar kills the window\r
+bindsym --release button2 kill\r
+\r
+# The middle button and a modifer over any part of the window kills the window\r
+bindsym --whole-window $mod+button2 kill\r
+\r
+# The right button toggles floating\r
+bindsym button3 floating toggle\r
+bindsym $mod+button3 floating toggle\r
+\r
+# The side buttons move the window around\r
+bindsym button9 move left\r
+bindsym button8 move right</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="floating_modifier">4.5. 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
click anywhere in the window itself to move it. The most common setup is to\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_orientation_for_new_workspaces">4.5. Orientation for new workspaces</h3>\r
+<h3 id="_constraining_floating_window_size">4.6. Constraining floating window size</h3>\r
+<div class="paragraph"><p>The maximum and minimum dimensions of floating windows can be specified. If\r
+either dimension of <tt>floating_maximum_size</tt> is specified as -1, that dimension\r
+will be unconstrained with respect to its maximum value. If either dimension of\r
+<tt>floating_maximum_size</tt> is undefined, or specified as 0, i3 will use a default\r
+value to constrain the maximum size. <tt>floating_minimum_size</tt> is treated in a\r
+manner analogous to <tt>floating_maximum_size</tt>.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>floating_minimum_size <width> x <height>\r
+floating_maximum_size <width> x <height></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>floating_minimum_size 75 x 50\r
+floating_maximum_size -1 x -1</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_orientation_for_new_workspaces">4.7. Orientation for new workspaces</h3>\r
<div class="paragraph"><p>New workspaces get a reasonable default orientation: Wide-screen monitors\r
(anything wider than high) get horizontal orientation, rotated monitors\r
(anything higher than wide) get vertical orientation.</p></div>\r
<div class="paragraph"><p>With the <tt>default_orientation</tt> configuration directive, you can override that\r
-behaviour.</p></div>\r
+behavior.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_layout_mode_for_new_containers">4.6. Layout mode for new containers</h3>\r
+<h3 id="_layout_mode_for_new_containers">4.8. Layout mode for new containers</h3>\r
<div class="paragraph"><p>This option determines in which mode new containers on workspace level will\r
start.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_border_style_for_new_windows">4.7. Border style for new windows</h3>\r
-<div class="paragraph"><p>This option determines which border style new windows will have.</p></div>\r
+<h3 id="_border_style_for_new_windows">4.9. 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
+"normal". Note that new_float applies only to windows which are starting out as\r
+floating windows, e.g. dialog windows.</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|1pixel|none></tt></pre>\r
+<pre><tt>new_window <normal|1pixel|none|pixel>\r
+new_float <normal|1pixel|none|pixel></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>new_window 1pixel</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
+\r
+# A 3 px border\r
+new_window pixel 3</tt></pre>\r
+</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_arbitrary_commands_for_specific_windows_for_window">4.8. Arbitrary commands for specific windows (for_window)</h3>\r
+<h3 id="_hiding_vertical_borders">4.10. Hiding vertical borders</h3>\r
+<div class="paragraph"><p>You can hide vertical borders adjacent to the screen edges using\r
+<tt>hide_edge_borders</tt>. This is useful if you are using scrollbars, or do not want\r
+to waste even two pixels in displayspace. Default is none.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>hide_edge_borders <none|vertical|horizontal|both></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>hide_edge_borders vertical</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_arbitrary_commands_for_specific_windows_for_window">4.11. Arbitrary commands for specific windows (for_window)</h3>\r
<div class="paragraph"><p>With the <tt>for_window</tt> command, you can let i3 execute any command when it\r
encounters a specific window. This can be used to set windows to floating or to\r
change their border style, for example.</p></div>\r
<div class="paragraph"><p>The valid criteria are the same as those for commands, see <a href="#command_criteria">[command_criteria]</a>.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_variables">4.9. Variables</h3>\r
+<h3 id="_variables">4.12. Variables</h3>\r
<div class="paragraph"><p>As you learned in the section about keyboard bindings, you will have\r
to configure lots of bindings containing modifier keys. If you want to save\r
yourself some typing and be able to change the modifier you use later,\r
<pre><tt>set $m Mod1\r
bindsym $m+Shift+r restart</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>Variables are directly replaced in the file when parsing. There is no fancy\r
-handling and there are absolutely no plans to change this. If you need a more\r
-dynamic configuration you should create a little script which generates a\r
-configuration file and run it before starting i3 (for example in your\r
-<tt>~/.xsession</tt> file).</p></div>\r
+<div class="paragraph"><p>Variables are directly replaced in the file when parsing. Variables expansion\r
+is not recursive so it is not possible to define a variable with a value\r
+containing another variable. There is no fancy handling and there are\r
+absolutely no plans to change this. If you need a more dynamic configuration\r
+you should create a little script which generates a configuration file and run\r
+it before starting i3 (for example in your <tt>~/.xsession</tt> file).</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_automatically_putting_clients_on_specific_workspaces">4.10. Automatically putting clients on specific workspaces</h3>\r
+<h3 id="_automatically_putting_clients_on_specific_workspaces">4.13. Automatically putting clients on specific workspaces</h3>\r
<div class="paragraph" id="assign_workspace"><p>To automatically make a specific window show up on a specific workspace, you\r
can use an <strong>assignment</strong>. You can match windows by using any criteria,\r
see <a href="#command_criteria">[command_criteria]</a>. It is recommended that you match on window classes\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>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
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><strong>xwininfo</strong>:</p></div>\r
+<div class="paragraph"><p><strong>xprop</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>WM_CLASS(STRING) = "irssi", "URxvt"</tt></pre>\r
logfile first (see <a href="http://i3wm.org/docs/debugging.html">http://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
+workspace, but you don’t want to assign all instances of it permanently, you\r
+can make use of i3’s startup-notification support (see <a href="#exec">[exec]</a>) in your config\r
+file in the following way:</p></div>\r
+<div class="paragraph"><p><strong>Start iceweasel on workspace 3 (once)</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt># Start iceweasel on workspace 3, then switch back to workspace 1\r
+# (Being a command-line utility, i3-msg does not support startup notifications,\r
+# hence the exec --no-startup-id.)\r
+# (Starting iceweasel with i3’s exec command is important in order to make i3\r
+# create a startup notification context, without which the iceweasel window(s)\r
+# cannot be matched onto the workspace on which the command was started.)\r
+exec --no-startup-id i3-msg 'workspace 3; exec iceweasel; workspace 1'</tt></pre>\r
+</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_automatically_starting_applications_on_i3_startup">4.11. Automatically starting applications on i3 startup</h3>\r
+<h3 id="_automatically_starting_applications_on_i3_startup">4.14. Automatically starting applications on i3 startup</h3>\r
<div class="paragraph"><p>By using the <tt>exec</tt> keyword outside a keybinding, you can configure\r
which commands will be performed by i3 on initial startup. <tt>exec</tt>\r
commands will not run when restarting i3, if you need a command to run\r
<div class="paragraph"><p>The flag --no-startup-id is explained in <a href="#exec">[exec]</a>.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="workspace_screen">4.12. Automatically putting workspaces on specific screens</h3>\r
+<h3 id="workspace_screen">4.15. Automatically putting workspaces on specific screens</h3>\r
<div class="paragraph"><p>If you assign clients to workspaces, it might be handy to put the\r
workspaces on specific screens. Also, the assignment of workspaces to screens\r
will determine which workspace i3 uses for a new screen when adding screens\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_changing_colors">4.13. Changing colors</h3>\r
+<h3 id="_changing_colors">4.16. Changing colors</h3>\r
<div class="paragraph"><p>You can change all colors which i3 uses to draw the window decorations.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>colorclass border background text</tt></pre>\r
+<pre><tt>colorclass border background text indicator</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Where colorclass can be one of:</p></div>\r
<div class="dlist"><dl>\r
A client which has its urgency hint activated.\r
</p>\r
</dd>\r
+<dt class="hdlist1">\r
+client.placeholder\r
+</dt>\r
+<dd>\r
+<p>\r
+ Background and text color are used to draw placeholder window contents\r
+ (when restoring layouts). Border and indicator are ignored.\r
+</p>\r
+</dd>\r
</dl></div>\r
<div class="paragraph"><p>You can also specify the color to be used to paint the background of the client\r
windows. This color will be used to paint the window on top of which the client\r
<pre><tt>client.background color</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Only clients that do not cover the whole area of this window expose the color\r
-used to paint it. If you use a color other than black for your terminals, you\r
-most likely want to set the client background color to the same color as your\r
-terminal program’s background color to avoid black gaps between the rendered\r
-area of the termianal and the i3 border.</p></div>\r
+used to paint it.</p></div>\r
<div class="paragraph"><p>Colors are in HTML hex format (#rrggbb), see the following example:</p></div>\r
<div class="paragraph"><p><strong>Examples (default colors)</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt># class border backgr. text\r
-client.focused #4c7899 #285577 #ffffff\r
-client.focused_inactive #333333 #5f676a #ffffff\r
-client.unfocused #333333 #222222 #888888\r
-client.urgent #2f343a #900000 #ffffff</tt></pre>\r
+<pre><tt># class border backgr. text indicator\r
+client.focused #4c7899 #285577 #ffffff #2e9ef4\r
+client.focused_inactive #333333 #5f676a #ffffff #484e50\r
+client.unfocused #333333 #222222 #888888 #292d2e\r
+client.urgent #2f343a #900000 #ffffff #900000\r
+client.placeholder #000000 #0c0c0c #ffffff #000000</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Note that for the window decorations, the color around the child window is the\r
background color, and the border color is only the two thin lines at the top of\r
the window.</p></div>\r
+<div class="paragraph"><p>The indicator color is used for indicating where a new window will be opened.\r
+For horizontal split containers, the right border will be painted in indicator\r
+color, for vertical split containers, the bottom border. This only applies to\r
+single windows within a split container, which are otherwise indistinguishable\r
+from single windows outside of a split container.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_interprocess_communication">4.14. Interprocess communication</h3>\r
-<div class="paragraph"><p>i3 uses unix sockets to provide an IPC interface. This allows third-party\r
+<h3 id="_interprocess_communication">4.17. Interprocess communication</h3>\r
+<div class="paragraph"><p>i3 uses Unix sockets to provide an IPC interface. This allows third-party\r
programs to get information from i3, such as the current workspaces\r
(to display a workspace bar), and to control i3.</p></div>\r
<div class="paragraph"><p>The IPC socket is enabled by default and will be created in\r
-<tt>/tmp/i3-%u/ipc-socket.%p</tt> where <tt>%u</tt> is your UNIX username and <tt>%p</tt> is the PID\r
-of i3.</p></div>\r
+<tt>/tmp/i3-%u.XXXXXX/ipc-socket.%p</tt> where <tt>%u</tt> is your UNIX username, <tt>%p</tt> is\r
+the PID of i3 and XXXXXX is a string of random characters from the portable\r
+filename character set (see mkdtemp(3)).</p></div>\r
<div class="paragraph"><p>You can override the default path through the environment-variable <tt>I3SOCK</tt> or\r
by specifying the <tt>ipc-socket</tt> directive. This is discouraged, though, since i3\r
-does the right thing by default.</p></div>\r
+does the right thing by default. If you decide to change it, it is strongly\r
+recommended to set this to a location in your home directory so that no other\r
+user can create that directory.</p></div>\r
<div class="paragraph"><p><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>ipc-socket /tmp/i3-ipc.sock</tt></pre>\r
+<pre><tt>ipc-socket ~/.i3/i3-ipc.sock</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>You can then use the <tt>i3-msg</tt> application to perform any command listed in\r
the next section.</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_focus_follows_mouse">4.15. Focus follows mouse</h3>\r
-<div class="paragraph"><p>If you have a setup where your mouse usually is in your way (like a touchpad\r
-on your laptop which you do not want to disable completely), you might want\r
-to disable <em>focus follows mouse</em> and control focus only by using your keyboard.\r
-The mouse will still be useful inside the currently active window (for example\r
-to click on links in your browser window).</p></div>\r
+<h3 id="_focus_follows_mouse">4.18. Focus follows mouse</h3>\r
+<div class="paragraph"><p>By default, window focus follows your mouse movements. However, if you have a\r
+setup where your mouse usually is in your way (like a touchpad on your laptop\r
+which you do not want to disable completely), you might want to disable <em>focus\r
+follows mouse</em> and control focus only by using your keyboard. The mouse will\r
+still be useful inside the currently active window (for example to click on\r
+links in your browser window).</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_popups_during_fullscreen_mode">4.16. Popups during fullscreen mode</h3>\r
+<h3 id="_mouse_warping">4.19. Mouse warping</h3>\r
+<div class="paragraph"><p>By default, when switching focus to a window on a different output (e.g.\r
+focusing a window on workspace 3 on output VGA-1, coming from workspace 2 on\r
+LVDS-1), the mouse cursor is warped to the center of that window.</p></div>\r
+<div class="paragraph"><p>With the <tt>mouse_warping</tt> option, you can control when the mouse cursor should\r
+be warped. <tt>none</tt> disables warping entirely, whereas <tt>output</tt> is the default\r
+behavior described above.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>mouse_warping <output|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>mouse_warping none</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="_popups_during_fullscreen_mode">4.20. Popups during fullscreen mode</h3>\r
<div class="paragraph"><p>When you are in fullscreen mode, some applications still open popup windows\r
(take Xpdf for example). This is because these applications may not be aware\r
that they are in fullscreen mode (they do not check the corresponding hint).\r
-There are two things which are possible to do in this situation:</p></div>\r
+There are three things which are possible to do in this situation:</p></div>\r
<div class="olist arabic"><ol class="arabic">\r
<li>\r
<p>\r
+Display the popup if it belongs to the fullscreen application only. This is\r
+ the default and should be reasonable behavior for most users.\r
+</p>\r
+</li>\r
+<li>\r
+<p>\r
Just ignore the popup (don’t map it). This won’t interrupt you while you are\r
in fullscreen. However, some apps might react badly to this (deadlock until\r
you go out of fullscreen).\r
</li>\r
<li>\r
<p>\r
-Leave fullscreen mode. This is the default.\r
+Leave fullscreen mode.\r
</p>\r
</li>\r
</ol></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>popup_during_fullscreen <ignore|leave_fullscreen></tt></pre>\r
+<pre><tt>popup_during_fullscreen <smart|ignore|leave_fullscreen></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>popup_during_fullscreen ignore</tt></pre>\r
+<pre><tt>popup_during_fullscreen smart</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_focus_wrapping">4.17. Focus wrapping</h3>\r
+<h3 id="_focus_wrapping">4.21. 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 behaviour so you can navigate to\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>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
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_forcing_xinerama">4.18. Forcing Xinerama</h3>\r
+<h3 id="_forcing_xinerama">4.22. 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
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
reconfiguring your screens on the fly (they are read only once on startup and\r
that’s it).</p></div>\r
-<div class="paragraph"><p>For people who do cannot modify their <tt>~/.xsession</tt> to add the\r
+<div class="paragraph"><p>For people who cannot modify their <tt>~/.xsession</tt> to add the\r
<tt>--force-xinerama</tt> commandline parameter, a configuration option is provided:</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
Xinerama, instead they are counted up, starting at 0: <tt>xinerama-0</tt>, <tt>xinerama-1</tt>, …</p></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_automatic_back_and_forth_when_switching_to_the_current_workspace">4.19. Automatic back-and-forth when switching to the current workspace</h3>\r
+<h3 id="_automatic_back_and_forth_when_switching_to_the_current_workspace">4.23. Automatic back-and-forth when switching to the current workspace</h3>\r
<div class="paragraph"><p>This configuration directive enables automatic <tt>workspace back_and_forth</tt> (see\r
<a href="#back_and_forth">[back_and_forth]</a>) when switching to the workspace that is currently focused.</p></div>\r
<div class="paragraph"><p>For instance: Assume you are on workspace "1: www" and switch to "2: IM" using\r
mod+2 because somebody sent you a message. You don’t need to remember where you\r
-came from now, you can just press mod+2 again to switch back to "1: www".</p></div>\r
+came from now, you can just press $mod+2 again to switch back to "1: www".</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt>workspace_auto_back_and_forth yes</tt></pre>\r
</div></div>\r
</div>\r
+<div class="sect2">\r
+<h3 id="_delaying_urgency_hint_reset_on_workspace_change">4.24. Delaying urgency hint reset on workspace change</h3>\r
+<div class="paragraph"><p>If an application on another workspace sets an urgency hint, switching to this\r
+workspace may lead to immediate focus of the application, which also means the\r
+window decoration color would be immediately reset to <tt>client.focused</tt>. This\r
+may make it unnecessarily hard to tell which window originally raised the\r
+event.</p></div>\r
+<div class="paragraph"><p>In order to prevent this, you can tell i3 to delay resetting the urgency state\r
+by a certain time using the <tt>force_display_urgency_hint</tt> directive. Setting the\r
+value to 0 disables this feature.</p></div>\r
+<div class="paragraph"><p>The default is 500ms.</p></div>\r
+<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
+<div class="listingblock">\r
+<div class="content">\r
+<pre><tt>force_display_urgency_hint <timeout> ms</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>force_display_urgency_hint 500 ms</tt></pre>\r
+</div></div>\r
+</div>\r
</div>\r
</div>\r
<div class="sect1">\r
}</tt></pre>\r
</div></div>\r
<div class="sect2">\r
-<h3 id="_statusline_command">5.1. Statusline command</h3>\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><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>status_command i3status --config ~/.i3status.conf</tt></pre>\r
+<pre><tt>bar {\r
+ status_command i3status --config ~/.i3status.conf\r
+}</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_display_mode">5.2. Display mode</h3>\r
-<div class="paragraph"><p>You can have i3bar either 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>\r
-mode).</p></div>\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>The default is dock mode.</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></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>).</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. Currently only the mouse wheel buttons are supported. This is\r
+useful for disabling the scroll wheel action or running scripts that implement\r
+custom behavior for these buttons.</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></tt></pre>\r
+<pre><tt>wheel_up_cmd <command>\r
+wheel_down_cmd <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>mode hide</tt></pre>\r
+<pre><tt>bar {\r
+ wheel_up_cmd nop\r
+ wheel_down_cmd exec ~/.i3/scripts/custom_wheel_down\r
+}</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_position">5.3. Position</h3>\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="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>position top</tt></pre>\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.4. Output(s)</h3>\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
<div class="content">\r
<pre><tt># big monitor: everything\r
bar {\r
- output HDMI2\r
- status_command i3status\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
+ 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.5. Tray output</h3>\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
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>tray_output <none|output></tt></pre>\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
-tray_output none\r
+bar {\r
+ tray_output none\r
+}\r
+\r
+# show tray icons on the primary monitor\r
+tray_output primary\r
\r
# show tray icons on the big monitor\r
-tray_output HDMI2</tt></pre>\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>\r
<div class="sect2">\r
-<h3 id="_font">5.6. Font</h3>\r
-<div class="paragraph"><p>Specifies the font (again, X core font, not Xft, just like in i3) to be used in\r
-the bar.</p></div>\r
+<h3 id="_font">5.9. 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
<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1</tt></pre>\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="_workspace_buttons">5.7. Workspace buttons</h3>\r
+<h3 id="_workspace_buttons">5.10. 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>Example</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>workspace_buttons no</tt></pre>\r
+<pre><tt>bar {\r
+ workspace_buttons no\r
+}</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_colors">5.8. Colors</h3>\r
+<h3 id="_strip_workspace_numbers">5.11. 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.12. 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.\r
+For an example of a <tt>mode</tt> definition, see <a href="#resizingconfig">[resizingconfig]</a>.</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.13. 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
</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_workspace\r
</dt>\r
<dd>\r
<p>\r
- Text color/background color for a workspace button when the workspace\r
+ Border, background and text color for a workspace button when the workspace\r
has focus.\r
</p>\r
</dd>\r
</dt>\r
<dd>\r
<p>\r
- Text color/background color for a workspace button when the workspace\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
</dt>\r
<dd>\r
<p>\r
- Text color/background color for a workspace button when the workspace\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
</dt>\r
<dd>\r
<p>\r
- Text color/background color for workspaces which contain at least one\r
- window with the urgency hint set.\r
+ Border, background and text color for a workspace button when the workspace\r
+ contains a window with the urgency hint set. Also applies to <tt>mode</tt> indicators.\r
</p>\r
</dd>\r
</dl></div>\r
<pre><tt>colors {\r
background <color>\r
statusline <color>\r
+ separator <color>\r
\r
- colorclass <foreground> <background>\r
+ colorclass <border> <background> <text>\r
}</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p><strong>Example</strong>:</p></div>\r
+<div class="paragraph"><p><strong>Example (default colors)</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>colors {\r
- background #000000\r
- statusline #ffffff\r
+<pre><tt>bar {\r
+ colors {\r
+ background #000000\r
+ statusline #ffffff\r
+ separator #666666\r
\r
- focused_workspace #ffffff #285577\r
- active_workspace #ffffff #333333\r
- inactive_workspace #888888 #222222\r
- urgent_workspace #ffffff #900000\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
+ }\r
}</tt></pre>\r
</div></div>\r
</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 workspace 3; workspace 3</tt></pre>\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. These are\r
-prefixed in square brackets to every command. If you want to kill all windows\r
-which have the class Firefox, use:</p></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>bindsym mod+x [class="Firefox"] kill\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</tt></pre>\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
</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
con_mark\r
</dt>\r
<dd>\r
<div class="listingblock">\r
<div class="content">\r
<pre><tt># Start the GIMP\r
-bindsym mod+g exec gimp\r
+bindsym $mod+g exec gimp\r
\r
# Start the terminal emulator urxvt which is not yet startup-notification-aware\r
-bindsym mod+enter exec --no-startup-id urxvt</tt></pre>\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
<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. Every split container has an orientation, it is\r
-either split horizontally (a new window gets placed to the right of the current\r
-one) or vertically (a new window gets placed below the current one).</p></div>\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).</p></div>\r
+orientation will be changed (if it does not have more than one window). Use\r
+<tt>layout toggle split</tt> to change the layout of any split container from splitv\r
+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
<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</tt></pre>\r
+<pre><tt>bindsym $mod+v split vertical\r
+bindsym $mod+h split horizontal</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 default</tt>, <tt>layout stacking</tt> or <tt>layout tabbed</tt> to change the\r
-current container layout to default, stacking or tabbed layout, respectively.</p></div>\r
-<div class="paragraph"><p>To make the current window (!) fullscreen, use <tt>fullscreen</tt>, to make\r
-it floating (or tiling again) use <tt>floating enable</tt> respectively <tt>floating disable</tt>\r
-(or <tt>floating toggle</tt>):</p></div>\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 default\r
-bindsym mod+w layout tabbed\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\r
+bindsym $mod+f fullscreen toggle\r
\r
# Toggle floating/tiling\r
-bindsym mod+t floating toggle</tt></pre>\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/Moving containers</h3>\r
-<div class="paragraph"><p>To change the focus, use the focus command: <tt>focus left</tt>, <tt>focus right</tt>, <tt>focus down</tt> and <tt>focus up</tt>.</p></div>\r
+<div class="paragraph"><p>To change the focus, use the focus command: <tt>focus left</tt>, <tt>focus right</tt>, <tt>focus\r
+down</tt> and <tt>focus up</tt>.</p></div>\r
<div class="paragraph"><p>There are a few special parameters you can use for the focus command:</p></div>\r
<div class="dlist"><dl>\r
<dt class="hdlist1">\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>For moving, use <tt>move left</tt>, <tt>move right</tt>, <tt>move down</tt> and <tt>move up</tt>.</p></div>\r
<div class="paragraph"><p><strong>Syntax</strong>:</p></div>\r
<div class="content">\r
<pre><tt>focus <left|right|down|up>\r
focus <parent|child|floating|tiling|mode_toggle>\r
-move <left|right|down|up> [<px> px]</tt></pre>\r
+focus output <<left|right|down|up>|output>\r
+move <left|right|down|up> [<px> px]\r
+move [absolute] position [[<px> px] [<px> px]|center]</tt></pre>\r
</div></div>\r
<div class="paragraph"><p>Note that the amount of pixels you can specify for the <tt>move</tt> command is only\r
relevant for floating containers. The default amount is 10 pixels.</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
+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
+bindsym $mod+u focus parent\r
\r
# Focus last floating/tiling container\r
-bindsym mod+g focus mode_toggle\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\r
\r
# 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
+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</tt></pre>\r
+bindsym $mod+j move left 20 px\r
+\r
+# Move floating container to the center\r
+# of all outputs\r
+bindsym $mod+c move absolute position center</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_changing_named_workspaces_moving_to_workspaces">6.5. 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. To move containers to specific workspaces, use\r
-<tt>move workspace</tt>.</p></div>\r
+<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. Similarily, you can use <tt>move workspace next</tt> and <tt>move workspace\r
-prev</tt> to move a container to the next/previous workspace.</p></div>\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>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>.</p></div>\r
-<div class="paragraph"><p>To move a container to another xrandr output such as <tt>LVDS1</tt> or <tt>VGA1</tt>, you can\r
-use the <tt>move output</tt> command followed by the name of the target output. You\r
-may also use <tt>left</tt>, <tt>right</tt>, <tt>up</tt>, <tt>down</tt> instead of the xrandr output name to\r
-move to the the next output in the specified direction.</p></div>\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 <name>\r
+workspace number <name>\r
+\r
+move [window|container] [to] workspace <name>\r
+move [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
+<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 workspace 1\r
-bindsym mod+Shift+2 move workspace 2\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</tt></pre>\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.5.1. Named workspaces</h4>\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
+<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
<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
+<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.</p></div>\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.5.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="resizingconfig">6.6. Resizing containers/windows</h3>\r
+<h3 id="_moving_workspaces_to_a_different_screen">6.6. 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">6.7. Moving containers/workspaces to RandR outputs</h3>\r
+<div class="paragraph" id="move_to_outputs"><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="resizingconfig">6.8. 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]</tt></pre>\r
+<pre><tt>resize <grow|shrink> <direction> [<px> px [or <ppt> ppt]]</tt></pre>\r
</div></div>\r
-<div class="paragraph"><p>Direction can be one of <tt>up</tt>, <tt>down</tt>, <tt>left</tt> or <tt>right</tt>. The optional pixel\r
-argument specifies by how many pixels a <strong>floating container</strong> should be grown or\r
-shrunk (the default is 10 pixels). The ppt argument means percentage points\r
-and specifies by how many percentage points a <strong>tiling container</strong> should be\r
-grown or shrunk (the default is 10 percentage points).</p></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).</p></div>\r
<div class="paragraph"><p>I recommend using the resize command inside a so called <tt>mode</tt>:</p></div>\r
<div class="listingblock">\r
<div class="title">Example: Configuration file, defining a mode for resizing</div>\r
<pre><tt>mode "resize" {\r
# These bindings trigger as soon as you enter the resize mode\r
\r
- # They resize the border in the direction you pressed, e.g.\r
- # when pressing left, the window is resized so that it has\r
- # more space on its left\r
+ # Pressing left will shrink the window’s width.\r
+ # Pressing right will grow the window’s width.\r
+ # Pressing up will shrink the window’s height.\r
+ # Pressing down will grow the window’s height.\r
+ bindsym j resize shrink width 10 px or 10 ppt\r
+ bindsym k resize grow height 10 px or 10 ppt\r
+ bindsym l resize shrink height 10 px or 10 ppt\r
+ bindsym semicolon resize grow width 10 px or 10 ppt\r
\r
- bindsym j resize shrink left\r
- bindsym Shift+j resize grow left\r
-\r
- bindsym k resize grow down\r
- bindsym Shift+k resize shrink down\r
-\r
- bindsym l resize shrink up\r
- bindsym Shift+l resize grow up\r
-\r
- bindsym semicolon resize grow right\r
- bindsym Shift+semicolon resize shrink right\r
+ # same bindings, but for the arrow keys\r
+ bindsym Left resize shrink width 10 px or 10 ppt\r
+ bindsym Down resize grow height 10 px or 10 ppt\r
+ bindsym Up resize shrink height 10 px or 10 ppt\r
+ bindsym Right resize grow width 10 px or 10 ppt\r
\r
# back to normal: Enter or Escape\r
bindsym Return mode "default"\r
}\r
\r
# Enter resize mode\r
-bindsym mod+r mode "resize"</tt></pre>\r
+bindsym $mod+r mode "resize"</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_jumping_to_specific_windows">6.7. Jumping to specific windows</h3>\r
+<h3 id="_jumping_to_specific_windows">6.9. 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 mailclient,\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># Get me to the next open VIM instance\r
-bindsym mod+a [class="urxvt" title="VIM"] focus</tt></pre>\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_mark_goto">6.8. VIM-like marks (mark/goto)</h3>\r
+<h3 id="_vim_like_marks_mark_goto">6.10. VIM-like marks (mark/goto)</h3>\r
<div class="paragraph" id="vim_like_marks"><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 do not need to ensure that your\r
-windows have unique classes or titles, and you do not need to change your\r
-configuration file.</p></div>\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
<div class="listingblock">\r
<div class="content">\r
<pre><tt>mark identifier\r
-[con_mark="identifier"] focus</tt></pre>\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>$ i3-msg mark irssi\r
-$ i3-msg '[con_mark="irssi"] focus'</tt></pre>\r
+$ i3-msg '[con_mark="irssi"] focus'\r
+$ i3-msg unmark irssi</tt></pre>\r
</div></div>\r
</div>\r
<div class="sect2">\r
-<h3 id="_changing_border_style">6.9. Changing border style</h3>\r
+<h3 id="_changing_border_style">6.11. 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 1pixel</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><strong>Examples</strong>:</p></div>\r
<div class="listingblock">\r
<div class="content">\r
-<pre><tt>bindsym mod+t border normal\r
-bindsym mod+y border 1pixel\r
-bindsym mod+u border none</tt></pre>\r
+<pre><tt>bindsym $mod+t border normal\r
+bindsym $mod+y border 1pixel\r
+bindsym $mod+u border none</tt></pre>\r
+</div></div>\r
+</div>\r
+<div class="sect2">\r
+<h3 id="shmlog">6.12. 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.13. 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="stack-limit">6.10. Reloading/Restarting/Exiting</h3>\r
+<h3 id="_reloading_restarting_exiting">6.14. 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 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
+<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.15. 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="_i3bar_control">6.16. 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
quickly switch between windows. See <a href="#vim_like_marks">[vim_like_marks]</a>.\r
</p>\r
</li>\r
+<li>\r
+<p>\r
+For information on how to move existing workspaces between monitors,\r
+ see <a href="#_moving_containers_workspaces_to_randr_outputs">[_moving_containers_workspaces_to_randr_outputs]</a>.\r
+</p>\r
+</li>\r
</ol></div>\r
</div>\r
</div>\r
this task. It was written in C with the goal of using as few syscalls as\r
possible to reduce the time your CPU is woken up from sleep states. Because\r
i3status only spits out text, you need to combine it with some other tool, like\r
-i3bar. Use a pipe to connect them: <tt>i3status | i3bar -d</tt>.</p></div>\r
+i3bar. See <a href="#status_command">[status_command]</a> for how to display i3status in i3bar.</p></div>\r
<div class="paragraph"><p>Regardless of which application you use to display the status line, you\r
want to make sure that it registers as a dock window using EWMH hints. i3 will\r
position the window either at the top or at the bottom of the screen, depending\r
-on which hint the application sets. With i3bar, you can use <tt>-d</tt> or <tt>-dbottom</tt>\r
-for positioning it at the bottom and <tt>-dtop</tt> to position it at the top of the\r
-screen.</p></div>\r
+on which hint the application sets. With i3bar, you can configure its position,\r
+see <a href="#i3bar_position">[i3bar_position]</a>.</p></div>\r
</div>\r
<div class="sect2">\r
<h3 id="_giving_presentations_multi_monitor">8.2. Giving presentations (multi-monitor)</h3>\r
projects / i3 / i3.github.io / blobdiff