1 <!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.1//EN"
\r
2 "http://www.w3.org/TR/xhtml11/DTD/xhtml11.dtd">
\r
3 <html xmlns="http://www.w3.org/1999/xhtml" xml:lang="en">
\r
5 <link rel="icon" type="image/x-icon" href="/favicon.ico">
\r
6 <meta http-equiv="Content-Type" content="application/xhtml+xml; charset=UTF-8" />
\r
7 <meta name="generator" content="AsciiDoc 8.6.8" />
\r
8 <title>i3: i3 User’s Guide</title>
\r
9 <link rel="stylesheet" href="/css/style.css" type="text/css" />
\r
10 <link rel="stylesheet" href="/css/xhtml11.css" type="text/css" />
\r
11 <script type="text/javascript">
\r
13 document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); asciidoc.toc(2);}, false);
\r
16 <script type="text/javascript" src="/js/asciidoc-xhtml11.js"></script>
\r
18 <body class="article">
\r
21 <a href="/"><h1 id="title">i3 - improved tiling WM</h1></a>
\r
23 <li><a style="border-bottom: 2px solid #fff" href="/docs">Docs</a></li>
\r
24 <li><a href="/screenshots">Screens</a></li>
\r
25 <li><a href="https://faq.i3wm.org/">FAQ</a></li>
\r
26 <li><a href="/contact">Contact</a></li>
\r
27 <li><a href="https://github.com/i3/i3/issues">Bugs</a></li>
\r
29 <br style="clear: both">
\r
32 <h1>i3 User’s Guide</h1>
\r
33 <span id="author">Michael Stapelberg</span><br />
\r
34 <span id="email"><tt><<a href="mailto:michael@i3wm.org">michael@i3wm.org</a>></tt></span><br />
\r
35 <span id="revdate">March 2013</span>
\r
37 <div id="toctitle">Table of Contents</div>
38 <noscript><p><b>JavaScript must be enabled in your browser to display the table of contents.</b></p></noscript>
42 <div class="sectionbody">
\r
43 <div class="paragraph"><p>This document contains all the information you need to configure and use the i3
\r
44 window manager. If it does not, please check <a href="http://faq.i3wm.org/">http://faq.i3wm.org/</a> first, then
\r
45 contact us on IRC (preferred) or post your question(s) on the mailing list.</p></div>
\r
49 <h2 id="_default_keybindings">1. Default keybindings</h2>
\r
50 <div class="sectionbody">
\r
51 <div class="paragraph"><p>For the "too long; didn’t read" people, here is an overview of the default
\r
52 keybindings (click to see the full size image):</p></div>
\r
53 <div class="paragraph"><p><strong>Keys to use with $mod (Alt):</strong></p></div>
\r
54 <div class="paragraph"><p><span class="image">
\r
55 <a class="image" href="keyboard-layer1.png">
\r
56 <img src="keyboard-layer1.png" alt="Keys to use with $mod (Alt)" width="600" />
\r
59 <div class="paragraph"><p><strong>Keys to use with Shift+$mod:</strong></p></div>
\r
60 <div class="paragraph"><p><span class="image">
\r
61 <a class="image" href="keyboard-layer2.png">
\r
62 <img src="keyboard-layer2.png" alt="Keys to use with Shift+$mod" width="600" />
\r
65 <div class="paragraph"><p>The red keys are the modifiers you need to press (by default), the blue keys
\r
66 are your homerow.</p></div>
\r
70 <h2 id="_using_i3">2. Using i3</h2>
\r
71 <div class="sectionbody">
\r
72 <div class="paragraph"><p>Throughout this guide, the keyword <tt>$mod</tt> will be used to refer to the
\r
73 configured modifier. This is the Alt key (Mod1) by default, with the Windows
\r
74 key (Mod4) being a popular alternative.</p></div>
\r
76 <h3 id="_opening_terminals_and_moving_around">2.1. Opening terminals and moving around</h3>
\r
77 <div class="paragraph"><p>One very basic operation is opening a new terminal. By default, the keybinding
\r
78 for this is $mod+Enter, that is Alt+Enter in the default configuration. By
\r
79 pressing $mod+Enter, a new terminal will be opened. It will fill the whole
\r
80 space available on your screen.</p></div>
\r
81 <div class="paragraph"><p><span class="image">
\r
82 <img src="single_terminal.png" alt="Single terminal" />
\r
84 <div class="paragraph"><p>If you now open another terminal, i3 will place it next to the current one,
\r
85 splitting the screen size in half. Depending on your monitor, i3 will put the
\r
86 created window beside the existing window (on wide displays) or below the
\r
87 existing window (rotated displays).</p></div>
\r
88 <div class="paragraph"><p><span class="image">
\r
89 <img src="two_terminals.png" alt="Two terminals" />
\r
91 <div class="paragraph"><p>To move the focus between the two terminals, you can use the direction keys
\r
92 which you may know from the editor <tt>vi</tt>. However, in i3, your homerow is used
\r
93 for these keys (in <tt>vi</tt>, the keys are shifted to the left by one for
\r
94 compatibility with most keyboard layouts). Therefore, <tt>$mod+J</tt> is left, <tt>$mod+K</tt>
\r
95 is down, <tt>$mod+L</tt> is up and <tt>$mod+;</tt> is right. So, to switch between the
\r
96 terminals, use <tt>$mod+K</tt> or <tt>$mod+L</tt>. Of course, you can also use the arrow keys.</p></div>
\r
97 <div class="paragraph"><p>At the moment, your workspace is split (it contains two terminals) in a
\r
98 specific direction (horizontal by default). Every window can be split
\r
99 horizontally or vertically again, just like the workspace. The terminology is
\r
100 "window" for a container that actually contains an X11 window (like a terminal
\r
101 or browser) and "split container" for containers that consist of one or more
\r
103 <div class="paragraph"><p>TODO: picture of the tree</p></div>
\r
104 <div class="paragraph"><p>To split a window vertically, press <tt>$mod+v</tt> before you create the new window.
\r
105 To split it horizontally, press <tt>$mod+h</tt>.</p></div>
\r
107 <div class="sect2">
\r
108 <h3 id="_changing_the_container_layout">2.2. Changing the container layout</h3>
\r
109 <div class="paragraph"><p>A split container can have one of the following layouts:</p></div>
\r
110 <div class="dlist"><dl>
\r
111 <dt class="hdlist1">
\r
116 Windows are sized so that every window gets an equal amount of space in the
\r
117 container. splith distributes the windows horizontally (windows are right next
\r
118 to each other), splitv distributes them vertically (windows are on top of each
\r
122 <dt class="hdlist1">
\r
127 Only the focused window in the container is displayed. You get a list of
\r
128 windows at the top of the container.
\r
131 <dt class="hdlist1">
\r
136 The same principle as <tt>stacking</tt>, but the list of windows at the top is only
\r
137 a single line which is vertically split.
\r
141 <div class="paragraph"><p>To switch modes, press <tt>$mod+e</tt> for splith/splitv (it toggles), <tt>$mod+s</tt> for
\r
142 stacking and <tt>$mod+w</tt> for tabbed.</p></div>
\r
143 <div class="paragraph"><p><span class="image">
\r
144 <img src="modes.png" alt="Container modes" />
\r
147 <div class="sect2">
\r
148 <h3 id="_toggling_fullscreen_mode_for_a_window">2.3. Toggling fullscreen mode for a window</h3>
\r
149 <div class="paragraph"><p>To display a window in fullscreen mode or to go out of fullscreen mode again,
\r
150 press <tt>$mod+f</tt>.</p></div>
\r
151 <div class="paragraph"><p>There is also a global fullscreen mode in i3 in which the client will span all
\r
152 available outputs (the command is <tt>fullscreen toggle global</tt>).</p></div>
\r
154 <div class="sect2">
\r
155 <h3 id="_opening_other_applications">2.4. Opening other applications</h3>
\r
156 <div class="paragraph"><p>Aside from opening applications from a terminal, you can also use the handy
\r
157 <tt>dmenu</tt> which is opened by pressing <tt>$mod+d</tt> by default. Just type the name
\r
158 (or a part of it) of the application which you want to open. The corresponding
\r
159 application has to be in your <tt>$PATH</tt> for this to work.</p></div>
\r
160 <div class="paragraph"><p>Additionally, if you have applications you open very frequently, you can
\r
161 create a keybinding for starting the application directly. See the section
\r
162 <a href="#configuring">[configuring]</a> for details.</p></div>
\r
164 <div class="sect2">
\r
165 <h3 id="_closing_windows">2.5. Closing windows</h3>
\r
166 <div class="paragraph"><p>If an application does not provide a mechanism for closing (most applications
\r
167 provide a menu, the escape key or a shortcut like <tt>Control+W</tt> to close), you
\r
168 can press <tt>$mod+Shift+q</tt> to kill a window. For applications which support
\r
169 the WM_DELETE protocol, this will correctly close the application (saving
\r
170 any modifications or doing other cleanup). If the application doesn’t support
\r
171 the WM_DELETE protocol your X server will kill the window and the behaviour
\r
172 depends on the application.</p></div>
\r
174 <div class="sect2">
\r
175 <h3 id="_using_workspaces">2.6. Using workspaces</h3>
\r
176 <div class="paragraph"><p>Workspaces are an easy way to group a set of windows. By default, you are on
\r
177 the first workspace, as the bar on the bottom left indicates. To switch to
\r
178 another workspace, press <tt>$mod+num</tt> where <tt>num</tt> is the number of the workspace
\r
179 you want to use. If the workspace does not exist yet, it will be created.</p></div>
\r
180 <div class="paragraph"><p>A common paradigm is to put the web browser on one workspace, communication
\r
181 applications (<tt>mutt</tt>, <tt>irssi</tt>, …) on another one, and the ones with which you
\r
182 work, on the third one. Of course, there is no need to follow this approach.</p></div>
\r
183 <div class="paragraph"><p>If you have multiple screens, a workspace will be created on each screen at
\r
184 startup. If you open a new workspace, it will be bound to the screen you
\r
185 created it on. When you switch to a workspace on another screen, i3 will set
\r
186 focus to that screen.</p></div>
\r
188 <div class="sect2">
\r
189 <h3 id="_moving_windows_to_workspaces">2.7. Moving windows to workspaces</h3>
\r
190 <div class="paragraph"><p>To move a window to another workspace, simply press <tt>$mod+Shift+num</tt> where
\r
191 <tt>num</tt> is (like when switching workspaces) the number of the target workspace.
\r
192 Similarly to switching workspaces, the target workspace will be created if
\r
193 it does not yet exist.</p></div>
\r
195 <div class="sect2">
\r
196 <h3 id="_resizing">2.8. Resizing</h3>
\r
197 <div class="paragraph"><p>The easiest way to resize a container is by using the mouse: Grab the border
\r
198 and move it to the wanted size.</p></div>
\r
199 <div class="paragraph"><p>See <a href="#resizingconfig">[resizingconfig]</a> for how to configure i3 to be able to resize
\r
200 columns/rows with your keyboard.</p></div>
\r
202 <div class="sect2">
\r
203 <h3 id="_restarting_i3_inplace">2.9. Restarting i3 inplace</h3>
\r
204 <div class="paragraph"><p>To restart i3 in place (and thus get into a clean state if there is a bug, or
\r
205 to upgrade to a newer version of i3) you can use <tt>$mod+Shift+r</tt>.</p></div>
\r
207 <div class="sect2">
\r
208 <h3 id="_exiting_i3">2.10. Exiting i3</h3>
\r
209 <div class="paragraph"><p>To cleanly exit i3 without killing your X server, you can use <tt>$mod+Shift+e</tt>.
\r
210 By default, a dialog will ask you to confirm if you really want to quit.</p></div>
\r
212 <div class="sect2">
\r
213 <h3 id="_floating">2.11. Floating</h3>
\r
214 <div class="paragraph"><p>Floating mode is the opposite of tiling mode. The position and size of
\r
215 a window are not managed automatically by i3, but manually by
\r
216 you. Using this mode violates the tiling paradigm but can be useful
\r
217 for some corner cases like "Save as" dialog windows, or toolbar
\r
218 windows (GIMP or similar). Those windows usually set the appropriate
\r
219 hint and are opened in floating mode by default.</p></div>
\r
220 <div class="paragraph"><p>You can toggle floating mode for a window by pressing <tt>$mod+Shift+Space</tt>. By
\r
221 dragging the window’s titlebar with your mouse you can move the window
\r
222 around. By grabbing the borders and moving them you can resize the window. You
\r
223 can also do that by using the <a href="#floating_modifier">[floating_modifier]</a>. Another way to resize
\r
224 floating windows using the mouse is to right-click on the titlebar and drag.</p></div>
\r
225 <div class="paragraph"><p>For resizing floating windows with your keyboard, see <a href="#resizingconfig">[resizingconfig]</a>.</p></div>
\r
226 <div class="paragraph"><p>Floating windows are always on top of tiling windows.</p></div>
\r
230 <div class="sect1">
\r
231 <h2 id="_tree">3. Tree</h2>
\r
232 <div class="sectionbody">
\r
233 <div class="paragraph"><p>i3 stores all information about the X11 outputs, workspaces and layout of the
\r
234 windows on them in a tree. The root node is the X11 root window, followed by
\r
235 the X11 outputs, then dock areas and a content container, then workspaces and
\r
236 finally the windows themselves. In previous versions of i3 we had multiple lists
\r
237 (of outputs, workspaces) and a table for each workspace. That approach turned
\r
238 out to be complicated to use (snapping), understand and implement.</p></div>
\r
239 <div class="sect2">
\r
240 <h3 id="_the_tree_consists_of_containers">3.1. The tree consists of Containers</h3>
\r
241 <div class="paragraph"><p>The building blocks of our tree are so called <tt>Containers</tt>. A <tt>Container</tt> can
\r
242 host a window (meaning an X11 window, one that you can actually see and use,
\r
243 like a browser). Alternatively, it could contain one or more <tt>Containers</tt>. A
\r
244 simple example is the workspace: When you start i3 with a single monitor, a
\r
245 single workspace and you open two terminal windows, you will end up with a tree
\r
246 like this:</p></div>
\r
247 <div class="imageblock" style="float:right;">
\r
248 <div class="content">
\r
249 <img src="tree-layout2.png" alt="layout2" />
\r
252 <div class="imageblock">
\r
253 <div class="content">
\r
254 <img src="tree-shot4.png" alt="shot4" />
\r
256 <div class="title">Figure 1. Two terminals on standard workspace</div>
\r
259 <div class="sect2">
\r
260 <h3 id="_orientation_and_split_containers">3.2. Orientation and Split Containers</h3>
\r
261 <div class="paragraph" id="OrientationSplit"><p>It is only natural to use so-called <tt>Split Containers</tt> in order to build a
\r
262 layout when using a tree as data structure. In i3, every <tt>Container</tt> has an
\r
263 orientation (horizontal, vertical or unspecified) and the orientation depends
\r
264 on the layout the container is in (vertical for splitv and stacking, horizontal
\r
265 for splith and tabbed). So, in our example with the workspace, the default
\r
266 layout of the workspace <tt>Container</tt> is splith (most monitors are widescreen
\r
267 nowadays). If you change the layout to splitv (<tt>$mod+v</tt> in the default config)
\r
268 and <strong>then</strong> open two terminals, i3 will configure your windows like this:</p></div>
\r
269 <div class="imageblock">
\r
270 <div class="content">
\r
271 <img src="tree-shot2.png" alt="shot2" />
\r
273 <div class="title">Figure 2. Vertical Workspace Orientation</div>
\r
275 <div class="paragraph"><p>An interesting new feature of i3 since version 4 is the ability to split anything:
\r
276 Let’s assume you have two terminals on a workspace (with splith layout, that is
\r
277 horizontal orientation), focus is on the right terminal. Now you want to open
\r
278 another terminal window below the current one. If you would just open a new
\r
279 terminal window, it would show up to the right due to the splith layout.
\r
280 Instead, press <tt>$mod+v</tt> to split the container with the splitv layout (to
\r
281 open a <tt>Horizontal Split Container</tt>, use <tt>$mod+h</tt>). Now you can open a new
\r
282 terminal and it will open below the current one:</p></div>
\r
283 <div class="imageblock" style="float:right;">
\r
284 <div class="content">
\r
285 <img src="tree-layout1.png" alt="Layout" />
\r
288 <div class="imageblock">
\r
289 <div class="content">
\r
290 <img src="tree-shot1.png" alt="shot" />
\r
292 <div class="title">Figure 3. Vertical Split Container</div>
\r
294 <div style="clear:both;"></div>
\r
295 <div class="paragraph"><p>You probably guessed it already: There is no limit on how deep your hierarchy
\r
296 of splits can be.</p></div>
\r
298 <div class="sect2">
\r
299 <h3 id="_focus_parent">3.3. Focus parent</h3>
\r
300 <div class="paragraph"><p>Let’s stay with our example from above. We have a terminal on the left and two
\r
301 vertically split terminals on the right, focus is on the bottom right one. When
\r
302 you open a new terminal, it will open below the current one.</p></div>
\r
303 <div class="paragraph"><p>So, how can you open a new terminal window to the <strong>right</strong> of the current one?
\r
304 The solution is to use <tt>focus parent</tt>, which will focus the <tt>Parent Container</tt> of
\r
305 the current <tt>Container</tt>. In this case, you would focus the <tt>Vertical Split
\r
306 Container</tt> which is <strong>inside</strong> the horizontally oriented workspace. Thus, now new
\r
307 windows will be opened to the right of the <tt>Vertical Split Container</tt>:</p></div>
\r
308 <div class="imageblock">
\r
309 <div class="content">
\r
310 <img src="tree-shot3.png" alt="shot3" />
\r
312 <div class="title">Figure 4. Focus parent, then open new terminal</div>
\r
315 <div class="sect2">
\r
316 <h3 id="_implicit_containers">3.4. Implicit containers</h3>
\r
317 <div class="paragraph"><p>In some cases, i3 needs to implicitly create a container to fulfill your
\r
319 <div class="paragraph"><p>One example is the following scenario: You start i3 with a single monitor and a
\r
320 single workspace on which you open three terminal windows. All these terminal
\r
321 windows are directly attached to one node inside i3’s layout tree, the
\r
322 workspace node. By default, the workspace node’s orientation is <tt>horizontal</tt>.</p></div>
\r
323 <div class="paragraph"><p>Now you move one of these terminals down (<tt>$mod+Shift+k</tt> by default). The
\r
324 workspace node’s orientation will be changed to <tt>vertical</tt>. The terminal window
\r
325 you moved down is directly attached to the workspace and appears on the bottom
\r
326 of the screen. A new (horizontal) container was created to accommodate the
\r
327 other two terminal windows. You will notice this when switching to tabbed mode
\r
328 (for example). You would end up having one tab called "another container" and
\r
329 the other one being the terminal window you moved down.</p></div>
\r
333 <div class="sect1">
\r
334 <h2 id="configuring">4. Configuring i3</h2>
\r
335 <div class="sectionbody">
\r
336 <div class="paragraph"><p>This is where the real fun begins ;-). Most things are very dependent on your
\r
337 ideal working environment so we can’t make reasonable defaults for them.</p></div>
\r
338 <div class="paragraph"><p>While not using a programming language for the configuration, i3 stays
\r
339 quite flexible in regards to the things you usually want your window manager
\r
341 <div class="paragraph"><p>For example, you can configure bindings to jump to specific windows,
\r
342 you can set specific applications to start on specific workspaces, you can
\r
343 automatically start applications, you can change the colors of i3, and you
\r
344 can bind your keys to do useful things.</p></div>
\r
345 <div class="paragraph"><p>To change the configuration of i3, copy <tt>/etc/i3/config</tt> to <tt>~/.i3/config</tt>
\r
346 (or <tt>~/.config/i3/config</tt> if you like the XDG directory scheme) and edit it
\r
347 with a text editor.</p></div>
\r
348 <div class="paragraph"><p>On first start (and on all following starts, unless you have a configuration
\r
349 file), i3 will offer you to create a configuration file. You can tell the
\r
350 wizard to use either Alt (Mod1) or Windows (Mod4) as modifier in the config
\r
351 file. Also, the created config file will use the key symbols of your current
\r
352 keyboard layout. To start the wizard, use the command <tt>i3-config-wizard</tt>.
\r
353 Please note that you must not have <tt>~/.i3/config</tt>, otherwise the wizard will
\r
355 <div class="sect2">
\r
356 <h3 id="_comments">4.1. Comments</h3>
\r
357 <div class="paragraph"><p>It is possible and recommended to use comments in your configuration file to
\r
358 properly document your setup for later reference. Comments are started with
\r
359 a # and can only be used at the beginning of a line:</p></div>
\r
360 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
361 <div class="listingblock">
\r
362 <div class="content">
\r
363 <pre><tt># This is a comment</tt></pre>
\r
366 <div class="sect2">
\r
367 <h3 id="fonts">4.2. Fonts</h3>
\r
368 <div class="paragraph"><p>i3 has support for both X core fonts and FreeType fonts (through Pango) to
\r
369 render window titles.</p></div>
\r
370 <div class="paragraph"><p>To generate an X core font description, you can use <tt>xfontsel(1)</tt>. To see
\r
371 special characters (Unicode), you need to use a font which supports the
\r
372 ISO-10646 encoding.</p></div>
\r
373 <div class="paragraph"><p>A FreeType font description is composed by a font family, a style, a weight,
\r
374 a variant, a stretch and a size.
\r
375 FreeType fonts support right-to-left rendering and contain often more
\r
376 Unicode glyphs than X core fonts.</p></div>
\r
377 <div class="paragraph"><p>If i3 cannot open the configured font, it will output an error in the logfile
\r
378 and fall back to a working font.</p></div>
\r
379 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
380 <div class="listingblock">
\r
381 <div class="content">
\r
382 <pre><tt>font <X core font description>
\r
383 font pango:[family list] [style options] [size]</tt></pre>
\r
385 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
386 <div class="listingblock">
\r
387 <div class="content">
\r
388 <pre><tt>font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
\r
389 font pango:DejaVu Sans Mono 10
\r
390 font pango:DejaVu Sans Mono, Terminus Bold Semi-Condensed 11
\r
391 font pango:Terminus 11px</tt></pre>
\r
394 <div class="sect2">
\r
395 <h3 id="keybindings">4.3. Keyboard bindings</h3>
\r
396 <div class="paragraph"><p>A keyboard binding makes i3 execute a command (see below) upon pressing a
\r
397 specific key. i3 allows you to bind either on keycodes or on keysyms (you can
\r
398 also mix your bindings, though i3 will not protect you from overlapping ones).</p></div>
\r
399 <div class="ulist"><ul>
\r
402 A keysym (key symbol) is a description for a specific symbol, like "a"
\r
403 or "b", but also more strange ones like "underscore" instead of "_". These
\r
404 are the ones you use in Xmodmap to remap your keys. To get the current
\r
405 mapping of your keys, use <tt>xmodmap -pke</tt>. To interactively enter a key and
\r
406 see what keysym it is configured to, use <tt>xev</tt>.
\r
411 Keycodes do not need to have a symbol assigned (handy for custom vendor
\r
412 hotkeys on some notebooks) and they will not change their meaning as you
\r
413 switch to a different keyboard layout (when using <tt>xmodmap</tt>).
\r
417 <div class="paragraph"><p>My recommendation is: If you often switch keyboard layouts but you want to keep
\r
418 your bindings in the same physical location on the keyboard, use keycodes.
\r
419 If you don’t switch layouts, and want a clean and simple config file, use
\r
421 <div class="paragraph"><p>Some tools (such as <tt>import</tt> or <tt>xdotool</tt>) might be unable to run upon a
\r
422 KeyPress event, because the keyboard/pointer is still grabbed. For these
\r
423 situations, the <tt>--release</tt> flag can be used, which will execute the command
\r
424 after the keys have been released.</p></div>
\r
425 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
426 <div class="listingblock">
\r
427 <div class="content">
\r
428 <pre><tt>bindsym [--release] [Modifiers+]keysym command
\r
429 bindcode [--release] [Modifiers+]keycode command</tt></pre>
\r
431 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
432 <div class="listingblock">
\r
433 <div class="content">
\r
434 <pre><tt># Fullscreen
\r
435 bindsym $mod+f fullscreen toggle
\r
438 bindsym $mod+Shift+r restart
\r
440 # Notebook-specific hotkeys
\r
441 bindcode 214 exec --no-startup-id /home/michael/toggle_beamer.sh
\r
443 # Simulate ctrl+v upon pressing $mod+x
\r
444 bindsym --release $mod+x exec --no-startup-id xdotool key --clearmodifiers ctrl+v
\r
446 # Take a screenshot upon pressing $mod+x (select an area)
\r
447 bindsym --release $mod+x exec --no-startup-id import /tmp/latest-screenshot.png</tt></pre>
\r
449 <div class="paragraph"><p>Available Modifiers:</p></div>
\r
450 <div class="dlist"><dl>
\r
451 <dt class="hdlist1">
\r
452 Mod1-Mod5, Shift, Control
\r
456 Standard modifiers, see <tt>xmodmap(1)</tt>
\r
459 <dt class="hdlist1">
\r
464 Unlike other window managers, i3 can use Mode_switch as a modifier. This allows
\r
465 you to remap capslock (for example) to Mode_switch and use it for both: typing
\r
466 umlauts or special characters <em>and</em> having some comfortably reachable key
\r
467 bindings. For example, when typing, capslock+1 or capslock+2 for switching
\r
468 workspaces is totally convenient. Try it :-).
\r
473 <div class="sect2">
\r
474 <h3 id="mousebindings">4.4. Mouse bindings</h3>
\r
475 <div class="paragraph"><p>A mouse binding makes i3 execute a command upon pressing a specific mouse
\r
476 button in the scope of the clicked container (see <a href="#command_criteria">[command_criteria]</a>). You
\r
477 can configure mouse bindings in a similar way to key bindings.</p></div>
\r
478 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
479 <div class="listingblock">
\r
480 <div class="content">
\r
481 <pre><tt>bindsym [--release] [--whole-window] [Modifiers+]button[n] command</tt></pre>
\r
483 <div class="paragraph"><p>By default, the binding will only run when you click on the titlebar of the
\r
484 window. If the <tt>--whole-window</tt> flag is given, it will run when any part of the
\r
485 window is clicked. If the <tt>--release</tt> flag is given, it will run when the mouse
\r
486 button is released.</p></div>
\r
487 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
488 <div class="listingblock">
\r
489 <div class="content">
\r
490 <pre><tt># The middle button over a titlebar kills the window
\r
491 bindsym --release button2 kill
\r
493 # The middle button and a modifer over any part of the window kills the window
\r
494 bindsym --whole-window $mod+button2 kill
\r
496 # The right button toggles floating
\r
497 bindsym button3 floating toggle
\r
498 bindsym $mod+button3 floating toggle
\r
500 # The side buttons move the window around
\r
501 bindsym button9 move left
\r
502 bindsym button8 move right</tt></pre>
\r
505 <div class="sect2">
\r
506 <h3 id="floating_modifier">4.5. The floating modifier</h3>
\r
507 <div class="paragraph"><p>To move floating windows with your mouse, you can either grab their titlebar
\r
508 or configure the so called floating modifier which you can then press and
\r
509 click anywhere in the window itself to move it. The most common setup is to
\r
510 use the same key you use for managing windows (Mod1 for example). Then
\r
511 you can press Mod1, click into a window using your left mouse button, and drag
\r
512 it to the position you want.</p></div>
\r
513 <div class="paragraph"><p>When holding the floating modifier, you can resize a floating window by
\r
514 pressing the right mouse button on it and moving around while holding it. If
\r
515 you hold the shift button as well, the resize will be proportional (the aspect
\r
516 ratio will be preserved).</p></div>
\r
517 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
518 <div class="listingblock">
\r
519 <div class="content">
\r
520 <pre><tt>floating_modifier <Modifiers></tt></pre>
\r
522 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
523 <div class="listingblock">
\r
524 <div class="content">
\r
525 <pre><tt>floating_modifier Mod1</tt></pre>
\r
528 <div class="sect2">
\r
529 <h3 id="_constraining_floating_window_size">4.6. Constraining floating window size</h3>
\r
530 <div class="paragraph"><p>The maximum and minimum dimensions of floating windows can be specified. If
\r
531 either dimension of <tt>floating_maximum_size</tt> is specified as -1, that dimension
\r
532 will be unconstrained with respect to its maximum value. If either dimension of
\r
533 <tt>floating_maximum_size</tt> is undefined, or specified as 0, i3 will use a default
\r
534 value to constrain the maximum size. <tt>floating_minimum_size</tt> is treated in a
\r
535 manner analogous to <tt>floating_maximum_size</tt>.</p></div>
\r
536 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
537 <div class="listingblock">
\r
538 <div class="content">
\r
539 <pre><tt>floating_minimum_size <width> x <height>
\r
540 floating_maximum_size <width> x <height></tt></pre>
\r
542 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
543 <div class="listingblock">
\r
544 <div class="content">
\r
545 <pre><tt>floating_minimum_size 75 x 50
\r
546 floating_maximum_size -1 x -1</tt></pre>
\r
549 <div class="sect2">
\r
550 <h3 id="_orientation_for_new_workspaces">4.7. Orientation for new workspaces</h3>
\r
551 <div class="paragraph"><p>New workspaces get a reasonable default orientation: Wide-screen monitors
\r
552 (anything wider than high) get horizontal orientation, rotated monitors
\r
553 (anything higher than wide) get vertical orientation.</p></div>
\r
554 <div class="paragraph"><p>With the <tt>default_orientation</tt> configuration directive, you can override that
\r
555 behavior.</p></div>
\r
556 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
557 <div class="listingblock">
\r
558 <div class="content">
\r
559 <pre><tt>default_orientation <horizontal|vertical|auto></tt></pre>
\r
561 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
562 <div class="listingblock">
\r
563 <div class="content">
\r
564 <pre><tt>default_orientation vertical</tt></pre>
\r
567 <div class="sect2">
\r
568 <h3 id="_layout_mode_for_new_containers">4.8. Layout mode for new containers</h3>
\r
569 <div class="paragraph"><p>This option determines in which mode new containers on workspace level will
\r
571 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
572 <div class="listingblock">
\r
573 <div class="content">
\r
574 <pre><tt>workspace_layout <default|stacking|tabbed></tt></pre>
\r
576 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
577 <div class="listingblock">
\r
578 <div class="content">
\r
579 <pre><tt>workspace_layout tabbed</tt></pre>
\r
582 <div class="sect2">
\r
583 <h3 id="_border_style_for_new_windows">4.9. Border style for new windows</h3>
\r
584 <div class="paragraph"><p>This option determines which border style new windows will have. The default is
\r
585 "normal". Note that new_float applies only to windows which are starting out as
\r
586 floating windows, e.g. dialog windows.</p></div>
\r
587 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
588 <div class="listingblock">
\r
589 <div class="content">
\r
590 <pre><tt>new_window <normal|1pixel|none|pixel>
\r
591 new_float <normal|1pixel|none|pixel></tt></pre>
\r
593 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
594 <div class="listingblock">
\r
595 <div class="content">
\r
596 <pre><tt>new_window 1pixel</tt></pre>
\r
598 <div class="paragraph"><p>The "normal" and "pixel" border styles support an optional border width in
\r
600 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
601 <div class="listingblock">
\r
602 <div class="content">
\r
603 <pre><tt># The same as new_window none
\r
607 new_window pixel 3</tt></pre>
\r
610 <div class="sect2">
\r
611 <h3 id="_hiding_vertical_borders">4.10. Hiding vertical borders</h3>
\r
612 <div class="paragraph"><p>You can hide vertical borders adjacent to the screen edges using
\r
613 <tt>hide_edge_borders</tt>. This is useful if you are using scrollbars, or do not want
\r
614 to waste even two pixels in displayspace. Default is none.</p></div>
\r
615 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
616 <div class="listingblock">
\r
617 <div class="content">
\r
618 <pre><tt>hide_edge_borders <none|vertical|horizontal|both></tt></pre>
\r
620 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
621 <div class="listingblock">
\r
622 <div class="content">
\r
623 <pre><tt>hide_edge_borders vertical</tt></pre>
\r
626 <div class="sect2">
\r
627 <h3 id="_arbitrary_commands_for_specific_windows_for_window">4.11. Arbitrary commands for specific windows (for_window)</h3>
\r
628 <div class="paragraph"><p>With the <tt>for_window</tt> command, you can let i3 execute any command when it
\r
629 encounters a specific window. This can be used to set windows to floating or to
\r
630 change their border style, for example.</p></div>
\r
631 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
632 <div class="listingblock">
\r
633 <div class="content">
\r
634 <pre><tt>for_window <criteria> command</tt></pre>
\r
636 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
637 <div class="listingblock">
\r
638 <div class="content">
\r
639 <pre><tt># enable floating mode for all XTerm windows
\r
640 for_window [class="XTerm"] floating enable
\r
642 # Make all urxvts use a 1-pixel border:
\r
643 for_window [class="urxvt"] border 1pixel
\r
645 # A less useful, but rather funny example:
\r
646 # makes the window floating as soon as I change
\r
647 # directory to ~/work
\r
648 for_window [title="x200: ~/work"] floating enable</tt></pre>
\r
650 <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
652 <div class="sect2">
\r
653 <h3 id="_variables">4.12. Variables</h3>
\r
654 <div class="paragraph"><p>As you learned in the section about keyboard bindings, you will have
\r
655 to configure lots of bindings containing modifier keys. If you want to save
\r
656 yourself some typing and be able to change the modifier you use later,
\r
657 variables can be handy.</p></div>
\r
658 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
659 <div class="listingblock">
\r
660 <div class="content">
\r
661 <pre><tt>set $name value</tt></pre>
\r
663 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
664 <div class="listingblock">
\r
665 <div class="content">
\r
666 <pre><tt>set $m Mod1
\r
667 bindsym $m+Shift+r restart</tt></pre>
\r
669 <div class="paragraph"><p>Variables are directly replaced in the file when parsing. Variables expansion
\r
670 is not recursive so it is not possible to define a variable with a value
\r
671 containing another variable. There is no fancy handling and there are
\r
672 absolutely no plans to change this. If you need a more dynamic configuration
\r
673 you should create a little script which generates a configuration file and run
\r
674 it before starting i3 (for example in your <tt>~/.xsession</tt> file).</p></div>
\r
676 <div class="sect2">
\r
677 <h3 id="_automatically_putting_clients_on_specific_workspaces">4.13. Automatically putting clients on specific workspaces</h3>
\r
678 <div class="paragraph" id="assign_workspace"><p>To automatically make a specific window show up on a specific workspace, you
\r
679 can use an <strong>assignment</strong>. You can match windows by using any criteria,
\r
680 see <a href="#command_criteria">[command_criteria]</a>. It is recommended that you match on window classes
\r
681 (and instances, when appropriate) instead of window titles whenever possible
\r
682 because some applications first create their window, and then worry about
\r
683 setting the correct title. Firefox with Vimperator comes to mind. The window
\r
684 starts up being named Firefox, and only when Vimperator is loaded does the
\r
685 title change. As i3 will get the title as soon as the application maps the
\r
686 window (mapping means actually displaying it on the screen), you’d need to have
\r
687 to match on <em>Firefox</em> in this case.</p></div>
\r
688 <div class="paragraph"><p>Assignments are processed by i3 in the order in which they appear in the config
\r
689 file. The first one which matches the window wins and later assignments are not
\r
690 considered.</p></div>
\r
691 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
692 <div class="listingblock">
\r
693 <div class="content">
\r
694 <pre><tt>assign <criteria> [→] workspace</tt></pre>
\r
696 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
697 <div class="listingblock">
\r
698 <div class="content">
\r
699 <pre><tt># Assign URxvt terminals to workspace 2
\r
700 assign [class="URxvt"] 2
\r
702 # Same thing, but more precise (exact match instead of substring)
\r
703 assign [class="^URxvt$"] 2
\r
705 # Same thing, but with a beautiful arrow :)
\r
706 assign [class="^URxvt$"] → 2
\r
708 # Assignment to a named workspace
\r
709 assign [class="^URxvt$"] → work
\r
711 # Start urxvt -name irssi
\r
712 assign [class="^URxvt$" instance="^irssi$"] → 3</tt></pre>
\r
714 <div class="paragraph"><p>Note that the arrow is not required, it just looks good :-). If you decide to
\r
715 use it, it has to be a UTF-8 encoded arrow, not <tt>-></tt> or something like that.</p></div>
\r
716 <div class="paragraph"><p>To get the class and instance, you can use <tt>xprop</tt>. After clicking on the
\r
717 window, you will see the following output:</p></div>
\r
718 <div class="paragraph"><p><strong>xprop</strong>:</p></div>
\r
719 <div class="listingblock">
\r
720 <div class="content">
\r
721 <pre><tt>WM_CLASS(STRING) = "irssi", "URxvt"</tt></pre>
\r
723 <div class="paragraph"><p>The first part of the WM_CLASS is the instance ("irssi" in this example), the
\r
724 second part is the class ("URxvt" in this example).</p></div>
\r
725 <div class="paragraph"><p>Should you have any problems with assignments, make sure to check the i3
\r
726 logfile first (see <a href="http://i3wm.org/docs/debugging.html">http://i3wm.org/docs/debugging.html</a>). It includes more
\r
727 details about the matching process and the window’s actual class, instance and
\r
728 title when starting up.</p></div>
\r
729 <div class="paragraph"><p>Note that if you want to start an application just once on a specific
\r
730 workspace, but you don’t want to assign all instances of it permanently, you
\r
731 can make use of i3’s startup-notification support (see <a href="#exec">[exec]</a>) in your config
\r
732 file in the following way:</p></div>
\r
733 <div class="paragraph"><p><strong>Start iceweasel on workspace 3 (once)</strong>:</p></div>
\r
734 <div class="listingblock">
\r
735 <div class="content">
\r
736 <pre><tt># Start iceweasel on workspace 3, then switch back to workspace 1
\r
737 # (Being a command-line utility, i3-msg does not support startup notifications,
\r
738 # hence the exec --no-startup-id.)
\r
739 # (Starting iceweasel with i3’s exec command is important in order to make i3
\r
740 # create a startup notification context, without which the iceweasel window(s)
\r
741 # cannot be matched onto the workspace on which the command was started.)
\r
742 exec --no-startup-id i3-msg 'workspace 3; exec iceweasel; workspace 1'</tt></pre>
\r
745 <div class="sect2">
\r
746 <h3 id="_automatically_starting_applications_on_i3_startup">4.14. Automatically starting applications on i3 startup</h3>
\r
747 <div class="paragraph"><p>By using the <tt>exec</tt> keyword outside a keybinding, you can configure
\r
748 which commands will be performed by i3 on initial startup. <tt>exec</tt>
\r
749 commands will not run when restarting i3, if you need a command to run
\r
750 also when restarting i3 you should use the <tt>exec_always</tt>
\r
751 keyword. These commands will be run in order.</p></div>
\r
752 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
753 <div class="listingblock">
\r
754 <div class="content">
\r
755 <pre><tt>exec [--no-startup-id] command
\r
756 exec_always [--no-startup-id] command</tt></pre>
\r
758 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
759 <div class="listingblock">
\r
760 <div class="content">
\r
761 <pre><tt>exec chromium
\r
762 exec_always ~/my_script.sh
\r
764 # Execute the terminal emulator urxvt, which is not yet startup-notification aware.
\r
765 exec --no-startup-id urxvt</tt></pre>
\r
767 <div class="paragraph"><p>The flag --no-startup-id is explained in <a href="#exec">[exec]</a>.</p></div>
\r
769 <div class="sect2">
\r
770 <h3 id="workspace_screen">4.15. Automatically putting workspaces on specific screens</h3>
\r
771 <div class="paragraph"><p>If you assign clients to workspaces, it might be handy to put the
\r
772 workspaces on specific screens. Also, the assignment of workspaces to screens
\r
773 will determine which workspace i3 uses for a new screen when adding screens
\r
774 or when starting (e.g., by default it will use 1 for the first screen, 2 for
\r
775 the second screen and so on).</p></div>
\r
776 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
777 <div class="listingblock">
\r
778 <div class="content">
\r
779 <pre><tt>workspace <workspace> output <output></tt></pre>
\r
781 <div class="paragraph"><p>The <em>output</em> is the name of the RandR output you attach your screen to. On a
\r
782 laptop, you might have VGA1 and LVDS1 as output names. You can see the
\r
783 available outputs by running <tt>xrandr --current</tt>.</p></div>
\r
784 <div class="paragraph"><p>If you use named workspaces, they must be quoted:</p></div>
\r
785 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
786 <div class="listingblock">
\r
787 <div class="content">
\r
788 <pre><tt>workspace 1 output LVDS1
\r
789 workspace 5 output VGA1
\r
790 workspace "2: vim" output VGA1</tt></pre>
\r
793 <div class="sect2">
\r
794 <h3 id="_changing_colors">4.16. Changing colors</h3>
\r
795 <div class="paragraph"><p>You can change all colors which i3 uses to draw the window decorations.</p></div>
\r
796 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
797 <div class="listingblock">
\r
798 <div class="content">
\r
799 <pre><tt>colorclass border background text indicator</tt></pre>
\r
801 <div class="paragraph"><p>Where colorclass can be one of:</p></div>
\r
802 <div class="dlist"><dl>
\r
803 <dt class="hdlist1">
\r
808 A client which currently has the focus.
\r
811 <dt class="hdlist1">
\r
812 client.focused_inactive
\r
816 A client which is the focused one of its container, but it does not have
\r
817 the focus at the moment.
\r
820 <dt class="hdlist1">
\r
825 A client which is not the focused one of its container.
\r
828 <dt class="hdlist1">
\r
833 A client which has its urgency hint activated.
\r
836 <dt class="hdlist1">
\r
841 Background and text color are used to draw placeholder window contents
\r
842 (when restoring layouts). Border and indicator are ignored.
\r
846 <div class="paragraph"><p>You can also specify the color to be used to paint the background of the client
\r
847 windows. This color will be used to paint the window on top of which the client
\r
848 will be rendered.</p></div>
\r
849 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
850 <div class="listingblock">
\r
851 <div class="content">
\r
852 <pre><tt>client.background color</tt></pre>
\r
854 <div class="paragraph"><p>Only clients that do not cover the whole area of this window expose the color
\r
855 used to paint it.</p></div>
\r
856 <div class="paragraph"><p>Colors are in HTML hex format (#rrggbb), see the following example:</p></div>
\r
857 <div class="paragraph"><p><strong>Examples (default colors)</strong>:</p></div>
\r
858 <div class="listingblock">
\r
859 <div class="content">
\r
860 <pre><tt># class border backgr. text indicator
\r
861 client.focused #4c7899 #285577 #ffffff #2e9ef4
\r
862 client.focused_inactive #333333 #5f676a #ffffff #484e50
\r
863 client.unfocused #333333 #222222 #888888 #292d2e
\r
864 client.urgent #2f343a #900000 #ffffff #900000
\r
865 client.placeholder #000000 #0c0c0c #ffffff #000000</tt></pre>
\r
867 <div class="paragraph"><p>Note that for the window decorations, the color around the child window is the
\r
868 background color, and the border color is only the two thin lines at the top of
\r
869 the window.</p></div>
\r
870 <div class="paragraph"><p>The indicator color is used for indicating where a new window will be opened.
\r
871 For horizontal split containers, the right border will be painted in indicator
\r
872 color, for vertical split containers, the bottom border. This only applies to
\r
873 single windows within a split container, which are otherwise indistinguishable
\r
874 from single windows outside of a split container.</p></div>
\r
876 <div class="sect2">
\r
877 <h3 id="_interprocess_communication">4.17. Interprocess communication</h3>
\r
878 <div class="paragraph"><p>i3 uses Unix sockets to provide an IPC interface. This allows third-party
\r
879 programs to get information from i3, such as the current workspaces
\r
880 (to display a workspace bar), and to control i3.</p></div>
\r
881 <div class="paragraph"><p>The IPC socket is enabled by default and will be created in
\r
882 <tt>/tmp/i3-%u.XXXXXX/ipc-socket.%p</tt> where <tt>%u</tt> is your UNIX username, <tt>%p</tt> is
\r
883 the PID of i3 and XXXXXX is a string of random characters from the portable
\r
884 filename character set (see mkdtemp(3)).</p></div>
\r
885 <div class="paragraph"><p>You can override the default path through the environment-variable <tt>I3SOCK</tt> or
\r
886 by specifying the <tt>ipc-socket</tt> directive. This is discouraged, though, since i3
\r
887 does the right thing by default. If you decide to change it, it is strongly
\r
888 recommended to set this to a location in your home directory so that no other
\r
889 user can create that directory.</p></div>
\r
890 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
891 <div class="listingblock">
\r
892 <div class="content">
\r
893 <pre><tt>ipc-socket ~/.i3/i3-ipc.sock</tt></pre>
\r
895 <div class="paragraph"><p>You can then use the <tt>i3-msg</tt> application to perform any command listed in
\r
896 the next section.</p></div>
\r
898 <div class="sect2">
\r
899 <h3 id="_focus_follows_mouse">4.18. Focus follows mouse</h3>
\r
900 <div class="paragraph"><p>By default, window focus follows your mouse movements. However, if you have a
\r
901 setup where your mouse usually is in your way (like a touchpad on your laptop
\r
902 which you do not want to disable completely), you might want to disable <em>focus
\r
903 follows mouse</em> and control focus only by using your keyboard. The mouse will
\r
904 still be useful inside the currently active window (for example to click on
\r
905 links in your browser window).</p></div>
\r
906 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
907 <div class="listingblock">
\r
908 <div class="content">
\r
909 <pre><tt>focus_follows_mouse <yes|no></tt></pre>
\r
911 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
912 <div class="listingblock">
\r
913 <div class="content">
\r
914 <pre><tt>focus_follows_mouse no</tt></pre>
\r
917 <div class="sect2">
\r
918 <h3 id="_mouse_warping">4.19. Mouse warping</h3>
\r
919 <div class="paragraph"><p>By default, when switching focus to a window on a different output (e.g.
\r
920 focusing a window on workspace 3 on output VGA-1, coming from workspace 2 on
\r
921 LVDS-1), the mouse cursor is warped to the center of that window.</p></div>
\r
922 <div class="paragraph"><p>With the <tt>mouse_warping</tt> option, you can control when the mouse cursor should
\r
923 be warped. <tt>none</tt> disables warping entirely, whereas <tt>output</tt> is the default
\r
924 behavior described above.</p></div>
\r
925 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
926 <div class="listingblock">
\r
927 <div class="content">
\r
928 <pre><tt>mouse_warping <output|none></tt></pre>
\r
930 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
931 <div class="listingblock">
\r
932 <div class="content">
\r
933 <pre><tt>mouse_warping none</tt></pre>
\r
936 <div class="sect2">
\r
937 <h3 id="_popups_during_fullscreen_mode">4.20. Popups during fullscreen mode</h3>
\r
938 <div class="paragraph"><p>When you are in fullscreen mode, some applications still open popup windows
\r
939 (take Xpdf for example). This is because these applications may not be aware
\r
940 that they are in fullscreen mode (they do not check the corresponding hint).
\r
941 There are three things which are possible to do in this situation:</p></div>
\r
942 <div class="olist arabic"><ol class="arabic">
\r
945 Display the popup if it belongs to the fullscreen application only. This is
\r
946 the default and should be reasonable behavior for most users.
\r
951 Just ignore the popup (don’t map it). This won’t interrupt you while you are
\r
952 in fullscreen. However, some apps might react badly to this (deadlock until
\r
953 you go out of fullscreen).
\r
958 Leave fullscreen mode.
\r
962 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
963 <div class="listingblock">
\r
964 <div class="content">
\r
965 <pre><tt>popup_during_fullscreen <smart|ignore|leave_fullscreen></tt></pre>
\r
967 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
968 <div class="listingblock">
\r
969 <div class="content">
\r
970 <pre><tt>popup_during_fullscreen smart</tt></pre>
\r
973 <div class="sect2">
\r
974 <h3 id="_focus_wrapping">4.21. Focus wrapping</h3>
\r
975 <div class="paragraph"><p>When being in a tabbed or stacked container, the first container will be
\r
976 focused when you use <tt>focus down</tt> on the last container — the focus wraps. If
\r
977 however there is another stacked/tabbed container in that direction, focus will
\r
978 be set on that container. This is the default behavior so you can navigate to
\r
979 all your windows without having to use <tt>focus parent</tt>.</p></div>
\r
980 <div class="paragraph"><p>If you want the focus to <strong>always</strong> wrap and you are aware of using <tt>focus
\r
981 parent</tt> to switch to different containers, you can use the
\r
982 <tt>force_focus_wrapping</tt> configuration directive. After enabling it, the focus
\r
983 will always wrap.</p></div>
\r
984 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
985 <div class="listingblock">
\r
986 <div class="content">
\r
987 <pre><tt>force_focus_wrapping <yes|no></tt></pre>
\r
989 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
990 <div class="listingblock">
\r
991 <div class="content">
\r
992 <pre><tt>force_focus_wrapping yes</tt></pre>
\r
995 <div class="sect2">
\r
996 <h3 id="_forcing_xinerama">4.22. Forcing Xinerama</h3>
\r
997 <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
998 video drivers (especially the nVidia binary driver) only provide support for
\r
999 Xinerama instead of RandR. In such a situation, i3 must be told to use the
\r
1000 inferior Xinerama API explicitly and therefore don’t provide support for
\r
1001 reconfiguring your screens on the fly (they are read only once on startup and
\r
1002 that’s it).</p></div>
\r
1003 <div class="paragraph"><p>For people who cannot modify their <tt>~/.xsession</tt> to add the
\r
1004 <tt>--force-xinerama</tt> commandline parameter, a configuration option is provided:</p></div>
\r
1005 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1006 <div class="listingblock">
\r
1007 <div class="content">
\r
1008 <pre><tt>force_xinerama <yes|no></tt></pre>
\r
1010 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1011 <div class="listingblock">
\r
1012 <div class="content">
\r
1013 <pre><tt>force_xinerama yes</tt></pre>
\r
1015 <div class="paragraph"><p>Also note that your output names are not descriptive (like <tt>HDMI1</tt>) when using
\r
1016 Xinerama, instead they are counted up, starting at 0: <tt>xinerama-0</tt>, <tt>xinerama-1</tt>, …</p></div>
\r
1018 <div class="sect2">
\r
1019 <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
1020 <div class="paragraph"><p>This configuration directive enables automatic <tt>workspace back_and_forth</tt> (see
\r
1021 <a href="#back_and_forth">[back_and_forth]</a>) when switching to the workspace that is currently focused.</p></div>
\r
1022 <div class="paragraph"><p>For instance: Assume you are on workspace "1: www" and switch to "2: IM" using
\r
1023 mod+2 because somebody sent you a message. You don’t need to remember where you
\r
1024 came from now, you can just press $mod+2 again to switch back to "1: www".</p></div>
\r
1025 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1026 <div class="listingblock">
\r
1027 <div class="content">
\r
1028 <pre><tt>workspace_auto_back_and_forth <yes|no></tt></pre>
\r
1030 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1031 <div class="listingblock">
\r
1032 <div class="content">
\r
1033 <pre><tt>workspace_auto_back_and_forth yes</tt></pre>
\r
1036 <div class="sect2">
\r
1037 <h3 id="_delaying_urgency_hint_reset_on_workspace_change">4.24. Delaying urgency hint reset on workspace change</h3>
\r
1038 <div class="paragraph"><p>If an application on another workspace sets an urgency hint, switching to this
\r
1039 workspace may lead to immediate focus of the application, which also means the
\r
1040 window decoration color would be immediately reset to <tt>client.focused</tt>. This
\r
1041 may make it unnecessarily hard to tell which window originally raised the
\r
1043 <div class="paragraph"><p>In order to prevent this, you can tell i3 to delay resetting the urgency state
\r
1044 by a certain time using the <tt>force_display_urgency_hint</tt> directive. Setting the
\r
1045 value to 0 disables this feature.</p></div>
\r
1046 <div class="paragraph"><p>The default is 500ms.</p></div>
\r
1047 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1048 <div class="listingblock">
\r
1049 <div class="content">
\r
1050 <pre><tt>force_display_urgency_hint <timeout> ms</tt></pre>
\r
1052 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1053 <div class="listingblock">
\r
1054 <div class="content">
\r
1055 <pre><tt>force_display_urgency_hint 500 ms</tt></pre>
\r
1060 <div class="sect1">
\r
1061 <h2 id="_configuring_i3bar">5. Configuring i3bar</h2>
\r
1062 <div class="sectionbody">
\r
1063 <div class="paragraph"><p>The bar at the bottom of your monitor is drawn by a separate process called
\r
1064 i3bar. Having this part of "the i3 user interface" in a separate process has
\r
1065 several advantages:</p></div>
\r
1066 <div class="olist arabic"><ol class="arabic">
\r
1069 It is a modular approach. If you don’t need a workspace bar at all, or if
\r
1070 you prefer a different one (dzen2, xmobar, maybe even gnome-panel?), you can
\r
1071 just remove the i3bar configuration and start your favorite bar instead.
\r
1076 It follows the UNIX philosophy of "Make each program do one thing well".
\r
1077 While i3 manages your windows well, i3bar is good at displaying a bar on
\r
1078 each monitor (unless you configure it otherwise).
\r
1083 It leads to two separate, clean codebases. If you want to understand i3, you
\r
1084 don’t need to bother with the details of i3bar and vice versa.
\r
1088 <div class="paragraph"><p>That said, i3bar is configured in the same configuration file as i3. This is
\r
1089 because it is tightly coupled with i3 (in contrary to i3lock or i3status which
\r
1090 are useful for people using other window managers). Therefore, it makes no
\r
1091 sense to use a different configuration place when we already have a good
\r
1092 configuration infrastructure in place.</p></div>
\r
1093 <div class="paragraph"><p>Configuring your workspace bar starts with opening a <tt>bar</tt> block. You can have
\r
1094 multiple bar blocks to use different settings for different outputs (monitors):</p></div>
\r
1095 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1096 <div class="listingblock">
\r
1097 <div class="content">
\r
1099 status_command i3status
\r
1102 <div class="sect2">
\r
1103 <h3 id="_i3bar_command">5.1. i3bar command</h3>
\r
1104 <div class="paragraph"><p>By default i3 will just pass <tt>i3bar</tt> and let your shell handle the execution,
\r
1105 searching your <tt>$PATH</tt> for a correct version.
\r
1106 If you have a different <tt>i3bar</tt> somewhere or the binary is not in your <tt>$PATH</tt> you can
\r
1107 tell i3 what to execute.</p></div>
\r
1108 <div class="paragraph"><p>The specified command will be passed to <tt>sh -c</tt>, so you can use globbing and
\r
1109 have to have correct quoting etc.</p></div>
\r
1110 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1111 <div class="listingblock">
\r
1112 <div class="content">
\r
1113 <pre><tt>i3bar_command command</tt></pre>
\r
1115 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1116 <div class="listingblock">
\r
1117 <div class="content">
\r
1119 i3bar_command /home/user/bin/i3bar
\r
1123 <div class="sect2">
\r
1124 <h3 id="status_command">5.2. Statusline command</h3>
\r
1125 <div class="paragraph"><p>i3bar can run a program and display every line of its <tt>stdout</tt> output on the
\r
1126 right hand side of the bar. This is useful to display system information like
\r
1127 your current IP address, battery status or date/time.</p></div>
\r
1128 <div class="paragraph"><p>The specified command will be passed to <tt>sh -c</tt>, so you can use globbing and
\r
1129 have to have correct quoting etc.</p></div>
\r
1130 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1131 <div class="listingblock">
\r
1132 <div class="content">
\r
1133 <pre><tt>status_command command</tt></pre>
\r
1135 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1136 <div class="listingblock">
\r
1137 <div class="content">
\r
1139 status_command i3status --config ~/.i3status.conf
\r
1143 <div class="sect2">
\r
1144 <h3 id="_display_mode">5.3. Display mode</h3>
\r
1145 <div class="paragraph"><p>You can either have i3bar be visible permanently at one edge of the screen
\r
1146 (<tt>dock</tt> mode) or make it show up when you press your modifier key (<tt>hide</tt> mode).
\r
1147 It is also possible to force i3bar to always stay hidden (<tt>invisible</tt>
\r
1148 mode). The modifier key can be configured using the <tt>modifier</tt> option.</p></div>
\r
1149 <div class="paragraph"><p>The mode option can be changed during runtime through the <tt>bar mode</tt> command.
\r
1150 On reload the mode will be reverted to its configured value.</p></div>
\r
1151 <div class="paragraph"><p>The hide mode maximizes screen space that can be used for actual windows. Also,
\r
1152 i3bar sends the <tt>SIGSTOP</tt> and <tt>SIGCONT</tt> signals to the statusline process to
\r
1153 save battery power.</p></div>
\r
1154 <div class="paragraph"><p>Invisible mode allows to permanently maximize screen space, as the bar is never
\r
1155 shown. Thus, you can configure i3bar to not disturb you by popping up because
\r
1156 of an urgency hint or because the modifier key is pressed.</p></div>
\r
1157 <div class="paragraph"><p>In order to control whether i3bar is hidden or shown in hide mode, there exists
\r
1158 the hidden_state option, which has no effect in dock mode or invisible mode. It
\r
1159 indicates the current hidden_state of the bar: (1) The bar acts like in normal
\r
1160 hide mode, it is hidden and is only unhidden in case of urgency hints or by
\r
1161 pressing the modifier key (<tt>hide</tt> state), or (2) it is drawn on top of the
\r
1162 currently visible workspace (<tt>show</tt> state).</p></div>
\r
1163 <div class="paragraph"><p>Like the mode, the hidden_state can also be controlled through i3, this can be
\r
1164 done by using the <tt>bar hidden_state</tt> command.</p></div>
\r
1165 <div class="paragraph"><p>The default mode is dock mode; in hide mode, the default modifier is Mod4 (usually
\r
1166 the windows key). The default value for the hidden_state is hide.</p></div>
\r
1167 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1168 <div class="listingblock">
\r
1169 <div class="content">
\r
1170 <pre><tt>mode <dock|hide|invisible>
\r
1171 hidden_state <hide|show>
\r
1172 modifier <Modifier></tt></pre>
\r
1174 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1175 <div class="listingblock">
\r
1176 <div class="content">
\r
1183 <div class="paragraph"><p>Available modifiers are Mod1-Mod5, Shift, Control (see <tt>xmodmap(1)</tt>).</p></div>
\r
1185 <div class="sect2">
\r
1186 <h3 id="_mouse_button_commands">5.4. Mouse button commands</h3>
\r
1187 <div class="paragraph"><p>Specifies a command to run when a button was pressed on i3bar to override the
\r
1188 default behavior. Currently only the mouse wheel buttons are supported. This is
\r
1189 useful for disabling the scroll wheel action or running scripts that implement
\r
1190 custom behavior for these buttons.</p></div>
\r
1191 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1192 <div class="listingblock">
\r
1193 <div class="content">
\r
1194 <pre><tt>wheel_up_cmd <command>
\r
1195 wheel_down_cmd <command></tt></pre>
\r
1197 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1198 <div class="listingblock">
\r
1199 <div class="content">
\r
1202 wheel_down_cmd exec ~/.i3/scripts/custom_wheel_down
\r
1206 <div class="sect2">
\r
1207 <h3 id="_bar_id">5.5. Bar ID</h3>
\r
1208 <div class="paragraph"><p>Specifies the bar ID for the configured bar instance. If this option is missing,
\r
1209 the ID is set to <em>bar-x</em>, where x corresponds to the position of the embedding
\r
1210 bar block in the config file (<em>bar-0</em>, <em>bar-1</em>, …).</p></div>
\r
1211 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1212 <div class="listingblock">
\r
1213 <div class="content">
\r
1214 <pre><tt>id <bar_id></tt></pre>
\r
1216 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1217 <div class="listingblock">
\r
1218 <div class="content">
\r
1224 <div class="sect2">
\r
1225 <h3 id="i3bar_position">5.6. Position</h3>
\r
1226 <div class="paragraph"><p>This option determines in which edge of the screen i3bar should show up.</p></div>
\r
1227 <div class="paragraph"><p>The default is bottom.</p></div>
\r
1228 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1229 <div class="listingblock">
\r
1230 <div class="content">
\r
1231 <pre><tt>position <top|bottom></tt></pre>
\r
1233 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1234 <div class="listingblock">
\r
1235 <div class="content">
\r
1241 <div class="sect2">
\r
1242 <h3 id="_output_s">5.7. Output(s)</h3>
\r
1243 <div class="paragraph"><p>You can restrict i3bar to one or more outputs (monitors). The default is to
\r
1244 handle all outputs. Restricting the outputs is useful for using different
\r
1245 options for different outputs by using multiple <em>bar</em> blocks.</p></div>
\r
1246 <div class="paragraph"><p>To make a particular i3bar instance handle multiple outputs, specify the output
\r
1247 directive multiple times.</p></div>
\r
1248 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1249 <div class="listingblock">
\r
1250 <div class="content">
\r
1251 <pre><tt>output <output></tt></pre>
\r
1253 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1254 <div class="listingblock">
\r
1255 <div class="content">
\r
1256 <pre><tt># big monitor: everything
\r
1258 # The display is connected either via HDMI or via DisplayPort
\r
1261 status_command i3status
\r
1264 # laptop monitor: bright colors and i3status with less modules.
\r
1267 status_command i3status --config ~/.i3status-small.conf
\r
1269 background #000000
\r
1270 statusline #ffffff
\r
1275 <div class="sect2">
\r
1276 <h3 id="_tray_output">5.8. Tray output</h3>
\r
1277 <div class="paragraph"><p>i3bar by default provides a system tray area where programs such as
\r
1278 NetworkManager, VLC, Pidgin, etc. can place little icons.</p></div>
\r
1279 <div class="paragraph"><p>You can configure on which output (monitor) the icons should be displayed or
\r
1280 you can turn off the functionality entirely.</p></div>
\r
1281 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1282 <div class="listingblock">
\r
1283 <div class="content">
\r
1284 <pre><tt>tray_output <none|primary|output></tt></pre>
\r
1286 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1287 <div class="listingblock">
\r
1288 <div class="content">
\r
1289 <pre><tt># disable system tray
\r
1294 # show tray icons on the primary monitor
\r
1295 tray_output primary
\r
1297 # show tray icons on the big monitor
\r
1302 <div class="paragraph"><p>Note that you might not have a primary output configured yet. To do so, run:</p></div>
\r
1303 <div class="listingblock">
\r
1304 <div class="content">
\r
1305 <pre><tt>xrandr --output <output> --primary</tt></pre>
\r
1308 <div class="sect2">
\r
1309 <h3 id="_font">5.9. Font</h3>
\r
1310 <div class="paragraph"><p>Specifies the font to be used in the bar. See <a href="#fonts">[fonts]</a>.</p></div>
\r
1311 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1312 <div class="listingblock">
\r
1313 <div class="content">
\r
1314 <pre><tt>font <font></tt></pre>
\r
1316 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1317 <div class="listingblock">
\r
1318 <div class="content">
\r
1320 font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
\r
1321 font pango:DejaVu Sans Mono 10
\r
1325 <div class="sect2">
\r
1326 <h3 id="_custom_separator_symbol">5.10. Custom separator symbol</h3>
\r
1327 <div class="paragraph"><p>Specifies a custom symbol to be used for the separator as opposed to the vertical,
\r
1328 one pixel thick separator.</p></div>
\r
1329 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1330 <div class="listingblock">
\r
1331 <div class="content">
\r
1332 <pre><tt>separator_symbol <symbol></tt></pre>
\r
1334 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1335 <div class="listingblock">
\r
1336 <div class="content">
\r
1338 separator_symbol ":|:"
\r
1342 <div class="sect2">
\r
1343 <h3 id="_workspace_buttons">5.11. Workspace buttons</h3>
\r
1344 <div class="paragraph"><p>Specifies whether workspace buttons should be shown or not. This is useful if
\r
1345 you want to display a statusline-only bar containing additional information.</p></div>
\r
1346 <div class="paragraph"><p>The default is to show workspace buttons.</p></div>
\r
1347 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1348 <div class="listingblock">
\r
1349 <div class="content">
\r
1350 <pre><tt>workspace_buttons <yes|no></tt></pre>
\r
1352 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1353 <div class="listingblock">
\r
1354 <div class="content">
\r
1356 workspace_buttons no
\r
1360 <div class="sect2">
\r
1361 <h3 id="_strip_workspace_numbers">5.12. Strip workspace numbers</h3>
\r
1362 <div class="paragraph"><p>Specifies whether workspace numbers should be displayed within the workspace
\r
1363 buttons. This is useful if you want to have a named workspace that stays in
\r
1364 order on the bar according to its number without displaying the number prefix.</p></div>
\r
1365 <div class="paragraph"><p>When <tt>strip_workspace_numbers</tt> is set to <tt>yes</tt>, any workspace that has a name of
\r
1366 the form "[n]:[NAME]" will display only the name. You could use this, for
\r
1367 instance, to display Roman numerals rather than digits by naming your
\r
1368 workspaces to "1:I", "2:II", "3:III", "4:IV", …</p></div>
\r
1369 <div class="paragraph"><p>The default is to display the full name within the workspace button.</p></div>
\r
1370 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1371 <div class="listingblock">
\r
1372 <div class="content">
\r
1373 <pre><tt>strip_workspace_numbers <yes|no></tt></pre>
\r
1375 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1376 <div class="listingblock">
\r
1377 <div class="content">
\r
1379 strip_workspace_numbers yes
\r
1383 <div class="sect2">
\r
1384 <h3 id="_binding_mode_indicator">5.13. Binding Mode indicator</h3>
\r
1385 <div class="paragraph"><p>Specifies whether the current binding mode indicator should be shown or not.
\r
1386 This is useful if you want to hide the workspace buttons but still be able
\r
1387 to see the current binding mode indicator.
\r
1388 For an example of a <tt>mode</tt> definition, see <a href="#resizingconfig">[resizingconfig]</a>.</p></div>
\r
1389 <div class="paragraph"><p>The default is to show the mode indicator.</p></div>
\r
1390 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1391 <div class="listingblock">
\r
1392 <div class="content">
\r
1393 <pre><tt>binding_mode_indicator <yes|no></tt></pre>
\r
1395 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1396 <div class="listingblock">
\r
1397 <div class="content">
\r
1399 binding_mode_indicator no
\r
1403 <div class="sect2">
\r
1404 <h3 id="_colors">5.14. Colors</h3>
\r
1405 <div class="paragraph"><p>As with i3, colors are in HTML hex format (#rrggbb). The following colors can
\r
1406 be configured at the moment:</p></div>
\r
1407 <div class="dlist"><dl>
\r
1408 <dt class="hdlist1">
\r
1413 Background color of the bar.
\r
1416 <dt class="hdlist1">
\r
1421 Text color to be used for the statusline.
\r
1424 <dt class="hdlist1">
\r
1429 Text color to be used for the separator.
\r
1432 <dt class="hdlist1">
\r
1437 Border, background and text color for a workspace button when the workspace
\r
1441 <dt class="hdlist1">
\r
1446 Border, background and text color for a workspace button when the workspace
\r
1447 is active (visible) on some output, but the focus is on another one.
\r
1448 You can only tell this apart from the focused workspace when you are
\r
1449 using multiple monitors.
\r
1452 <dt class="hdlist1">
\r
1453 inactive_workspace
\r
1457 Border, background and text color for a workspace button when the workspace
\r
1458 does not have focus and is not active (visible) on any output. This
\r
1459 will be the case for most workspaces.
\r
1462 <dt class="hdlist1">
\r
1467 Border, background and text color for a workspace button when the workspace
\r
1468 contains a window with the urgency hint set. Also applies to <tt>mode</tt> indicators.
\r
1472 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1473 <div class="listingblock">
\r
1474 <div class="content">
\r
1476 background <color>
\r
1477 statusline <color>
\r
1478 separator <color>
\r
1480 colorclass <border> <background> <text>
\r
1483 <div class="paragraph"><p><strong>Example (default colors)</strong>:</p></div>
\r
1484 <div class="listingblock">
\r
1485 <div class="content">
\r
1488 background #000000
\r
1489 statusline #ffffff
\r
1492 focused_workspace #4c7899 #285577 #ffffff
\r
1493 active_workspace #333333 #5f676a #ffffff
\r
1494 inactive_workspace #333333 #222222 #888888
\r
1495 urgent_workspace #2f343a #900000 #ffffff
\r
1502 <div class="sect1">
\r
1503 <h2 id="_list_of_commands">6. List of commands</h2>
\r
1504 <div class="sectionbody">
\r
1505 <div class="paragraph"><p>Commands are what you bind to specific keypresses. You can also issue commands
\r
1506 at runtime without pressing a key by using the IPC interface. An easy way to
\r
1507 do this is to use the <tt>i3-msg</tt> utility:</p></div>
\r
1508 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1509 <div class="listingblock">
\r
1510 <div class="content">
\r
1511 <pre><tt># execute this on your shell to make the current container borderless
\r
1512 i3-msg border none</tt></pre>
\r
1514 <div class="paragraph"><p>Commands can be chained by using <tt>;</tt> (a semicolon). So, to move a window to a
\r
1515 specific workspace and immediately switch to that workspace, you can configure
\r
1516 the following keybinding:</p></div>
\r
1517 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1518 <div class="listingblock">
\r
1519 <div class="content">
\r
1520 <pre><tt>bindsym $mod+x move container to workspace 3; workspace 3</tt></pre>
\r
1522 <div class="paragraph" id="command_criteria"><p>Furthermore, you can change the scope of a command - that is, which containers
\r
1523 should be affected by that command, by using various criteria. The criteria
\r
1524 are specified before any command in a pair of square brackets and are separated
\r
1525 by space.</p></div>
\r
1526 <div class="paragraph"><p>When using multiple commands, separate them by using a <tt>,</tt> (a comma) instead of
\r
1527 a semicolon. Criteria apply only until the next semicolon, so if you use a
\r
1528 semicolon to separate commands, only the first one will be executed for the
\r
1529 matched window(s).</p></div>
\r
1530 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1531 <div class="listingblock">
\r
1532 <div class="content">
\r
1533 <pre><tt># if you want to kill all windows which have the class Firefox, use:
\r
1534 bindsym $mod+x [class="Firefox"] kill
\r
1536 # same thing, but case-insensitive
\r
1537 bindsym $mod+x [class="(?i)firefox"] kill
\r
1539 # kill only the About dialog from Firefox
\r
1540 bindsym $mod+x [class="Firefox" window_role="About"] kill
\r
1542 # enable floating mode and move container to workspace 4
\r
1543 for_window [class="^evil-app$"] floating enable, move container to workspace 4</tt></pre>
\r
1545 <div class="paragraph"><p>The criteria which are currently implemented are:</p></div>
\r
1546 <div class="dlist"><dl>
\r
1547 <dt class="hdlist1">
\r
1552 Compares the window class (the second part of WM_CLASS)
\r
1555 <dt class="hdlist1">
\r
1560 Compares the window instance (the first part of WM_CLASS)
\r
1563 <dt class="hdlist1">
\r
1568 Compares the window role (WM_WINDOW_ROLE).
\r
1571 <dt class="hdlist1">
\r
1576 Compares the X11 window ID, which you can get via <tt>xwininfo</tt> for example.
\r
1579 <dt class="hdlist1">
\r
1584 Compares the X11 window title (_NET_WM_NAME or WM_NAME as fallback).
\r
1587 <dt class="hdlist1">
\r
1592 Compares the urgent state of the window. Can be "latest" or "oldest".
\r
1593 Matches the latest or oldest urgent window, respectively.
\r
1594 (The following aliases are also available: newest, last, recent, first)
\r
1597 <dt class="hdlist1">
\r
1602 Compares the mark set for this container, see <a href="#vim_like_marks">[vim_like_marks]</a>.
\r
1605 <dt class="hdlist1">
\r
1610 Compares the i3-internal container ID, which you can get via the IPC
\r
1611 interface. Handy for scripting.
\r
1615 <div class="paragraph"><p>The criteria <tt>class</tt>, <tt>instance</tt>, <tt>role</tt>, <tt>title</tt> and <tt>mark</tt> are actually
\r
1616 regular expressions (PCRE). See <tt>pcresyntax(3)</tt> or <tt>perldoc perlre</tt> for
\r
1617 information on how to use them.</p></div>
\r
1618 <div class="sect2">
\r
1619 <h3 id="exec">6.1. Executing applications (exec)</h3>
\r
1620 <div class="paragraph"><p>What good is a window manager if you can’t actually start any applications?
\r
1621 The exec command starts an application by passing the command you specify to a
\r
1622 shell. This implies that you can use globbing (wildcards) and programs will be
\r
1623 searched in your $PATH.</p></div>
\r
1624 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1625 <div class="listingblock">
\r
1626 <div class="content">
\r
1627 <pre><tt>exec [--no-startup-id] command</tt></pre>
\r
1629 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1630 <div class="listingblock">
\r
1631 <div class="content">
\r
1632 <pre><tt># Start the GIMP
\r
1633 bindsym $mod+g exec gimp
\r
1635 # Start the terminal emulator urxvt which is not yet startup-notification-aware
\r
1636 bindsym $mod+Return exec --no-startup-id urxvt</tt></pre>
\r
1638 <div class="paragraph"><p>The <tt>--no-startup-id</tt> parameter disables startup-notification support for this
\r
1639 particular exec command. With startup-notification, i3 can make sure that a
\r
1640 window appears on the workspace on which you used the exec command. Also, it
\r
1641 will change the X11 cursor to <tt>watch</tt> (a clock) while the application is
\r
1642 launching. So, if an application is not startup-notification aware (most GTK
\r
1643 and Qt using applications seem to be, though), you will end up with a watch
\r
1644 cursor for 60 seconds.</p></div>
\r
1646 <div class="sect2">
\r
1647 <h3 id="_splitting_containers">6.2. Splitting containers</h3>
\r
1648 <div class="paragraph"><p>The split command makes the current window a split container. Split containers
\r
1649 can contain multiple windows. Depending on the layout of the split container,
\r
1650 new windows get placed to the right of the current one (splith) or new windows
\r
1651 get placed below the current one (splitv).</p></div>
\r
1652 <div class="paragraph"><p>If you apply this command to a split container with the same orientation,
\r
1653 nothing will happen. If you use a different orientation, the split container’s
\r
1654 orientation will be changed (if it does not have more than one window). Use
\r
1655 <tt>layout toggle split</tt> to change the layout of any split container from splitv
\r
1656 to splith or vice-versa.</p></div>
\r
1657 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1658 <div class="listingblock">
\r
1659 <div class="content">
\r
1660 <pre><tt>split <vertical|horizontal></tt></pre>
\r
1662 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1663 <div class="listingblock">
\r
1664 <div class="content">
\r
1665 <pre><tt>bindsym $mod+v split vertical
\r
1666 bindsym $mod+h split horizontal</tt></pre>
\r
1669 <div class="sect2">
\r
1670 <h3 id="_manipulating_layout">6.3. Manipulating layout</h3>
\r
1671 <div class="paragraph"><p>Use <tt>layout toggle split</tt>, <tt>layout stacking</tt>, <tt>layout tabbed</tt>, <tt>layout splitv</tt>
\r
1672 or <tt>layout splith</tt> to change the current container layout to splith/splitv,
\r
1673 stacking, tabbed layout, splitv or splith, respectively.</p></div>
\r
1674 <div class="paragraph"><p>To make the current window (!) fullscreen, use <tt>fullscreen enable</tt> (or
\r
1675 <tt>fullscreen enable global</tt> for the global mode), to leave either fullscreen
\r
1676 mode use <tt>fullscreen disable</tt>, and to toggle between these two states use
\r
1677 <tt>fullscreen toggle</tt> (or <tt>fullscreen toggle global</tt>).</p></div>
\r
1678 <div class="paragraph"><p>Likewise, to make the current window floating (or tiling again) use <tt>floating
\r
1679 enable</tt> respectively <tt>floating disable</tt> (or <tt>floating toggle</tt>):</p></div>
\r
1680 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1681 <div class="listingblock">
\r
1682 <div class="content">
\r
1683 <pre><tt>layout <default|tabbed|stacking|splitv|splith>
\r
1684 layout toggle [split|all]</tt></pre>
\r
1686 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
1687 <div class="listingblock">
\r
1688 <div class="content">
\r
1689 <pre><tt>bindsym $mod+s layout stacking
\r
1690 bindsym $mod+l layout toggle split
\r
1691 bindsym $mod+w layout tabbed
\r
1693 # Toggle between stacking/tabbed/split:
\r
1694 bindsym $mod+x layout toggle
\r
1696 # Toggle between stacking/tabbed/splith/splitv:
\r
1697 bindsym $mod+x layout toggle all
\r
1699 # Toggle fullscreen
\r
1700 bindsym $mod+f fullscreen toggle
\r
1702 # Toggle floating/tiling
\r
1703 bindsym $mod+t floating toggle</tt></pre>
\r
1706 <div class="sect2">
\r
1707 <h3 id="_focusing_moving_containers">6.4. Focusing/Moving containers</h3>
\r
1708 <div class="paragraph"><p>To change the focus, use the focus command: <tt>focus left</tt>, <tt>focus right</tt>, <tt>focus
\r
1709 down</tt> and <tt>focus up</tt>.</p></div>
\r
1710 <div class="paragraph"><p>There are a few special parameters you can use for the focus command:</p></div>
\r
1711 <div class="dlist"><dl>
\r
1712 <dt class="hdlist1">
\r
1717 Sets focus to the <tt>Parent Container</tt> of the current <tt>Container</tt>.
\r
1720 <dt class="hdlist1">
\r
1725 The opposite of <tt>focus parent</tt>, sets the focus to the last focused
\r
1729 <dt class="hdlist1">
\r
1734 Sets focus to the last focused floating container.
\r
1737 <dt class="hdlist1">
\r
1742 Sets focus to the last focused tiling container.
\r
1745 <dt class="hdlist1">
\r
1750 Toggles between floating/tiling containers.
\r
1753 <dt class="hdlist1">
\r
1758 Followed by a direction or an output name, this will focus the
\r
1759 corresponding output.
\r
1763 <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
1764 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1765 <div class="listingblock">
\r
1766 <div class="content">
\r
1767 <pre><tt>focus <left|right|down|up>
\r
1768 focus <parent|child|floating|tiling|mode_toggle>
\r
1769 focus output <<left|right|down|up>|output>
\r
1770 move <left|right|down|up> [<px> px]
\r
1771 move [absolute] position [[<px> px] [<px> px]|center]</tt></pre>
\r
1773 <div class="paragraph"><p>Note that the amount of pixels you can specify for the <tt>move</tt> command is only
\r
1774 relevant for floating containers. The default amount is 10 pixels.</p></div>
\r
1775 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
1776 <div class="listingblock">
\r
1777 <div class="content">
\r
1778 <pre><tt># Focus container on the left, bottom, top, right:
\r
1779 bindsym $mod+j focus left
\r
1780 bindsym $mod+k focus down
\r
1781 bindsym $mod+l focus up
\r
1782 bindsym $mod+semicolon focus right
\r
1784 # Focus parent container
\r
1785 bindsym $mod+u focus parent
\r
1787 # Focus last floating/tiling container
\r
1788 bindsym $mod+g focus mode_toggle
\r
1790 # Focus the output right to the current one
\r
1791 bindsym $mod+x focus output right
\r
1793 # Focus the big output
\r
1794 bindsym $mod+x focus output HDMI-2
\r
1796 # Move container to the left, bottom, top, right:
\r
1797 bindsym $mod+j move left
\r
1798 bindsym $mod+k move down
\r
1799 bindsym $mod+l move up
\r
1800 bindsym $mod+semicolon move right
\r
1802 # Move container, but make floating containers
\r
1803 # move more than the default
\r
1804 bindsym $mod+j move left 20 px
\r
1806 # Move floating container to the center
\r
1808 bindsym $mod+c move absolute position center</tt></pre>
\r
1811 <div class="sect2">
\r
1812 <h3 id="_changing_named_workspaces_moving_to_workspaces">6.5. Changing (named) workspaces/moving to workspaces</h3>
\r
1813 <div class="paragraph"><p>To change to a specific workspace, use the <tt>workspace</tt> command, followed by the
\r
1814 number or name of the workspace. To move containers to specific workspaces, use
\r
1815 <tt>move container to workspace</tt>.</p></div>
\r
1816 <div class="paragraph"><p>You can also switch to the next and previous workspace with the commands
\r
1817 <tt>workspace next</tt> and <tt>workspace prev</tt>, which is handy, for example, if you have
\r
1818 workspace 1, 3, 4 and 9 and you want to cycle through them with a single key
\r
1819 combination. To restrict those to the current output, use <tt>workspace
\r
1820 next_on_output</tt> and <tt>workspace prev_on_output</tt>. Similarly, you can use <tt>move
\r
1821 container to workspace next</tt>, <tt>move container to workspace prev</tt> to move a
\r
1822 container to the next/previous workspace and <tt>move container to workspace current</tt>
\r
1823 (the last one makes sense only when used with criteria).</p></div>
\r
1824 <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
1825 RandR output.</p></div>
\r
1826 <div class="paragraph"><p>Workspace names are parsed as
\r
1827 <a href="https://developer.gnome.org/pango/stable/PangoMarkupFormat.html">Pango markup</a>
\r
1828 by i3bar.</p></div>
\r
1829 <div class="paragraph" id="back_and_forth"><p>To switch back to the previously focused workspace, use <tt>workspace
\r
1830 back_and_forth</tt>; likewise, you can move containers to the previously focused
\r
1831 workspace using <tt>move container to workspace back_and_forth</tt>.</p></div>
\r
1832 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1833 <div class="listingblock">
\r
1834 <div class="content">
\r
1835 <pre><tt>workspace <next|prev|next_on_output|prev_on_output>
\r
1836 workspace back_and_forth
\r
1837 workspace <name>
\r
1838 workspace number <name>
\r
1840 move [window|container] [to] workspace <name>
\r
1841 move [window|container] [to] workspace number <name>
\r
1842 move [window|container] [to] workspace <prev|next|current></tt></pre>
\r
1844 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
1845 <div class="listingblock">
\r
1846 <div class="content">
\r
1847 <pre><tt>bindsym $mod+1 workspace 1
\r
1848 bindsym $mod+2 workspace 2
\r
1849 bindsym $mod+3 workspace 3:<span foreground="red">vim</span>
\r
1852 bindsym $mod+Shift+1 move container to workspace 1
\r
1853 bindsym $mod+Shift+2 move container to workspace 2
\r
1856 # switch between the current and the previously focused one
\r
1857 bindsym $mod+b workspace back_and_forth
\r
1858 bindsym $mod+Shift+b move container to workspace back_and_forth
\r
1860 # move the whole workspace to the next output
\r
1861 bindsym $mod+x move workspace to output right
\r
1863 # move firefox to current workspace
\r
1864 bindsym $mod+F1 [class="Firefox"] move workspace current</tt></pre>
\r
1866 <div class="sect3">
\r
1867 <h4 id="_named_workspaces">6.5.1. Named workspaces</h4>
\r
1868 <div class="paragraph"><p>Workspaces are identified by their name. So, instead of using numbers in the
\r
1869 workspace command, you can use an arbitrary name:</p></div>
\r
1870 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1871 <div class="listingblock">
\r
1872 <div class="content">
\r
1873 <pre><tt>bindsym $mod+1 workspace mail
\r
1876 <div class="paragraph"><p>If you want the workspace to have a number <strong>and</strong> a name, just prefix the
\r
1877 number, like this:</p></div>
\r
1878 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
1879 <div class="listingblock">
\r
1880 <div class="content">
\r
1881 <pre><tt>bindsym $mod+1 workspace 1: mail
\r
1882 bindsym $mod+2 workspace 2: www
\r
1885 <div class="paragraph"><p>Note that the workspace will really be named "1: mail". i3 treats workspace
\r
1886 names beginning with a number in a slightly special way. Normally, named
\r
1887 workspaces are ordered the way they appeared. When they start with a number, i3
\r
1888 will order them numerically. Also, you will be able to use <tt>workspace number 1</tt>
\r
1889 to switch to the workspace which begins with number 1, regardless of which name
\r
1890 it has. This is useful in case you are changing the workspace’s name
\r
1891 dynamically. To combine both commands you can use <tt>workspace number 1: mail</tt> to
\r
1892 specify a default name if there’s currently no workspace starting with a "1".</p></div>
\r
1894 <div class="sect3">
\r
1895 <h4 id="_renaming_workspaces">6.5.2. Renaming workspaces</h4>
\r
1896 <div class="paragraph"><p>You can rename workspaces. This might be useful to start with the default
\r
1897 numbered workspaces, do your work, and rename the workspaces afterwards to
\r
1898 reflect what’s actually on them. You can also omit the old name to rename
\r
1899 the currently focused workspace. This is handy if you want to use the
\r
1900 rename command with <tt>i3-input</tt>.</p></div>
\r
1901 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1902 <div class="listingblock">
\r
1903 <div class="content">
\r
1904 <pre><tt>rename workspace <old_name> to <new_name>
\r
1905 rename workspace to <new_name></tt></pre>
\r
1907 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
1908 <div class="listingblock">
\r
1909 <div class="content">
\r
1910 <pre><tt>i3-msg 'rename workspace 5 to 6'
\r
1911 i3-msg 'rename workspace 1 to "1: www"'
\r
1912 i3-msg 'rename workspace "1: www" to "10: www"'
\r
1913 i3-msg 'rename workspace to "2: mail"
\r
1914 bindsym $mod+r exec i3-input -F 'rename workspace to "%s"' -P 'New name: '</tt></pre>
\r
1918 <div class="sect2">
\r
1919 <h3 id="_moving_workspaces_to_a_different_screen">6.6. Moving workspaces to a different screen</h3>
\r
1920 <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
1921 RandR output.</p></div>
\r
1923 <div class="sect2">
\r
1924 <h3 id="_moving_containers_workspaces_to_randr_outputs">6.7. Moving containers/workspaces to RandR outputs</h3>
\r
1925 <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
1926 <tt>VGA1</tt>) or to a RandR output identified by a specific direction (like <tt>left</tt>,
\r
1927 <tt>right</tt>, <tt>up</tt> or <tt>down</tt>), there are two commands:</p></div>
\r
1928 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1929 <div class="listingblock">
\r
1930 <div class="content">
\r
1931 <pre><tt>move container to output <<left|right|down|up>|<output>>
\r
1932 move workspace to output <<left|right|down|up>|<output>></tt></pre>
\r
1934 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
1935 <div class="listingblock">
\r
1936 <div class="content">
\r
1937 <pre><tt># Move the current workspace to the next output
\r
1938 # (effectively toggles when you only have two outputs)
\r
1939 bindsym $mod+x move workspace to output right
\r
1941 # Put this window on the presentation output.
\r
1942 bindsym $mod+x move container to output VGA1</tt></pre>
\r
1945 <div class="sect2">
\r
1946 <h3 id="resizingconfig">6.8. Resizing containers/windows</h3>
\r
1947 <div class="paragraph"><p>If you want to resize containers/windows using your keyboard, you can use the
\r
1948 <tt>resize</tt> command:</p></div>
\r
1949 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
1950 <div class="listingblock">
\r
1951 <div class="content">
\r
1952 <pre><tt>resize <grow|shrink> <direction> [<px> px [or <ppt> ppt]]</tt></pre>
\r
1954 <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
1955 less specific and use <tt>width</tt> or <tt>height</tt>, in which case i3 will take/give
\r
1956 space from all the other containers. The optional pixel argument specifies by
\r
1957 how many pixels a <strong>floating container</strong> should be grown or shrunk (the default
\r
1958 is 10 pixels). The ppt argument means percentage points and specifies by how
\r
1959 many percentage points a <strong>tiling container</strong> should be grown or shrunk (the
\r
1960 default is 10 percentage points).</p></div>
\r
1961 <div class="paragraph"><p>I recommend using the resize command inside a so called <tt>mode</tt>:</p></div>
\r
1962 <div class="listingblock">
\r
1963 <div class="title">Example: Configuration file, defining a mode for resizing</div>
\r
1964 <div class="content">
\r
1965 <pre><tt>mode "resize" {
\r
1966 # These bindings trigger as soon as you enter the resize mode
\r
1968 # Pressing left will shrink the window’s width.
\r
1969 # Pressing right will grow the window’s width.
\r
1970 # Pressing up will shrink the window’s height.
\r
1971 # Pressing down will grow the window’s height.
\r
1972 bindsym j resize shrink width 10 px or 10 ppt
\r
1973 bindsym k resize grow height 10 px or 10 ppt
\r
1974 bindsym l resize shrink height 10 px or 10 ppt
\r
1975 bindsym semicolon resize grow width 10 px or 10 ppt
\r
1977 # same bindings, but for the arrow keys
\r
1978 bindsym Left resize shrink width 10 px or 10 ppt
\r
1979 bindsym Down resize grow height 10 px or 10 ppt
\r
1980 bindsym Up resize shrink height 10 px or 10 ppt
\r
1981 bindsym Right resize grow width 10 px or 10 ppt
\r
1983 # back to normal: Enter or Escape
\r
1984 bindsym Return mode "default"
\r
1985 bindsym Escape mode "default"
\r
1988 # Enter resize mode
\r
1989 bindsym $mod+r mode "resize"</tt></pre>
\r
1992 <div class="sect2">
\r
1993 <h3 id="_jumping_to_specific_windows">6.9. Jumping to specific windows</h3>
\r
1994 <div class="paragraph"><p>Often when in a multi-monitor environment, you want to quickly jump to a
\r
1995 specific window. For example, while working on workspace 3 you may want to
\r
1996 jump to your mail client to email your boss that you’ve achieved some
\r
1997 important goal. Instead of figuring out how to navigate to your mail client,
\r
1998 it would be more convenient to have a shortcut. You can use the <tt>focus</tt> command
\r
1999 with criteria for that.</p></div>
\r
2000 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2001 <div class="listingblock">
\r
2002 <div class="content">
\r
2003 <pre><tt>[class="class"] focus
\r
2004 [title="title"] focus</tt></pre>
\r
2006 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2007 <div class="listingblock">
\r
2008 <div class="content">
\r
2009 <pre><tt># Get me to the next open VIM instance
\r
2010 bindsym $mod+a [class="urxvt" title="VIM"] focus</tt></pre>
\r
2013 <div class="sect2">
\r
2014 <h3 id="_vim_like_marks_mark_goto">6.10. VIM-like marks (mark/goto)</h3>
\r
2015 <div class="paragraph" id="vim_like_marks"><p>This feature is like the jump feature: It allows you to directly jump to a
\r
2016 specific window (this means switching to the appropriate workspace and setting
\r
2017 focus to the windows). However, you can directly mark a specific window with
\r
2018 an arbitrary label and use it afterwards. You can unmark the label in the same
\r
2019 way, using the unmark command. If you don’t specify a label, unmark removes all
\r
2020 marks. You do not need to ensure that your windows have unique classes or
\r
2021 titles, and you do not need to change your configuration file.</p></div>
\r
2022 <div class="paragraph"><p>As the command needs to include the label with which you want to mark the
\r
2023 window, you cannot simply bind it to a key. <tt>i3-input</tt> is a tool created
\r
2024 for this purpose: It lets you input a command and sends the command to i3. It
\r
2025 can also prefix this command and display a custom prompt for the input dialog.</p></div>
\r
2026 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2027 <div class="listingblock">
\r
2028 <div class="content">
\r
2029 <pre><tt>mark identifier
\r
2030 [con_mark="identifier"] focus
\r
2031 unmark identifier</tt></pre>
\r
2033 <div class="paragraph"><p><strong>Example (in a terminal)</strong>:</p></div>
\r
2034 <div class="listingblock">
\r
2035 <div class="content">
\r
2036 <pre><tt>$ i3-msg mark irssi
\r
2037 $ i3-msg '[con_mark="irssi"] focus'
\r
2038 $ i3-msg unmark irssi</tt></pre>
\r
2041 <div class="sect2">
\r
2042 <h3 id="_changing_border_style">6.11. Changing border style</h3>
\r
2043 <div class="paragraph"><p>To change the border of the current client, you can use <tt>border normal</tt> to use the normal
\r
2044 border (including window title), <tt>border 1pixel</tt> to use a 1-pixel border (no window title)
\r
2045 and <tt>border none</tt> to make the client borderless.</p></div>
\r
2046 <div class="paragraph"><p>There is also <tt>border toggle</tt> which will toggle the different border styles.</p></div>
\r
2047 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2048 <div class="listingblock">
\r
2049 <div class="content">
\r
2050 <pre><tt>bindsym $mod+t border normal
\r
2051 bindsym $mod+y border 1pixel
\r
2052 bindsym $mod+u border none</tt></pre>
\r
2055 <div class="sect2">
\r
2056 <h3 id="shmlog">6.12. Enabling shared memory logging</h3>
\r
2057 <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
2058 memory buffer, which you can dump using <tt>i3-dump-log</tt>. The <tt>shmlog</tt> command
\r
2059 allows you to enable or disable the shared memory logging at runtime.</p></div>
\r
2060 <div class="paragraph"><p>Note that when using <tt>shmlog <size_in_bytes></tt>, the current log will be
\r
2061 discarded and a new one will be started.</p></div>
\r
2062 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2063 <div class="listingblock">
\r
2064 <div class="content">
\r
2065 <pre><tt>shmlog <size_in_bytes>
\r
2066 shmlog <on|off|toggle></tt></pre>
\r
2068 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2069 <div class="listingblock">
\r
2070 <div class="content">
\r
2071 <pre><tt># Enable/disable logging
\r
2072 bindsym $mod+x shmlog toggle
\r
2074 # or, from a terminal:
\r
2075 # increase the shared memory log buffer to 50 MiB
\r
2076 i3-msg shmlog $((50*1024*1024))</tt></pre>
\r
2079 <div class="sect2">
\r
2080 <h3 id="_enabling_debug_logging">6.13. Enabling debug logging</h3>
\r
2081 <div class="paragraph"><p>The <tt>debuglog</tt> command allows you to enable or disable debug logging at
\r
2082 runtime. Debug logging is much more verbose than non-debug logging. This
\r
2083 command does not activate shared memory logging (shmlog), and as such is most
\r
2084 likely useful in combination with the above-described <a href="#shmlog">[shmlog]</a> command.</p></div>
\r
2085 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2086 <div class="listingblock">
\r
2087 <div class="content">
\r
2088 <pre><tt>debuglog <on|off|toggle></tt></pre>
\r
2090 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2091 <div class="listingblock">
\r
2092 <div class="content">
\r
2093 <pre><tt># Enable/disable logging
\r
2094 bindsym $mod+x debuglog toggle</tt></pre>
\r
2097 <div class="sect2">
\r
2098 <h3 id="_reloading_restarting_exiting">6.14. Reloading/Restarting/Exiting</h3>
\r
2099 <div class="paragraph"><p>You can make i3 reload its configuration file with <tt>reload</tt>. You can also
\r
2100 restart i3 inplace with the <tt>restart</tt> command to get it out of some weird state
\r
2101 (if that should ever happen) or to perform an upgrade without having to restart
\r
2102 your X session. To exit i3 properly, you can use the <tt>exit</tt> command,
\r
2103 however you don’t need to (simply killing your X session is fine as well).</p></div>
\r
2104 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2105 <div class="listingblock">
\r
2106 <div class="content">
\r
2107 <pre><tt>bindsym $mod+Shift+r restart
\r
2108 bindsym $mod+Shift+w reload
\r
2109 bindsym $mod+Shift+e exit</tt></pre>
\r
2112 <div class="sect2">
\r
2113 <h3 id="_scratchpad">6.15. Scratchpad</h3>
\r
2114 <div class="paragraph"><p>There are two commands to use any existing window as scratchpad window. <tt>move
\r
2115 scratchpad</tt> will move a window to the scratchpad workspace. This will make it
\r
2116 invisible until you show it again. There is no way to open that workspace.
\r
2117 Instead, when using <tt>scratchpad show</tt>, the window will be shown again, as a
\r
2118 floating window, centered on your current workspace (using <tt>scratchpad show</tt> on
\r
2119 a visible scratchpad window will make it hidden again, so you can have a
\r
2120 keybinding to toggle). Note that this is just a normal floating window, so if
\r
2121 you want to "remove it from scratchpad", you can simple make it tiling again
\r
2122 (<tt>floating toggle</tt>).</p></div>
\r
2123 <div class="paragraph"><p>As the name indicates, this is useful for having a window with your favorite
\r
2124 editor always at hand. However, you can also use this for other permanently
\r
2125 running applications which you don’t want to see all the time: Your music
\r
2126 player, alsamixer, maybe even your mail client…?</p></div>
\r
2127 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2128 <div class="listingblock">
\r
2129 <div class="content">
\r
2130 <pre><tt>move scratchpad
\r
2132 scratchpad show</tt></pre>
\r
2134 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2135 <div class="listingblock">
\r
2136 <div class="content">
\r
2137 <pre><tt># Make the currently focused window a scratchpad
\r
2138 bindsym $mod+Shift+minus move scratchpad
\r
2140 # Show the first scratchpad window
\r
2141 bindsym $mod+minus scratchpad show
\r
2143 # Show the sup-mail scratchpad window, if any.
\r
2144 bindsym mod4+s [title="^Sup ::"] scratchpad show</tt></pre>
\r
2147 <div class="sect2">
\r
2148 <h3 id="_nop">6.16. Nop</h3>
\r
2149 <div class="paragraph"><p>There is a no operation command <tt>nop</tt> which allows you to override default
\r
2150 behavior. This can be useful for, e.g., disabling a focus change on clicks with
\r
2151 the middle mouse button.</p></div>
\r
2152 <div class="paragraph"><p>The optional <tt>comment</tt> argument is ignored, but will be printed to the log file
\r
2153 for debugging purposes.</p></div>
\r
2154 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2155 <div class="listingblock">
\r
2156 <div class="content">
\r
2157 <pre><tt>nop [<comment>]</tt></pre>
\r
2159 <div class="paragraph"><p><strong>Example</strong>:</p></div>
\r
2160 <div class="listingblock">
\r
2161 <div class="content">
\r
2162 <pre><tt># Disable focus change for clicks on titlebars
\r
2163 # with the middle mouse button
\r
2164 bindsym button2 nop</tt></pre>
\r
2167 <div class="sect2">
\r
2168 <h3 id="_i3bar_control">6.17. i3bar control</h3>
\r
2169 <div class="paragraph"><p>There are two options in the configuration of each i3bar instance that can be
\r
2170 changed during runtime by invoking a command through i3. The commands <tt>bar
\r
2171 hidden_state</tt> and <tt>bar mode</tt> allow setting the current hidden_state
\r
2172 respectively mode option of each bar. It is also possible to toggle between
\r
2173 hide state and show state as well as between dock mode and hide mode. Each
\r
2174 i3bar instance can be controlled individually by specifying a bar_id, if none
\r
2175 is given, the command is executed for all bar instances.</p></div>
\r
2176 <div class="paragraph"><p><strong>Syntax</strong>:</p></div>
\r
2177 <div class="listingblock">
\r
2178 <div class="content">
\r
2179 <pre><tt>bar hidden_state hide|show|toggle [<bar_id>]
\r
2181 bar mode dock|hide|invisible|toggle [<bar_id>]</tt></pre>
\r
2183 <div class="paragraph"><p><strong>Examples</strong>:</p></div>
\r
2184 <div class="listingblock">
\r
2185 <div class="content">
\r
2186 <pre><tt># Toggle between hide state and show state
\r
2187 bindsym $mod+m bar hidden_state toggle
\r
2189 # Toggle between dock mode and hide mode
\r
2190 bindsym $mod+n bar mode toggle
\r
2192 # Set the bar instance with id 'bar-1' to switch to hide mode
\r
2193 bindsym $mod+b bar mode hide bar-1
\r
2195 # Set the bar instance with id 'bar-1' to always stay hidden
\r
2196 bindsym $mod+Shift+b bar mode invisible bar-1</tt></pre>
\r
2201 <div class="sect1">
\r
2202 <h2 id="multi_monitor">7. Multiple monitors</h2>
\r
2203 <div class="sectionbody">
\r
2204 <div class="paragraph"><p>As you can see in the goal list on the website, i3 was specifically developed
\r
2205 with support for multiple monitors in mind. This section will explain how to
\r
2206 handle multiple monitors.</p></div>
\r
2207 <div class="paragraph"><p>When you have only one monitor, things are simple. You usually start with
\r
2208 workspace 1 on your monitor and open new ones as you need them.</p></div>
\r
2209 <div class="paragraph"><p>When you have more than one monitor, each monitor will get an initial
\r
2210 workspace. The first monitor gets 1, the second gets 2 and a possible third
\r
2211 would get 3. When you switch to a workspace on a different monitor, i3 will
\r
2212 switch to that monitor and then switch to the workspace. This way, you don’t
\r
2213 need shortcuts to switch to a specific monitor, and you don’t need to remember
\r
2214 where you put which workspace. New workspaces will be opened on the currently
\r
2215 active monitor. It is not possible to have a monitor without a workspace.</p></div>
\r
2216 <div class="paragraph"><p>The idea of making workspaces global is based on the observation that most
\r
2217 users have a very limited set of workspaces on their additional monitors.
\r
2218 They are often used for a specific task (browser, shell) or for monitoring
\r
2219 several things (mail, IRC, syslog, …). Thus, using one workspace on one monitor
\r
2220 and "the rest" on the other monitors often makes sense. However, as you can
\r
2221 create an unlimited number of workspaces in i3 and tie them to specific
\r
2222 screens, you can have the "traditional" approach of having X workspaces per
\r
2223 screen by changing your configuration (using modes, for example).</p></div>
\r
2224 <div class="sect2">
\r
2225 <h3 id="_configuring_your_monitors">7.1. Configuring your monitors</h3>
\r
2226 <div class="paragraph"><p>To help you get going if you have never used multiple monitors before, here is
\r
2227 a short overview of the xrandr options which will probably be of interest to
\r
2228 you. It is always useful to get an overview of the current screen configuration.
\r
2229 Just run "xrandr" and you will get an output like the following:</p></div>
\r
2230 <div class="listingblock">
\r
2231 <div class="content">
\r
2233 Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
\r
2234 VGA1 disconnected (normal left inverted right x axis y axis)
\r
2235 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
\r
2236 1280x800 60.0*+ 50.0
\r
2237 1024x768 85.0 75.0 70.1 60.0
\r
2239 800x600 85.1 72.2 75.0 60.3 56.2
\r
2240 640x480 85.0 72.8 75.0 59.9
\r
2243 640x350 85.1</tt></pre>
\r
2245 <div class="paragraph"><p>Several things are important here: You can see that <tt>LVDS1</tt> is connected (of
\r
2246 course, it is the internal flat panel) but <tt>VGA1</tt> is not. If you have a monitor
\r
2247 connected to one of the ports but xrandr still says "disconnected", you should
\r
2248 check your cable, monitor or graphics driver.</p></div>
\r
2249 <div class="paragraph"><p>The maximum resolution you can see at the end of the first line is the maximum
\r
2250 combined resolution of your monitors. By default, it is usually too low and has
\r
2251 to be increased by editing <tt>/etc/X11/xorg.conf</tt>.</p></div>
\r
2252 <div class="paragraph"><p>So, say you connected VGA1 and want to use it as an additional screen:</p></div>
\r
2253 <div class="listingblock">
\r
2254 <div class="content">
\r
2255 <pre><tt>xrandr --output VGA1 --auto --left-of LVDS1</tt></pre>
\r
2257 <div class="paragraph"><p>This command makes xrandr try to find the native resolution of the device
\r
2258 connected to <tt>VGA1</tt> and configures it to the left of your internal flat panel.
\r
2259 When running "xrandr" again, the output looks like this:</p></div>
\r
2260 <div class="listingblock">
\r
2261 <div class="content">
\r
2263 Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 8192 x 8192
\r
2264 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
\r
2265 1280x1024 60.0*+ 75.0
\r
2268 1024x768 75.1 70.1 60.0
\r
2270 800x600 72.2 75.0 60.3 56.2
\r
2271 640x480 72.8 75.0 66.7 60.0
\r
2273 LVDS1 connected 1280x800+1280+0 (normal left inverted right x axis y axis) 261mm x 163mm
\r
2274 1280x800 60.0*+ 50.0
\r
2275 1024x768 85.0 75.0 70.1 60.0
\r
2277 800x600 85.1 72.2 75.0 60.3 56.2
\r
2278 640x480 85.0 72.8 75.0 59.9
\r
2281 640x350 85.1</tt></pre>
\r
2283 <div class="paragraph"><p>Please note that i3 uses exactly the same API as xrandr does, so it will see
\r
2284 only what you can see in xrandr.</p></div>
\r
2285 <div class="paragraph"><p>See also <a href="#presentations">[presentations]</a> for more examples of multi-monitor setups.</p></div>
\r
2287 <div class="sect2">
\r
2288 <h3 id="_interesting_configuration_for_multi_monitor_environments">7.2. Interesting configuration for multi-monitor environments</h3>
\r
2289 <div class="paragraph"><p>There are several things to configure in i3 which may be interesting if you
\r
2290 have more than one monitor:</p></div>
\r
2291 <div class="olist arabic"><ol class="arabic">
\r
2294 You can specify which workspace should be put on which screen. This
\r
2295 allows you to have a different set of workspaces when starting than just
\r
2296 1 for the first monitor, 2 for the second and so on. See
\r
2297 <a href="#workspace_screen">[workspace_screen]</a>.
\r
2302 If you want some applications to generally open on the bigger screen
\r
2303 (MPlayer, Firefox, …), you can assign them to a specific workspace, see
\r
2304 <a href="#assign_workspace">[assign_workspace]</a>.
\r
2309 If you have many workspaces on many monitors, it might get hard to keep
\r
2310 track of which window you put where. Thus, you can use vim-like marks to
\r
2311 quickly switch between windows. See <a href="#vim_like_marks">[vim_like_marks]</a>.
\r
2316 For information on how to move existing workspaces between monitors,
\r
2317 see <a href="#_moving_containers_workspaces_to_randr_outputs">[_moving_containers_workspaces_to_randr_outputs]</a>.
\r
2324 <div class="sect1">
\r
2325 <h2 id="_i3_and_the_rest_of_your_software_world">8. i3 and the rest of your software world</h2>
\r
2326 <div class="sectionbody">
\r
2327 <div class="sect2">
\r
2328 <h3 id="_displaying_a_status_line">8.1. Displaying a status line</h3>
\r
2329 <div class="paragraph"><p>A very common thing amongst users of exotic window managers is a status line at
\r
2330 some corner of the screen. It is an often superior replacement to the widget
\r
2331 approach you have in the task bar of a traditional desktop environment.</p></div>
\r
2332 <div class="paragraph"><p>If you don’t already have your favorite way of generating such a status line
\r
2333 (self-written scripts, conky, …), then i3status is the recommended tool for
\r
2334 this task. It was written in C with the goal of using as few syscalls as
\r
2335 possible to reduce the time your CPU is woken up from sleep states. Because
\r
2336 i3status only spits out text, you need to combine it with some other tool, like
\r
2337 i3bar. See <a href="#status_command">[status_command]</a> for how to display i3status in i3bar.</p></div>
\r
2338 <div class="paragraph"><p>Regardless of which application you use to display the status line, you
\r
2339 want to make sure that it registers as a dock window using EWMH hints. i3 will
\r
2340 position the window either at the top or at the bottom of the screen, depending
\r
2341 on which hint the application sets. With i3bar, you can configure its position,
\r
2342 see <a href="#i3bar_position">[i3bar_position]</a>.</p></div>
\r
2344 <div class="sect2">
\r
2345 <h3 id="_giving_presentations_multi_monitor">8.2. Giving presentations (multi-monitor)</h3>
\r
2346 <div class="paragraph"><p>When giving a presentation, you typically want the audience to see what you see
\r
2347 on your screen and then go through a series of slides (if the presentation is
\r
2348 simple). For more complex presentations, you might want to have some notes
\r
2349 which only you can see on your screen, while the audience can only see the
\r
2351 <div class="sect3">
\r
2352 <h4 id="presentations">8.2.1. Case 1: everybody gets the same output</h4>
\r
2353 <div class="paragraph"><p>This is the simple case. You connect your computer to the video projector,
\r
2354 turn on both (computer and video projector) and configure your X server to
\r
2355 clone the internal flat panel of your computer to the video output:</p></div>
\r
2356 <div class="listingblock">
\r
2357 <div class="content">
\r
2358 <pre><tt>xrandr --output VGA1 --mode 1024x768 --same-as LVDS1</tt></pre>
\r
2360 <div class="paragraph"><p>i3 will then use the lowest common subset of screen resolutions, the rest of
\r
2361 your screen will be left untouched (it will show the X background). So, in
\r
2362 our example, this would be 1024x768 (my notebook has 1280x800).</p></div>
\r
2364 <div class="sect3">
\r
2365 <h4 id="_case_2_you_can_see_more_than_your_audience">8.2.2. Case 2: you can see more than your audience</h4>
\r
2366 <div class="paragraph"><p>This case is a bit harder. First of all, you should configure the VGA output
\r
2367 somewhere near your internal flat panel, say right of it:</p></div>
\r
2368 <div class="listingblock">
\r
2369 <div class="content">
\r
2370 <pre><tt>xrandr --output VGA1 --mode 1024x768 --right-of LVDS1</tt></pre>
\r
2372 <div class="paragraph"><p>Now, i3 will put a new workspace (depending on your settings) on the new screen
\r
2373 and you are in multi-monitor mode (see <a href="#multi_monitor">[multi_monitor]</a>).</p></div>
\r
2374 <div class="paragraph"><p>Because i3 is not a compositing window manager, there is no ability to
\r
2375 display a window on two screens at the same time. Instead, your presentation
\r
2376 software needs to do this job (that is, open a window on each screen).</p></div>
\r
2382 <div id="footnotes"><hr /></div>
\r
2383 <div id="footer" lang="de">
\r
2384 © 2009-2011 Michael Stapelberg, <a href="/impress.html">Impressum</a>
\r
projects / i3 / i3.github.io / blob