3 Michael Stapelberg <michael@i3wm.org>
6 This document contains all the information you need to configure and use the i3
7 window manager. If it does not, please check http://faq.i3wm.org/ first, then
8 contact us on IRC (preferred) or post your question(s) on the mailing list.
10 == Default keybindings
12 For the "too long; didn’t read" people, here is an overview of the default
13 keybindings (click to see the full size image):
15 *Keys to use with $mod (Alt):*
17 image:keyboard-layer1.png["Keys to use with $mod (Alt)",width=600,link="keyboard-layer1.png"]
19 *Keys to use with Shift+$mod:*
21 image:keyboard-layer2.png["Keys to use with Shift+$mod",width=600,link="keyboard-layer2.png"]
23 The red keys are the modifiers you need to press (by default), the blue keys
28 Throughout this guide, the keyword +$mod+ will be used to refer to the
29 configured modifier. This is the Alt key (Mod1) by default, with the Windows
30 key (Mod4) being a popular alternative.
32 === Opening terminals and moving around
34 One very basic operation is opening a new terminal. By default, the keybinding
35 for this is $mod+Enter, that is Alt+Enter in the default configuration. By
36 pressing $mod+Enter, a new terminal will be opened. It will fill the whole
37 space available on your screen.
39 image:single_terminal.png[Single terminal]
41 If you now open another terminal, i3 will place it next to the current one,
42 splitting the screen size in half. Depending on your monitor, i3 will put the
43 created window beside the existing window (on wide displays) or below the
44 existing window (rotated displays).
46 image:two_terminals.png[Two terminals]
48 To move the focus between the two terminals, you can use the direction keys
49 which you may know from the editor +vi+. However, in i3, your homerow is used
50 for these keys (in +vi+, the keys are shifted to the left by one for
51 compatibility with most keyboard layouts). Therefore, +$mod+J+ is left, +$mod+K+
52 is down, +$mod+L+ is up and `$mod+;` is right. So, to switch between the
53 terminals, use +$mod+K+ or +$mod+L+. Of course, you can also use the arrow keys.
55 At the moment, your workspace is split (it contains two terminals) in a
56 specific direction (horizontal by default). Every window can be split
57 horizontally or vertically again, just like the workspace. The terminology is
58 "window" for a container that actually contains an X11 window (like a terminal
59 or browser) and "split container" for containers that consist of one or more
62 TODO: picture of the tree
64 To split a window vertically, press +$mod+v+ before you create the new window.
65 To split it horizontally, press +$mod+h+.
67 === Changing the container layout
69 A split container can have one of the following layouts:
72 Windows are sized so that every window gets an equal amount of space in the
73 container. splith distributes the windows horizontally (windows are right next
74 to each other), splitv distributes them vertically (windows are on top of each
77 Only the focused window in the container is displayed. You get a list of
78 windows at the top of the container.
80 The same principle as +stacking+, but the list of windows at the top is only
81 a single line which is vertically split.
83 To switch modes, press +$mod+e+ for splith/splitv (it toggles), +$mod+s+ for
84 stacking and +$mod+w+ for tabbed.
86 image:modes.png[Container modes]
88 === Toggling fullscreen mode for a window
90 To display a window in fullscreen mode or to go out of fullscreen mode again,
93 There is also a global fullscreen mode in i3 in which the client will span all
94 available outputs (the command is +fullscreen toggle global+).
96 === Opening other applications
98 Aside from opening applications from a terminal, you can also use the handy
99 +dmenu+ which is opened by pressing +$mod+d+ by default. Just type the name
100 (or a part of it) of the application which you want to open. The corresponding
101 application has to be in your +$PATH+ for this to work.
103 Additionally, if you have applications you open very frequently, you can
104 create a keybinding for starting the application directly. See the section
105 <<configuring>> for details.
109 If an application does not provide a mechanism for closing (most applications
110 provide a menu, the escape key or a shortcut like +Control+W+ to close), you
111 can press +$mod+Shift+q+ to kill a window. For applications which support
112 the WM_DELETE protocol, this will correctly close the application (saving
113 any modifications or doing other cleanup). If the application doesn’t support
114 the WM_DELETE protocol your X server will kill the window and the behaviour
115 depends on the application.
119 Workspaces are an easy way to group a set of windows. By default, you are on
120 the first workspace, as the bar on the bottom left indicates. To switch to
121 another workspace, press +$mod+num+ where +num+ is the number of the workspace
122 you want to use. If the workspace does not exist yet, it will be created.
124 A common paradigm is to put the web browser on one workspace, communication
125 applications (+mutt+, +irssi+, ...) on another one, and the ones with which you
126 work, on the third one. Of course, there is no need to follow this approach.
128 If you have multiple screens, a workspace will be created on each screen at
129 startup. If you open a new workspace, it will be bound to the screen you
130 created it on. When you switch to a workspace on another screen, i3 will set
131 focus to that screen.
133 === Moving windows to workspaces
135 To move a window to another workspace, simply press +$mod+Shift+num+ where
136 +num+ is (like when switching workspaces) the number of the target workspace.
137 Similarly to switching workspaces, the target workspace will be created if
138 it does not yet exist.
142 The easiest way to resize a container is by using the mouse: Grab the border
143 and move it to the wanted size.
145 See <<resizingconfig>> for how to configure i3 to be able to resize
146 columns/rows with your keyboard.
148 === Restarting i3 inplace
150 To restart i3 in place (and thus get into a clean state if there is a bug, or
151 to upgrade to a newer version of i3) you can use +$mod+Shift+r+.
155 To cleanly exit i3 without killing your X server, you can use +$mod+Shift+e+.
156 By default, a dialog will ask you to confirm if you really want to quit.
160 Floating mode is the opposite of tiling mode. The position and size of
161 a window are not managed automatically by i3, but manually by
162 you. Using this mode violates the tiling paradigm but can be useful
163 for some corner cases like "Save as" dialog windows, or toolbar
164 windows (GIMP or similar). Those windows usually set the appropriate
165 hint and are opened in floating mode by default.
167 You can toggle floating mode for a window by pressing +$mod+Shift+Space+. By
168 dragging the window’s titlebar with your mouse you can move the window
169 around. By grabbing the borders and moving them you can resize the window. You
170 can also do that by using the <<floating_modifier>>. Another way to resize
171 floating windows using the mouse is to right-click on the titlebar and drag.
173 For resizing floating windows with your keyboard, see <<resizingconfig>>.
175 Floating windows are always on top of tiling windows.
179 i3 stores all information about the X11 outputs, workspaces and layout of the
180 windows on them in a tree. The root node is the X11 root window, followed by
181 the X11 outputs, then dock areas and a content container, then workspaces and
182 finally the windows themselves. In previous versions of i3 we had multiple lists
183 (of outputs, workspaces) and a table for each workspace. That approach turned
184 out to be complicated to use (snapping), understand and implement.
186 === The tree consists of Containers
188 The building blocks of our tree are so called +Containers+. A +Container+ can
189 host a window (meaning an X11 window, one that you can actually see and use,
190 like a browser). Alternatively, it could contain one or more +Containers+. A
191 simple example is the workspace: When you start i3 with a single monitor, a
192 single workspace and you open two terminal windows, you will end up with a tree
195 image::tree-layout2.png["layout2",float="right"]
196 image::tree-shot4.png["shot4",title="Two terminals on standard workspace"]
198 === Orientation and Split Containers
202 It is only natural to use so-called +Split Containers+ in order to build a
203 layout when using a tree as data structure. In i3, every +Container+ has an
204 orientation (horizontal, vertical or unspecified) and the orientation depends
205 on the layout the container is in (vertical for splitv and stacking, horizontal
206 for splith and tabbed). So, in our example with the workspace, the default
207 layout of the workspace +Container+ is splith (most monitors are widescreen
208 nowadays). If you change the layout to splitv (+$mod+v+ in the default config)
209 and *then* open two terminals, i3 will configure your windows like this:
211 image::tree-shot2.png["shot2",title="Vertical Workspace Orientation"]
213 An interesting new feature of i3 since version 4 is the ability to split anything:
214 Let’s assume you have two terminals on a workspace (with splith layout, that is
215 horizontal orientation), focus is on the right terminal. Now you want to open
216 another terminal window below the current one. If you would just open a new
217 terminal window, it would show up to the right due to the splith layout.
218 Instead, press +$mod+v+ to split the container with the splitv layout (to
219 open a +Horizontal Split Container+, use +$mod+h+). Now you can open a new
220 terminal and it will open below the current one:
222 image::tree-layout1.png["Layout",float="right"]
223 image::tree-shot1.png["shot",title="Vertical Split Container"]
227 You probably guessed it already: There is no limit on how deep your hierarchy
232 Let’s stay with our example from above. We have a terminal on the left and two
233 vertically split terminals on the right, focus is on the bottom right one. When
234 you open a new terminal, it will open below the current one.
236 So, how can you open a new terminal window to the *right* of the current one?
237 The solution is to use +focus parent+, which will focus the +Parent Container+ of
238 the current +Container+. In this case, you would focus the +Vertical Split
239 Container+ which is *inside* the horizontally oriented workspace. Thus, now new
240 windows will be opened to the right of the +Vertical Split Container+:
242 image::tree-shot3.png["shot3",title="Focus parent, then open new terminal"]
244 === Implicit containers
246 In some cases, i3 needs to implicitly create a container to fulfill your
249 One example is the following scenario: You start i3 with a single monitor and a
250 single workspace on which you open three terminal windows. All these terminal
251 windows are directly attached to one node inside i3’s layout tree, the
252 workspace node. By default, the workspace node’s orientation is +horizontal+.
254 Now you move one of these terminals down (+$mod+Shift+k+ by default). The
255 workspace node’s orientation will be changed to +vertical+. The terminal window
256 you moved down is directly attached to the workspace and appears on the bottom
257 of the screen. A new (horizontal) container was created to accommodate the
258 other two terminal windows. You will notice this when switching to tabbed mode
259 (for example). You would end up having one tab with a representation of the split
260 container (e.g., "H[urxvt firefox]") and the other one being the terminal window
266 This is where the real fun begins ;-). Most things are very dependent on your
267 ideal working environment so we can’t make reasonable defaults for them.
269 While not using a programming language for the configuration, i3 stays
270 quite flexible in regards to the things you usually want your window manager
273 For example, you can configure bindings to jump to specific windows,
274 you can set specific applications to start on specific workspaces, you can
275 automatically start applications, you can change the colors of i3, and you
276 can bind your keys to do useful things.
278 To change the configuration of i3, copy +/etc/i3/config+ to +\~/.i3/config+
279 (or +~/.config/i3/config+ if you like the XDG directory scheme) and edit it
282 On first start (and on all following starts, unless you have a configuration
283 file), i3 will offer you to create a configuration file. You can tell the
284 wizard to use either Alt (Mod1) or Windows (Mod4) as modifier in the config
285 file. Also, the created config file will use the key symbols of your current
286 keyboard layout. To start the wizard, use the command +i3-config-wizard+.
287 Please note that you must not have +~/.i3/config+, otherwise the wizard will
292 It is possible and recommended to use comments in your configuration file to
293 properly document your setup for later reference. Comments are started with
294 a # and can only be used at the beginning of a line:
305 i3 has support for both X core fonts and FreeType fonts (through Pango) to
306 render window titles.
308 To generate an X core font description, you can use +xfontsel(1)+. To see
309 special characters (Unicode), you need to use a font which supports the
312 A FreeType font description is composed by a font family, a style, a weight,
313 a variant, a stretch and a size.
314 FreeType fonts support right-to-left rendering and contain often more
315 Unicode glyphs than X core fonts.
317 If i3 cannot open the configured font, it will output an error in the logfile
318 and fall back to a working font.
321 ------------------------------
322 font <X core font description>
323 font pango:[family list] [style options] [size]
324 ------------------------------
327 --------------------------------------------------------------
328 font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
329 font pango:DejaVu Sans Mono 10
330 font pango:DejaVu Sans Mono, Terminus Bold Semi-Condensed 11
331 font pango:Terminus 11px
332 --------------------------------------------------------------
336 === Keyboard bindings
338 A keyboard binding makes i3 execute a command (see below) upon pressing a
339 specific key. i3 allows you to bind either on keycodes or on keysyms (you can
340 also mix your bindings, though i3 will not protect you from overlapping ones).
342 * A keysym (key symbol) is a description for a specific symbol, like "a"
343 or "b", but also more strange ones like "underscore" instead of "_". These
344 are the ones you use in Xmodmap to remap your keys. To get the current
345 mapping of your keys, use +xmodmap -pke+. To interactively enter a key and
346 see what keysym it is configured to, use +xev+.
348 * Keycodes do not need to have a symbol assigned (handy for custom vendor
349 hotkeys on some notebooks) and they will not change their meaning as you
350 switch to a different keyboard layout (when using +xmodmap+).
352 My recommendation is: If you often switch keyboard layouts but you want to keep
353 your bindings in the same physical location on the keyboard, use keycodes.
354 If you don’t switch layouts, and want a clean and simple config file, use
357 Some tools (such as +import+ or +xdotool+) might be unable to run upon a
358 KeyPress event, because the keyboard/pointer is still grabbed. For these
359 situations, the +--release+ flag can be used, which will execute the command
360 after the keys have been released.
363 ----------------------------------
364 bindsym [--release] [Modifiers+]keysym command
365 bindcode [--release] [Modifiers+]keycode command
366 ----------------------------------
369 --------------------------------
371 bindsym $mod+f fullscreen toggle
374 bindsym $mod+Shift+r restart
376 # Notebook-specific hotkeys
377 bindcode 214 exec --no-startup-id /home/michael/toggle_beamer.sh
379 # Simulate ctrl+v upon pressing $mod+x
380 bindsym --release $mod+x exec --no-startup-id xdotool key --clearmodifiers ctrl+v
382 # Take a screenshot upon pressing $mod+x (select an area)
383 bindsym --release $mod+x exec --no-startup-id import /tmp/latest-screenshot.png
384 --------------------------------
388 Mod1-Mod5, Shift, Control::
389 Standard modifiers, see +xmodmap(1)+
392 Unlike other window managers, i3 can use Mode_switch as a modifier. This allows
393 you to remap capslock (for example) to Mode_switch and use it for both: typing
394 umlauts or special characters 'and' having some comfortably reachable key
395 bindings. For example, when typing, capslock+1 or capslock+2 for switching
396 workspaces is totally convenient. Try it :-).
402 A mouse binding makes i3 execute a command upon pressing a specific mouse
403 button in the scope of the clicked container (see <<command_criteria>>). You
404 can configure mouse bindings in a similar way to key bindings.
407 ----------------------------------
408 bindsym [--release] [--border] [--whole-window] [Modifiers+]button[n] command
409 ----------------------------------
411 By default, the binding will only run when you click on the titlebar of the
412 window. If the +--release+ flag is given, it will run when the mouse button
415 If the +--whole-window+ flag is given, the binding will also run when any part
416 of the window is clicked, with the exception of the border. To have a bind run
417 when the border is clicked, specify the +--border+ flag.
420 --------------------------------
421 # The middle button over a titlebar kills the window
422 bindsym --release button2 kill
424 # The middle button and a modifer over any part of the window kills the window
425 bindsym --whole-window $mod+button2 kill
427 # The right button toggles floating
428 bindsym button3 floating toggle
429 bindsym $mod+button3 floating toggle
431 # The side buttons move the window around
432 bindsym button9 move left
433 bindsym button8 move right
434 --------------------------------
436 [[floating_modifier]]
438 === The floating modifier
440 To move floating windows with your mouse, you can either grab their titlebar
441 or configure the so called floating modifier which you can then press and
442 click anywhere in the window itself to move it. The most common setup is to
443 use the same key you use for managing windows (Mod1 for example). Then
444 you can press Mod1, click into a window using your left mouse button, and drag
445 it to the position you want.
447 When holding the floating modifier, you can resize a floating window by
448 pressing the right mouse button on it and moving around while holding it. If
449 you hold the shift button as well, the resize will be proportional (the aspect
450 ratio will be preserved).
453 --------------------------------
454 floating_modifier <Modifiers>
455 --------------------------------
458 --------------------------------
459 floating_modifier Mod1
460 --------------------------------
462 === Constraining floating window size
464 The maximum and minimum dimensions of floating windows can be specified. If
465 either dimension of +floating_maximum_size+ is specified as -1, that dimension
466 will be unconstrained with respect to its maximum value. If either dimension of
467 +floating_maximum_size+ is undefined, or specified as 0, i3 will use a default
468 value to constrain the maximum size. +floating_minimum_size+ is treated in a
469 manner analogous to +floating_maximum_size+.
472 ----------------------------------------
473 floating_minimum_size <width> x <height>
474 floating_maximum_size <width> x <height>
475 ----------------------------------------
478 --------------------------------------
479 floating_minimum_size 75 x 50
480 floating_maximum_size -1 x -1
481 --------------------------------------
483 === Orientation for new workspaces
485 New workspaces get a reasonable default orientation: Wide-screen monitors
486 (anything wider than high) get horizontal orientation, rotated monitors
487 (anything higher than wide) get vertical orientation.
489 With the +default_orientation+ configuration directive, you can override that
493 ----------------------------------------------
494 default_orientation <horizontal|vertical|auto>
495 ----------------------------------------------
498 ----------------------------
499 default_orientation vertical
500 ----------------------------
502 === Layout mode for new containers
504 This option determines in which mode new containers on workspace level will
506 ///////////////////////////////
507 See also <<stack-limit>>.
508 //////////////////////////////
511 ---------------------------------------------
512 workspace_layout <default|stacking|tabbed>
513 ---------------------------------------------
514 /////////////////////////////////////////////
515 new_container stack-limit <cols|rows> <value>
516 /////////////////////////////////////////////
519 ---------------------
520 workspace_layout tabbed
521 ---------------------
523 === Border style for new windows
525 This option determines which border style new windows will have. The default is
526 "normal". Note that new_float applies only to windows which are starting out as
527 floating windows, e.g. dialog windows.
530 ---------------------------------------------
531 new_window <normal|1pixel|none|pixel>
532 new_float <normal|1pixel|none|pixel>
533 ---------------------------------------------
536 ---------------------
538 ---------------------
540 The "normal" and "pixel" border styles support an optional border width in
544 ---------------------
545 # The same as new_window none
550 ---------------------
553 === Hiding vertical borders
555 You can hide vertical borders adjacent to the screen edges using
556 +hide_edge_borders+. This is useful if you are using scrollbars, or do not want
557 to waste even two pixels in displayspace. Default is none.
560 ----------------------------
561 hide_edge_borders <none|vertical|horizontal|both>
562 ----------------------------
565 ----------------------
566 hide_edge_borders vertical
567 ----------------------
569 === Arbitrary commands for specific windows (for_window)
571 With the +for_window+ command, you can let i3 execute any command when it
572 encounters a specific window. This can be used to set windows to floating or to
573 change their border style, for example.
576 -----------------------------
577 for_window <criteria> command
578 -----------------------------
581 ------------------------------------------------
582 # enable floating mode for all XTerm windows
583 for_window [class="XTerm"] floating enable
585 # Make all urxvts use a 1-pixel border:
586 for_window [class="urxvt"] border 1pixel
588 # A less useful, but rather funny example:
589 # makes the window floating as soon as I change
590 # directory to ~/work
591 for_window [title="x200: ~/work"] floating enable
592 ------------------------------------------------
594 The valid criteria are the same as those for commands, see <<command_criteria>>.
596 === Don't focus window upon opening
600 When a new window appears, it will be focused. The +no_focus+ directive allows preventing
601 this from happening and can be used in combination with <<command_criteria>>.
603 Note that this does not apply to all cases, e.g., when feeding data into a running application
604 causing it to request being focused. To configure the behavior in such cases, refer to
605 <<focus_on_window_activation>>.
613 -------------------------------
614 no_focus [window_role="pop-up"]
615 -------------------------------
619 As you learned in the section about keyboard bindings, you will have
620 to configure lots of bindings containing modifier keys. If you want to save
621 yourself some typing and be able to change the modifier you use later,
622 variables can be handy.
630 ------------------------
632 bindsym $m+Shift+r restart
633 ------------------------
635 Variables are directly replaced in the file when parsing. Variables expansion
636 is not recursive so it is not possible to define a variable with a value
637 containing another variable. There is no fancy handling and there are
638 absolutely no plans to change this. If you need a more dynamic configuration
639 you should create a little script which generates a configuration file and run
640 it before starting i3 (for example in your +~/.xsession+ file).
642 === Automatically putting clients on specific workspaces
646 To automatically make a specific window show up on a specific workspace, you
647 can use an *assignment*. You can match windows by using any criteria,
648 see <<command_criteria>>. It is recommended that you match on window classes
649 (and instances, when appropriate) instead of window titles whenever possible
650 because some applications first create their window, and then worry about
651 setting the correct title. Firefox with Vimperator comes to mind. The window
652 starts up being named Firefox, and only when Vimperator is loaded does the
653 title change. As i3 will get the title as soon as the application maps the
654 window (mapping means actually displaying it on the screen), you’d need to have
655 to match on 'Firefox' in this case.
657 Assignments are processed by i3 in the order in which they appear in the config
658 file. The first one which matches the window wins and later assignments are not
662 ------------------------------------------------------------
663 assign <criteria> [→] workspace
664 ------------------------------------------------------------
667 ----------------------
668 # Assign URxvt terminals to workspace 2
669 assign [class="URxvt"] 2
671 # Same thing, but more precise (exact match instead of substring)
672 assign [class="^URxvt$"] 2
674 # Same thing, but with a beautiful arrow :)
675 assign [class="^URxvt$"] → 2
677 # Assignment to a named workspace
678 assign [class="^URxvt$"] → work
680 # Start urxvt -name irssi
681 assign [class="^URxvt$" instance="^irssi$"] → 3
682 ----------------------
684 Note that the arrow is not required, it just looks good :-). If you decide to
685 use it, it has to be a UTF-8 encoded arrow, not `->` or something like that.
687 To get the class and instance, you can use +xprop+. After clicking on the
688 window, you will see the following output:
691 -----------------------------------
692 WM_CLASS(STRING) = "irssi", "URxvt"
693 -----------------------------------
695 The first part of the WM_CLASS is the instance ("irssi" in this example), the
696 second part is the class ("URxvt" in this example).
698 Should you have any problems with assignments, make sure to check the i3
699 logfile first (see http://i3wm.org/docs/debugging.html). It includes more
700 details about the matching process and the window’s actual class, instance and
701 title when starting up.
703 Note that if you want to start an application just once on a specific
704 workspace, but you don’t want to assign all instances of it permanently, you
705 can make use of i3’s startup-notification support (see <<exec>>) in your config
706 file in the following way:
708 *Start iceweasel on workspace 3 (once)*:
709 -------------------------------------------------------------------------------
710 # Start iceweasel on workspace 3, then switch back to workspace 1
711 # (Being a command-line utility, i3-msg does not support startup notifications,
712 # hence the exec --no-startup-id.)
713 # (Starting iceweasel with i3’s exec command is important in order to make i3
714 # create a startup notification context, without which the iceweasel window(s)
715 # cannot be matched onto the workspace on which the command was started.)
716 exec --no-startup-id i3-msg 'workspace 3; exec iceweasel; workspace 1'
717 -------------------------------------------------------------------------------
719 === Automatically starting applications on i3 startup
721 By using the +exec+ keyword outside a keybinding, you can configure
722 which commands will be performed by i3 on initial startup. +exec+
723 commands will not run when restarting i3, if you need a command to run
724 also when restarting i3 you should use the +exec_always+
725 keyword. These commands will be run in order.
727 See <<command_chaining>> for details on the special meaning of +;+ (semicolon)
728 and +,+ (comma): they chain commands together in i3, so you need to use quoted
729 strings if they appear in your command.
733 exec [--no-startup-id] command
734 exec_always [--no-startup-id] command
738 --------------------------------
740 exec_always ~/my_script.sh
742 # Execute the terminal emulator urxvt, which is not yet startup-notification aware.
743 exec --no-startup-id urxvt
744 --------------------------------
746 The flag --no-startup-id is explained in <<exec>>.
750 === Automatically putting workspaces on specific screens
752 If you assign clients to workspaces, it might be handy to put the
753 workspaces on specific screens. Also, the assignment of workspaces to screens
754 will determine which workspace i3 uses for a new screen when adding screens
755 or when starting (e.g., by default it will use 1 for the first screen, 2 for
756 the second screen and so on).
759 ----------------------------------
760 workspace <workspace> output <output>
761 ----------------------------------
763 The 'output' is the name of the RandR output you attach your screen to. On a
764 laptop, you might have VGA1 and LVDS1 as output names. You can see the
765 available outputs by running +xrandr --current+.
767 If you use named workspaces, they must be quoted:
770 ---------------------------
771 workspace 1 output LVDS1
772 workspace 5 output VGA1
773 workspace "2: vim" output VGA1
774 ---------------------------
778 You can change all colors which i3 uses to draw the window decorations.
781 --------------------------------------------
782 colorclass border background text indicator
783 --------------------------------------------
785 Where colorclass can be one of:
788 A client which currently has the focus.
789 client.focused_inactive::
790 A client which is the focused one of its container, but it does not have
791 the focus at the moment.
793 A client which is not the focused one of its container.
795 A client which has its urgency hint activated.
797 Background and text color are used to draw placeholder window contents
798 (when restoring layouts). Border and indicator are ignored.
800 You can also specify the color to be used to paint the background of the client
801 windows. This color will be used to paint the window on top of which the client
805 -----------------------
806 client.background color
807 -----------------------
809 Only clients that do not cover the whole area of this window expose the color
812 Colors are in HTML hex format (#rrggbb), see the following example:
814 *Examples (default colors)*:
815 ---------------------------------------------------------
816 # class border backgr. text indicator
817 client.focused #4c7899 #285577 #ffffff #2e9ef4
818 client.focused_inactive #333333 #5f676a #ffffff #484e50
819 client.unfocused #333333 #222222 #888888 #292d2e
820 client.urgent #2f343a #900000 #ffffff #900000
821 client.placeholder #000000 #0c0c0c #ffffff #000000
822 ---------------------------------------------------------
824 Note that for the window decorations, the color around the child window is the
825 background color, and the border color is only the two thin lines at the top of
828 The indicator color is used for indicating where a new window will be opened.
829 For horizontal split containers, the right border will be painted in indicator
830 color, for vertical split containers, the bottom border. This only applies to
831 single windows within a split container, which are otherwise indistinguishable
832 from single windows outside of a split container.
834 === Interprocess communication
836 i3 uses Unix sockets to provide an IPC interface. This allows third-party
837 programs to get information from i3, such as the current workspaces
838 (to display a workspace bar), and to control i3.
840 The IPC socket is enabled by default and will be created in
841 +/tmp/i3-%u.XXXXXX/ipc-socket.%p+ where +%u+ is your UNIX username, +%p+ is
842 the PID of i3 and XXXXXX is a string of random characters from the portable
843 filename character set (see mkdtemp(3)).
845 You can override the default path through the environment-variable +I3SOCK+ or
846 by specifying the +ipc-socket+ directive. This is discouraged, though, since i3
847 does the right thing by default. If you decide to change it, it is strongly
848 recommended to set this to a location in your home directory so that no other
849 user can create that directory.
852 ----------------------------
853 ipc-socket ~/.i3/i3-ipc.sock
854 ----------------------------
856 You can then use the +i3-msg+ application to perform any command listed in
859 === Focus follows mouse
861 By default, window focus follows your mouse movements. However, if you have a
862 setup where your mouse usually is in your way (like a touchpad on your laptop
863 which you do not want to disable completely), you might want to disable 'focus
864 follows mouse' and control focus only by using your keyboard. The mouse will
865 still be useful inside the currently active window (for example to click on
866 links in your browser window).
869 ----------------------------
870 focus_follows_mouse <yes|no>
871 ----------------------------
874 ----------------------
875 focus_follows_mouse no
876 ----------------------
880 By default, when switching focus to a window on a different output (e.g.
881 focusing a window on workspace 3 on output VGA-1, coming from workspace 2 on
882 LVDS-1), the mouse cursor is warped to the center of that window.
884 With the +mouse_warping+ option, you can control when the mouse cursor should
885 be warped. +none+ disables warping entirely, whereas +output+ is the default
886 behavior described above.
889 ---------------------------
890 mouse_warping <output|none>
891 ---------------------------
898 === Popups during fullscreen mode
900 When you are in fullscreen mode, some applications still open popup windows
901 (take Xpdf for example). This is because these applications may not be aware
902 that they are in fullscreen mode (they do not check the corresponding hint).
903 There are three things which are possible to do in this situation:
905 1. Display the popup if it belongs to the fullscreen application only. This is
906 the default and should be reasonable behavior for most users.
907 2. Just ignore the popup (don’t map it). This won’t interrupt you while you are
908 in fullscreen. However, some apps might react badly to this (deadlock until
909 you go out of fullscreen).
910 3. Leave fullscreen mode.
913 -------------------------------------------------
914 popup_during_fullscreen <smart|ignore|leave_fullscreen>
915 -------------------------------------------------
918 ------------------------------
919 popup_during_fullscreen smart
920 ------------------------------
924 When being in a tabbed or stacked container, the first container will be
925 focused when you use +focus down+ on the last container -- the focus wraps. If
926 however there is another stacked/tabbed container in that direction, focus will
927 be set on that container. This is the default behavior so you can navigate to
928 all your windows without having to use +focus parent+.
930 If you want the focus to *always* wrap and you are aware of using +focus
931 parent+ to switch to different containers, you can use the
932 +force_focus_wrapping+ configuration directive. After enabling it, the focus
936 -----------------------------
937 force_focus_wrapping <yes|no>
938 -----------------------------
941 ------------------------
942 force_focus_wrapping yes
943 ------------------------
947 As explained in-depth in <http://i3wm.org/docs/multi-monitor.html>, some X11
948 video drivers (especially the nVidia binary driver) only provide support for
949 Xinerama instead of RandR. In such a situation, i3 must be told to use the
950 inferior Xinerama API explicitly and therefore don’t provide support for
951 reconfiguring your screens on the fly (they are read only once on startup and
954 For people who cannot modify their +~/.xsession+ to add the
955 +--force-xinerama+ commandline parameter, a configuration option is provided:
958 -----------------------
959 force_xinerama <yes|no>
960 -----------------------
967 Also note that your output names are not descriptive (like +HDMI1+) when using
968 Xinerama, instead they are counted up, starting at 0: +xinerama-0+, +xinerama-1+, …
970 === Automatic back-and-forth when switching to the current workspace
972 This configuration directive enables automatic +workspace back_and_forth+ (see
973 <<back_and_forth>>) when switching to the workspace that is currently focused.
975 For instance: Assume you are on workspace "1: www" and switch to "2: IM" using
976 mod+2 because somebody sent you a message. You don’t need to remember where you
977 came from now, you can just press $mod+2 again to switch back to "1: www".
980 --------------------------------------
981 workspace_auto_back_and_forth <yes|no>
982 --------------------------------------
985 ---------------------------------
986 workspace_auto_back_and_forth yes
987 ---------------------------------
989 === Delaying urgency hint reset on workspace change
991 If an application on another workspace sets an urgency hint, switching to this
992 workspace may lead to immediate focus of the application, which also means the
993 window decoration color would be immediately reset to +client.focused+. This
994 may make it unnecessarily hard to tell which window originally raised the
997 In order to prevent this, you can tell i3 to delay resetting the urgency state
998 by a certain time using the +force_display_urgency_hint+ directive. Setting the
999 value to 0 disables this feature.
1001 The default is 500ms.
1004 ---------------------------------------
1005 force_display_urgency_hint <timeout> ms
1006 ---------------------------------------
1009 ---------------------------------
1010 force_display_urgency_hint 500 ms
1011 ---------------------------------
1013 === Delaying exiting on zero displays
1015 Outputs may disappear momentarily and come back later. For example,
1016 using a docking station that does not announce the undock (e.g. ACPI Undock
1017 event triggered through manually pushing a button before actually ejecting
1018 the notebook). During the removal of the notebook from the docking station,
1019 all outputs disappear momentarily.
1021 To prevent i3 from exiting when no output is available momentarily, you can
1022 tell i3 to delay a certain time first and check available outputs again using
1023 the +delay_exit_on_zero_displays+ directive. Setting the value to 0 disables
1026 The default is 500ms.
1029 ----------------------------------------
1030 delay_exit_on_zero_displays <timeout> ms
1031 ----------------------------------------
1034 ----------------------------------
1035 delay_exit_on_zero_displays 500 ms
1036 ----------------------------------
1038 === Focus on window activation
1040 [[focus_on_window_activation]]
1042 If a window is activated, e.g., via +google-chrome www.google.com+, it may request
1043 to take focus. Since this may not preferable, different reactions can be configured.
1045 Note that this may not affect windows that are being opened. To prevent new windows
1046 from being focused, see <<no_focus>>.
1049 ----------------------------------------------------
1050 focus_on_window_activation <smart|urgent|focus|none>
1051 ----------------------------------------------------
1053 The different modes will act as follows:
1056 This is the default behavior. If the window requesting focus is on an active
1057 workspace, it will receive the focus. Otherwise, the urgency hint will be set.
1059 The window will always be marked urgent, but the focus will not be stolen.
1061 The window will always be focused and not be marked urgent.
1063 The window will neither be focused, nor be marked urgent.
1065 === Drawing marks on window decoration
1067 If activated, marks on windows are drawn in their window decoration. However,
1068 any mark starting with an underscore in its name (+_+) will not be drawn even if
1069 this option is activated.
1071 The default for this option is +yes+.
1083 == Configuring i3bar
1085 The bar at the bottom of your monitor is drawn by a separate process called
1086 i3bar. Having this part of "the i3 user interface" in a separate process has
1089 1. It is a modular approach. If you don’t need a workspace bar at all, or if
1090 you prefer a different one (dzen2, xmobar, maybe even gnome-panel?), you can
1091 just remove the i3bar configuration and start your favorite bar instead.
1092 2. It follows the UNIX philosophy of "Make each program do one thing well".
1093 While i3 manages your windows well, i3bar is good at displaying a bar on
1094 each monitor (unless you configure it otherwise).
1095 3. It leads to two separate, clean codebases. If you want to understand i3, you
1096 don’t need to bother with the details of i3bar and vice versa.
1098 That said, i3bar is configured in the same configuration file as i3. This is
1099 because it is tightly coupled with i3 (in contrary to i3lock or i3status which
1100 are useful for people using other window managers). Therefore, it makes no
1101 sense to use a different configuration place when we already have a good
1102 configuration infrastructure in place.
1104 Configuring your workspace bar starts with opening a +bar+ block. You can have
1105 multiple bar blocks to use different settings for different outputs (monitors):
1108 ---------------------------
1110 status_command i3status
1112 ---------------------------
1116 By default i3 will just pass +i3bar+ and let your shell handle the execution,
1117 searching your +$PATH+ for a correct version.
1118 If you have a different +i3bar+ somewhere or the binary is not in your +$PATH+ you can
1119 tell i3 what to execute.
1121 The specified command will be passed to +sh -c+, so you can use globbing and
1122 have to have correct quoting etc.
1125 ----------------------
1126 i3bar_command command
1127 ----------------------
1130 -------------------------------------------------
1132 i3bar_command /home/user/bin/i3bar
1134 -------------------------------------------------
1137 === Statusline command
1139 i3bar can run a program and display every line of its +stdout+ output on the
1140 right hand side of the bar. This is useful to display system information like
1141 your current IP address, battery status or date/time.
1143 The specified command will be passed to +sh -c+, so you can use globbing and
1144 have to have correct quoting etc.
1147 ----------------------
1148 status_command command
1149 ----------------------
1152 -------------------------------------------------
1154 status_command i3status --config ~/.i3status.conf
1156 -------------------------------------------------
1160 You can either have i3bar be visible permanently at one edge of the screen
1161 (+dock+ mode) or make it show up when you press your modifier key (+hide+ mode).
1162 It is also possible to force i3bar to always stay hidden (+invisible+
1163 mode). The modifier key can be configured using the +modifier+ option.
1165 The mode option can be changed during runtime through the +bar mode+ command.
1166 On reload the mode will be reverted to its configured value.
1168 The hide mode maximizes screen space that can be used for actual windows. Also,
1169 i3bar sends the +SIGSTOP+ and +SIGCONT+ signals to the statusline process to
1172 Invisible mode allows to permanently maximize screen space, as the bar is never
1173 shown. Thus, you can configure i3bar to not disturb you by popping up because
1174 of an urgency hint or because the modifier key is pressed.
1176 In order to control whether i3bar is hidden or shown in hide mode, there exists
1177 the hidden_state option, which has no effect in dock mode or invisible mode. It
1178 indicates the current hidden_state of the bar: (1) The bar acts like in normal
1179 hide mode, it is hidden and is only unhidden in case of urgency hints or by
1180 pressing the modifier key (+hide+ state), or (2) it is drawn on top of the
1181 currently visible workspace (+show+ state).
1183 Like the mode, the hidden_state can also be controlled through i3, this can be
1184 done by using the +bar hidden_state+ command.
1186 The default mode is dock mode; in hide mode, the default modifier is Mod4 (usually
1187 the windows key). The default value for the hidden_state is hide.
1191 mode <dock|hide|invisible>
1192 hidden_state <hide|show>
1205 Available modifiers are Mod1-Mod5, Shift, Control (see +xmodmap(1)+).
1207 === Mouse button commands
1209 Specifies a command to run when a button was pressed on i3bar to override the
1210 default behavior. Currently only the mouse wheel buttons are supported. This is
1211 useful for disabling the scroll wheel action or running scripts that implement
1212 custom behavior for these buttons.
1215 ---------------------
1216 wheel_up_cmd <command>
1217 wheel_down_cmd <command>
1218 ---------------------
1221 ---------------------
1224 wheel_down_cmd exec ~/.i3/scripts/custom_wheel_down
1226 ---------------------
1230 Specifies the bar ID for the configured bar instance. If this option is missing,
1231 the ID is set to 'bar-x', where x corresponds to the position of the embedding
1232 bar block in the config file ('bar-0', 'bar-1', ...).
1235 ---------------------
1237 ---------------------
1240 ---------------------
1244 ---------------------
1249 This option determines in which edge of the screen i3bar should show up.
1251 The default is bottom.
1254 ---------------------
1255 position <top|bottom>
1256 ---------------------
1259 ---------------------
1263 ---------------------
1267 You can restrict i3bar to one or more outputs (monitors). The default is to
1268 handle all outputs. Restricting the outputs is useful for using different
1269 options for different outputs by using multiple 'bar' blocks.
1271 To make a particular i3bar instance handle multiple outputs, specify the output
1272 directive multiple times.
1280 -------------------------------
1281 # big monitor: everything
1283 # The display is connected either via HDMI or via DisplayPort
1286 status_command i3status
1289 # laptop monitor: bright colors and i3status with less modules.
1292 status_command i3status --config ~/.i3status-small.conf
1298 -------------------------------
1302 i3bar by default provides a system tray area where programs such as
1303 NetworkManager, VLC, Pidgin, etc. can place little icons.
1305 You can configure on which output (monitor) the icons should be displayed or
1306 you can turn off the functionality entirely.
1309 -------------------------
1310 tray_output <none|primary|output>
1311 -------------------------
1314 -------------------------
1315 # disable system tray
1320 # show tray icons on the primary monitor
1323 # show tray icons on the big monitor
1327 -------------------------
1329 Note that you might not have a primary output configured yet. To do so, run:
1330 -------------------------
1331 xrandr --output <output> --primary
1332 -------------------------
1336 Specifies the font to be used in the bar. See <<fonts>>.
1339 ---------------------
1341 ---------------------
1344 --------------------------------------------------------------
1346 font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
1347 font pango:DejaVu Sans Mono 10
1349 --------------------------------------------------------------
1351 === Custom separator symbol
1353 Specifies a custom symbol to be used for the separator as opposed to the vertical,
1354 one pixel thick separator.
1357 -------------------------
1358 separator_symbol <symbol>
1359 -------------------------
1362 ------------------------
1364 separator_symbol ":|:"
1366 ------------------------
1368 === Workspace buttons
1370 Specifies whether workspace buttons should be shown or not. This is useful if
1371 you want to display a statusline-only bar containing additional information.
1373 The default is to show workspace buttons.
1376 --------------------------
1377 workspace_buttons <yes|no>
1378 --------------------------
1381 ------------------------
1383 workspace_buttons no
1385 ------------------------
1387 === Strip workspace numbers
1389 Specifies whether workspace numbers should be displayed within the workspace
1390 buttons. This is useful if you want to have a named workspace that stays in
1391 order on the bar according to its number without displaying the number prefix.
1393 When +strip_workspace_numbers+ is set to +yes+, any workspace that has a name of
1394 the form "[n]:[NAME]" will display only the name. You could use this, for
1395 instance, to display Roman numerals rather than digits by naming your
1396 workspaces to "1:I", "2:II", "3:III", "4:IV", ...
1398 The default is to display the full name within the workspace button.
1401 ----------------------------------
1402 strip_workspace_numbers <yes|no>
1403 ----------------------------------
1406 ----------------------------
1408 strip_workspace_numbers yes
1410 ----------------------------
1412 === Binding Mode indicator
1414 Specifies whether the current binding mode indicator should be shown or not.
1415 This is useful if you want to hide the workspace buttons but still be able
1416 to see the current binding mode indicator.
1417 For an example of a +mode+ definition, see <<resizingconfig>>.
1419 The default is to show the mode indicator.
1422 -------------------------------
1423 binding_mode_indicator <yes|no>
1424 -------------------------------
1427 -----------------------------
1429 binding_mode_indicator no
1431 -----------------------------
1435 As with i3, colors are in HTML hex format (#rrggbb). The following colors can
1436 be configured at the moment:
1439 Background color of the bar.
1441 Text color to be used for the statusline.
1443 Text color to be used for the separator.
1445 Border, background and text color for a workspace button when the workspace
1448 Border, background and text color for a workspace button when the workspace
1449 is active (visible) on some output, but the focus is on another one.
1450 You can only tell this apart from the focused workspace when you are
1451 using multiple monitors.
1452 inactive_workspace::
1453 Border, background and text color for a workspace button when the workspace
1454 does not have focus and is not active (visible) on any output. This
1455 will be the case for most workspaces.
1457 Border, background and text color for a workspace button when the workspace
1458 contains a window with the urgency hint set. Also applies to +mode+ indicators.
1461 ----------------------------------------
1467 colorclass <border> <background> <text>
1469 ----------------------------------------
1471 *Example (default colors)*:
1472 --------------------------------------
1479 focused_workspace #4c7899 #285577 #ffffff
1480 active_workspace #333333 #5f676a #ffffff
1481 inactive_workspace #333333 #222222 #888888
1482 urgent_workspace #2f343a #900000 #ffffff
1485 --------------------------------------
1489 Commands are what you bind to specific keypresses. You can also issue commands
1490 at runtime without pressing a key by using the IPC interface. An easy way to
1491 do this is to use the +i3-msg+ utility:
1494 --------------------------
1495 # execute this on your shell to make the current container borderless
1497 --------------------------
1499 [[command_chaining]]
1501 Commands can be chained by using +;+ (a semicolon). So, to move a window to a
1502 specific workspace and immediately switch to that workspace, you can configure
1503 the following keybinding:
1506 --------------------------------------------------------
1507 bindsym $mod+x move container to workspace 3; workspace 3
1508 --------------------------------------------------------
1510 [[command_criteria]]
1512 Furthermore, you can change the scope of a command - that is, which containers
1513 should be affected by that command, by using various criteria. The criteria
1514 are specified before any command in a pair of square brackets and are separated
1517 When using multiple commands, separate them by using a +,+ (a comma) instead of
1518 a semicolon. Criteria apply only until the next semicolon, so if you use a
1519 semicolon to separate commands, only the first one will be executed for the
1523 ------------------------------------
1524 # if you want to kill all windows which have the class Firefox, use:
1525 bindsym $mod+x [class="Firefox"] kill
1527 # same thing, but case-insensitive
1528 bindsym $mod+x [class="(?i)firefox"] kill
1530 # kill only the About dialog from Firefox
1531 bindsym $mod+x [class="Firefox" window_role="About"] kill
1533 # enable floating mode and move container to workspace 4
1534 for_window [class="^evil-app$"] floating enable, move container to workspace 4
1535 ------------------------------------
1537 The criteria which are currently implemented are:
1540 Compares the window class (the second part of WM_CLASS)
1542 Compares the window instance (the first part of WM_CLASS)
1544 Compares the window role (WM_WINDOW_ROLE).
1546 Compare the window type (_NET_WM_WINDOW_TYPE). Possible values are
1547 +normal+, +dialog+, +utility+, +toolbar+, +splash+, +menu+, +dropdown_menu+,
1548 +popup_menu+ and +toolti+.
1550 Compares the X11 window ID, which you can get via +xwininfo+ for example.
1552 Compares the X11 window title (_NET_WM_NAME or WM_NAME as fallback).
1554 Compares the urgent state of the window. Can be "latest" or "oldest".
1555 Matches the latest or oldest urgent window, respectively.
1556 (The following aliases are also available: newest, last, recent, first)
1558 Compares the mark set for this container, see <<vim_like_marks>>.
1560 Compares the i3-internal container ID, which you can get via the IPC
1561 interface. Handy for scripting.
1563 The criteria +class+, +instance+, +role+, +title+ and +mark+ are actually
1564 regular expressions (PCRE). See +pcresyntax(3)+ or +perldoc perlre+ for
1565 information on how to use them.
1569 === Executing applications (exec)
1571 What good is a window manager if you can’t actually start any applications?
1572 The exec command starts an application by passing the command you specify to a
1573 shell. This implies that you can use globbing (wildcards) and programs will be
1574 searched in your +$PATH+.
1576 See <<command_chaining>> for details on the special meaning of +;+ (semicolon)
1577 and +,+ (comma): they chain commands together in i3, so you need to use quoted
1578 strings if they appear in your command.
1581 ------------------------------
1582 exec [--no-startup-id] command
1583 ------------------------------
1586 ------------------------------
1588 bindsym $mod+g exec gimp
1590 # Start the terminal emulator urxvt which is not yet startup-notification-aware
1591 bindsym $mod+Return exec --no-startup-id urxvt
1592 ------------------------------
1594 The +--no-startup-id+ parameter disables startup-notification support for this
1595 particular exec command. With startup-notification, i3 can make sure that a
1596 window appears on the workspace on which you used the exec command. Also, it
1597 will change the X11 cursor to +watch+ (a clock) while the application is
1598 launching. So, if an application is not startup-notification aware (most GTK
1599 and Qt using applications seem to be, though), you will end up with a watch
1600 cursor for 60 seconds.
1602 === Splitting containers
1604 The split command makes the current window a split container. Split containers
1605 can contain multiple windows. Depending on the layout of the split container,
1606 new windows get placed to the right of the current one (splith) or new windows
1607 get placed below the current one (splitv).
1609 If you apply this command to a split container with the same orientation,
1610 nothing will happen. If you use a different orientation, the split container’s
1611 orientation will be changed (if it does not have more than one window). Use
1612 +layout toggle split+ to change the layout of any split container from splitv
1613 to splith or vice-versa.
1616 ---------------------------
1617 split <vertical|horizontal>
1618 ---------------------------
1621 ------------------------------
1622 bindsym $mod+v split vertical
1623 bindsym $mod+h split horizontal
1624 ------------------------------
1626 === Manipulating layout
1628 Use +layout toggle split+, +layout stacking+, +layout tabbed+, +layout splitv+
1629 or +layout splith+ to change the current container layout to splith/splitv,
1630 stacking, tabbed layout, splitv or splith, respectively.
1632 To make the current window (!) fullscreen, use +fullscreen enable+ (or
1633 +fullscreen enable global+ for the global mode), to leave either fullscreen
1634 mode use +fullscreen disable+, and to toggle between these two states use
1635 +fullscreen toggle+ (or +fullscreen toggle global+).
1637 Likewise, to make the current window floating (or tiling again) use +floating
1638 enable+ respectively +floating disable+ (or +floating toggle+):
1642 layout <default|tabbed|stacking|splitv|splith>
1643 layout toggle [split|all]
1648 bindsym $mod+s layout stacking
1649 bindsym $mod+l layout toggle split
1650 bindsym $mod+w layout tabbed
1652 # Toggle between stacking/tabbed/split:
1653 bindsym $mod+x layout toggle
1655 # Toggle between stacking/tabbed/splith/splitv:
1656 bindsym $mod+x layout toggle all
1659 bindsym $mod+f fullscreen toggle
1661 # Toggle floating/tiling
1662 bindsym $mod+t floating toggle
1665 === Focusing/Moving containers
1667 To change the focus, use the focus command: +focus left+, +focus right+, +focus
1668 down+ and +focus up+.
1670 There are a few special parameters you can use for the focus command:
1673 Sets focus to the +Parent Container+ of the current +Container+.
1675 The opposite of +focus parent+, sets the focus to the last focused
1678 Sets focus to the last focused floating container.
1680 Sets focus to the last focused tiling container.
1682 Toggles between floating/tiling containers.
1684 Followed by a direction or an output name, this will focus the
1685 corresponding output.
1687 For moving, use +move left+, +move right+, +move down+ and +move up+.
1690 -----------------------------------
1691 focus <left|right|down|up>
1692 focus <parent|child|floating|tiling|mode_toggle>
1693 focus output <<left|right|down|up>|output>
1694 move <left|right|down|up> [<px> px]
1695 move [absolute] position [[<px> px] [<px> px]|center]
1696 -----------------------------------
1698 Note that the amount of pixels you can specify for the +move+ command is only
1699 relevant for floating containers. The default amount is 10 pixels.
1702 ----------------------
1703 # Focus container on the left, bottom, top, right:
1704 bindsym $mod+j focus left
1705 bindsym $mod+k focus down
1706 bindsym $mod+l focus up
1707 bindsym $mod+semicolon focus right
1709 # Focus parent container
1710 bindsym $mod+u focus parent
1712 # Focus last floating/tiling container
1713 bindsym $mod+g focus mode_toggle
1715 # Focus the output right to the current one
1716 bindsym $mod+x focus output right
1718 # Focus the big output
1719 bindsym $mod+x focus output HDMI-2
1721 # Move container to the left, bottom, top, right:
1722 bindsym $mod+j move left
1723 bindsym $mod+k move down
1724 bindsym $mod+l move up
1725 bindsym $mod+semicolon move right
1727 # Move container, but make floating containers
1728 # move more than the default
1729 bindsym $mod+j move left 20 px
1731 # Move floating container to the center
1733 bindsym $mod+c move absolute position center
1734 ----------------------
1736 === Changing (named) workspaces/moving to workspaces
1738 To change to a specific workspace, use the +workspace+ command, followed by the
1739 number or name of the workspace. To move containers to specific workspaces, use
1740 +move container to workspace+.
1742 You can also switch to the next and previous workspace with the commands
1743 +workspace next+ and +workspace prev+, which is handy, for example, if you have
1744 workspace 1, 3, 4 and 9 and you want to cycle through them with a single key
1745 combination. To restrict those to the current output, use +workspace
1746 next_on_output+ and +workspace prev_on_output+. Similarly, you can use +move
1747 container to workspace next+, +move container to workspace prev+ to move a
1748 container to the next/previous workspace and +move container to workspace current+
1749 (the last one makes sense only when used with criteria).
1751 See <<move_to_outputs>> for how to move a container/workspace to a different
1754 Workspace names are parsed as
1755 https://developer.gnome.org/pango/stable/PangoMarkupFormat.html[Pango markup]
1759 To switch back to the previously focused workspace, use +workspace
1760 back_and_forth+; likewise, you can move containers to the previously focused
1761 workspace using +move container to workspace back_and_forth+.
1764 -----------------------------------
1765 workspace <next|prev|next_on_output|prev_on_output>
1766 workspace back_and_forth
1768 workspace number <name>
1770 move [window|container] [to] workspace <name>
1771 move [window|container] [to] workspace number <name>
1772 move [window|container] [to] workspace <prev|next|current>
1773 -----------------------------------
1776 -------------------------
1777 bindsym $mod+1 workspace 1
1778 bindsym $mod+2 workspace 2
1779 bindsym $mod+3 workspace 3:<span foreground="red">vim</span>
1782 bindsym $mod+Shift+1 move container to workspace 1
1783 bindsym $mod+Shift+2 move container to workspace 2
1786 # switch between the current and the previously focused one
1787 bindsym $mod+b workspace back_and_forth
1788 bindsym $mod+Shift+b move container to workspace back_and_forth
1790 # move the whole workspace to the next output
1791 bindsym $mod+x move workspace to output right
1793 # move firefox to current workspace
1794 bindsym $mod+F1 [class="Firefox"] move workspace current
1795 -------------------------
1797 ==== Named workspaces
1799 Workspaces are identified by their name. So, instead of using numbers in the
1800 workspace command, you can use an arbitrary name:
1803 -------------------------
1804 bindsym $mod+1 workspace mail
1806 -------------------------
1808 If you want the workspace to have a number *and* a name, just prefix the
1812 -------------------------
1813 bindsym $mod+1 workspace 1: mail
1814 bindsym $mod+2 workspace 2: www
1816 -------------------------
1818 Note that the workspace will really be named "1: mail". i3 treats workspace
1819 names beginning with a number in a slightly special way. Normally, named
1820 workspaces are ordered the way they appeared. When they start with a number, i3
1821 will order them numerically. Also, you will be able to use +workspace number 1+
1822 to switch to the workspace which begins with number 1, regardless of which name
1823 it has. This is useful in case you are changing the workspace’s name
1824 dynamically. To combine both commands you can use +workspace number 1: mail+ to
1825 specify a default name if there's currently no workspace starting with a "1".
1827 ==== Renaming workspaces
1829 You can rename workspaces. This might be useful to start with the default
1830 numbered workspaces, do your work, and rename the workspaces afterwards to
1831 reflect what’s actually on them. You can also omit the old name to rename
1832 the currently focused workspace. This is handy if you want to use the
1833 rename command with +i3-input+.
1836 ----------------------------------------------------
1837 rename workspace <old_name> to <new_name>
1838 rename workspace to <new_name>
1839 ----------------------------------------------------
1842 --------------------------------------------------------------------------
1843 i3-msg 'rename workspace 5 to 6'
1844 i3-msg 'rename workspace 1 to "1: www"'
1845 i3-msg 'rename workspace "1: www" to "10: www"'
1846 i3-msg 'rename workspace to "2: mail"
1847 bindsym $mod+r exec i3-input -F 'rename workspace to "%s"' -P 'New name: '
1848 --------------------------------------------------------------------------
1850 === Moving workspaces to a different screen
1852 See <<move_to_outputs>> for how to move a container/workspace to a different
1855 === Moving containers/workspaces to RandR outputs
1859 To move a container to another RandR output (addressed by names like +LVDS1+ or
1860 +VGA1+) or to a RandR output identified by a specific direction (like +left+,
1861 +right+, +up+ or +down+), there are two commands:
1864 --------------------------------------------------------
1865 move container to output <<left|right|down|up>|<output>>
1866 move workspace to output <<left|right|down|up>|<output>>
1867 --------------------------------------------------------
1870 --------------------------------------------------------
1871 # Move the current workspace to the next output
1872 # (effectively toggles when you only have two outputs)
1873 bindsym $mod+x move workspace to output right
1875 # Put this window on the presentation output.
1876 bindsym $mod+x move container to output VGA1
1877 --------------------------------------------------------
1879 === Moving containers/workspaces to marks
1881 To move a container to another container with a specific mark (see <<vim_like_marks>>),
1882 you can use the following command.
1884 The window will be moved right after the marked container in the tree, i.e., it ends up
1885 in the same position as if you had opened a new window when the marked container was
1886 focused. If the mark is on a split container, the window will appear as a new child
1887 after the currently focused child within that container.
1890 ------------------------------------
1891 move window|container to mark <mark>
1892 ------------------------------------
1895 --------------------------------------------------------
1896 for_window [instance="tabme"] move window to mark target
1897 --------------------------------------------------------
1901 === Resizing containers/windows
1903 If you want to resize containers/windows using your keyboard, you can use the
1907 ---------------------------------------------------------
1908 resize <grow|shrink> <direction> [<px> px [or <ppt> ppt]]
1909 ---------------------------------------------------------
1911 Direction can either be one of +up+, +down+, +left+ or +right+. Or you can be
1912 less specific and use +width+ or +height+, in which case i3 will take/give
1913 space from all the other containers. The optional pixel argument specifies by
1914 how many pixels a *floating container* should be grown or shrunk (the default
1915 is 10 pixels). The ppt argument means percentage points and specifies by how
1916 many percentage points a *tiling container* should be grown or shrunk (the
1917 default is 10 percentage points).
1919 I recommend using the resize command inside a so called +mode+:
1921 .Example: Configuration file, defining a mode for resizing
1922 ----------------------------------------------------------------------
1924 # These bindings trigger as soon as you enter the resize mode
1926 # Pressing left will shrink the window’s width.
1927 # Pressing right will grow the window’s width.
1928 # Pressing up will shrink the window’s height.
1929 # Pressing down will grow the window’s height.
1930 bindsym j resize shrink width 10 px or 10 ppt
1931 bindsym k resize grow height 10 px or 10 ppt
1932 bindsym l resize shrink height 10 px or 10 ppt
1933 bindsym semicolon resize grow width 10 px or 10 ppt
1935 # same bindings, but for the arrow keys
1936 bindsym Left resize shrink width 10 px or 10 ppt
1937 bindsym Down resize grow height 10 px or 10 ppt
1938 bindsym Up resize shrink height 10 px or 10 ppt
1939 bindsym Right resize grow width 10 px or 10 ppt
1941 # back to normal: Enter or Escape
1942 bindsym Return mode "default"
1943 bindsym Escape mode "default"
1947 bindsym $mod+r mode "resize"
1948 ----------------------------------------------------------------------
1950 === Jumping to specific windows
1952 Often when in a multi-monitor environment, you want to quickly jump to a
1953 specific window. For example, while working on workspace 3 you may want to
1954 jump to your mail client to email your boss that you’ve achieved some
1955 important goal. Instead of figuring out how to navigate to your mail client,
1956 it would be more convenient to have a shortcut. You can use the +focus+ command
1957 with criteria for that.
1960 ----------------------------------------------------
1961 [class="class"] focus
1962 [title="title"] focus
1963 ----------------------------------------------------
1966 ------------------------------------------------
1967 # Get me to the next open VIM instance
1968 bindsym $mod+a [class="urxvt" title="VIM"] focus
1969 ------------------------------------------------
1971 === VIM-like marks (mark/goto)
1975 This feature is like the jump feature: It allows you to directly jump to a
1976 specific window (this means switching to the appropriate workspace and setting
1977 focus to the windows). However, you can directly mark a specific window with
1978 an arbitrary label and use it afterwards. You can unmark the label in the same
1979 way, using the unmark command. If you don't specify a label, unmark removes all
1980 marks. You do not need to ensure that your windows have unique classes or
1981 titles, and you do not need to change your configuration file.
1983 As the command needs to include the label with which you want to mark the
1984 window, you cannot simply bind it to a key. +i3-input+ is a tool created
1985 for this purpose: It lets you input a command and sends the command to i3. It
1986 can also prefix this command and display a custom prompt for the input dialog.
1988 The additional +--toggle+ option will remove the mark if the window already has
1989 this mark, add it if the window has none or replace the current mark if it has
1992 Refer to +show_marks+ if you don't want marks to be shown in the window decoration.
1995 ------------------------------
1996 mark [--toggle] identifier
1997 [con_mark="identifier"] focus
1999 ------------------------------
2001 *Example (in a terminal)*:
2002 ------------------------------
2004 $ i3-msg '[con_mark="irssi"] focus'
2005 $ i3-msg unmark irssi
2006 ------------------------------
2008 ///////////////////////////////////////////////////////////////////
2009 TODO: make i3-input replace %s
2011 ---------------------------------------
2012 # Read 1 character and mark the current window with this character
2013 bindsym $mod+m exec i3-input -p 'mark ' -l 1 -P 'Mark: '
2015 # Read 1 character and go to the window with the character
2016 bindsym $mod+g exec i3-input -p 'goto ' -l 1 -P 'Goto: '
2017 ---------------------------------------
2019 Alternatively, if you do not want to mess with +i3-input+, you could create
2020 seperate bindings for a specific set of labels and then only use those labels.
2021 ///////////////////////////////////////////////////////////////////
2023 === Changing border style
2025 To change the border of the current client, you can use +border normal+ to use the normal
2026 border (including window title), +border 1pixel+ to use a 1-pixel border (no window title)
2027 and +border none+ to make the client borderless.
2029 There is also +border toggle+ which will toggle the different border styles.
2032 ----------------------------
2033 bindsym $mod+t border normal
2034 bindsym $mod+y border 1pixel
2035 bindsym $mod+u border none
2036 ----------------------------
2040 ///////////////////////////////////////////////////////////////////////////////
2041 TODO: not yet implemented
2042 === Changing the stack-limit of a container
2044 If you have a single container with a lot of windows inside it (say, more than
2045 10), the default layout of a stacking container can get a little unhandy.
2046 Depending on your screen’s size, you might end up with only half of the title
2047 lines being actually used, wasting a lot of screen space.
2049 Using the +stack-limit+ command, you can limit the number of rows or columns
2050 in a stacking container. i3 will create columns or rows (depending on what
2051 you limited) automatically as needed.
2054 --------------------------------
2055 stack-limit <cols|rows> <value>
2056 --------------------------------
2060 # I always want to have two window titles in one line
2063 # Not more than 5 rows in this stacking container
2067 image:stacklimit.png[Container limited to two columns]
2068 ///////////////////////////////////////////////////////////////////////////////
2072 === Enabling shared memory logging
2074 As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared
2075 memory buffer, which you can dump using +i3-dump-log+. The +shmlog+ command
2076 allows you to enable or disable the shared memory logging at runtime.
2078 Note that when using +shmlog <size_in_bytes>+, the current log will be
2079 discarded and a new one will be started.
2082 ------------------------------
2083 shmlog <size_in_bytes>
2084 shmlog <on|off|toggle>
2085 ------------------------------
2089 # Enable/disable logging
2090 bindsym $mod+x shmlog toggle
2092 # or, from a terminal:
2093 # increase the shared memory log buffer to 50 MiB
2094 i3-msg shmlog $((50*1024*1024))
2097 === Enabling debug logging
2099 The +debuglog+ command allows you to enable or disable debug logging at
2100 runtime. Debug logging is much more verbose than non-debug logging. This
2101 command does not activate shared memory logging (shmlog), and as such is most
2102 likely useful in combination with the above-described <<shmlog>> command.
2105 ------------------------
2106 debuglog <on|off|toggle>
2107 ------------------------
2110 ------------------------
2111 # Enable/disable logging
2112 bindsym $mod+x debuglog toggle
2113 ------------------------
2115 === Reloading/Restarting/Exiting
2117 You can make i3 reload its configuration file with +reload+. You can also
2118 restart i3 inplace with the +restart+ command to get it out of some weird state
2119 (if that should ever happen) or to perform an upgrade without having to restart
2120 your X session. To exit i3 properly, you can use the +exit+ command,
2121 however you don’t need to (simply killing your X session is fine as well).
2124 ----------------------------
2125 bindsym $mod+Shift+r restart
2126 bindsym $mod+Shift+w reload
2127 bindsym $mod+Shift+e exit
2128 ----------------------------
2132 There are two commands to use any existing window as scratchpad window. +move
2133 scratchpad+ will move a window to the scratchpad workspace. This will make it
2134 invisible until you show it again. There is no way to open that workspace.
2135 Instead, when using +scratchpad show+, the window will be shown again, as a
2136 floating window, centered on your current workspace (using +scratchpad show+ on
2137 a visible scratchpad window will make it hidden again, so you can have a
2138 keybinding to toggle). Note that this is just a normal floating window, so if
2139 you want to "remove it from scratchpad", you can simple make it tiling again
2140 (+floating toggle+).
2142 As the name indicates, this is useful for having a window with your favorite
2143 editor always at hand. However, you can also use this for other permanently
2144 running applications which you don’t want to see all the time: Your music
2145 player, alsamixer, maybe even your mail client…?
2155 ------------------------------------------------
2156 # Make the currently focused window a scratchpad
2157 bindsym $mod+Shift+minus move scratchpad
2159 # Show the first scratchpad window
2160 bindsym $mod+minus scratchpad show
2162 # Show the sup-mail scratchpad window, if any.
2163 bindsym mod4+s [title="^Sup ::"] scratchpad show
2164 ------------------------------------------------
2168 There is a no operation command +nop+ which allows you to override default
2169 behavior. This can be useful for, e.g., disabling a focus change on clicks with
2170 the middle mouse button.
2172 The optional +comment+ argument is ignored, but will be printed to the log file
2173 for debugging purposes.
2181 ----------------------------------------------
2182 # Disable focus change for clicks on titlebars
2183 # with the middle mouse button
2185 ----------------------------------------------
2189 There are two options in the configuration of each i3bar instance that can be
2190 changed during runtime by invoking a command through i3. The commands +bar
2191 hidden_state+ and +bar mode+ allow setting the current hidden_state
2192 respectively mode option of each bar. It is also possible to toggle between
2193 hide state and show state as well as between dock mode and hide mode. Each
2194 i3bar instance can be controlled individually by specifying a bar_id, if none
2195 is given, the command is executed for all bar instances.
2199 bar hidden_state hide|show|toggle [<bar_id>]
2201 bar mode dock|hide|invisible|toggle [<bar_id>]
2205 ------------------------------------------------
2206 # Toggle between hide state and show state
2207 bindsym $mod+m bar hidden_state toggle
2209 # Toggle between dock mode and hide mode
2210 bindsym $mod+n bar mode toggle
2212 # Set the bar instance with id 'bar-1' to switch to hide mode
2213 bindsym $mod+b bar mode hide bar-1
2215 # Set the bar instance with id 'bar-1' to always stay hidden
2216 bindsym $mod+Shift+b bar mode invisible bar-1
2217 ------------------------------------------------
2221 == Multiple monitors
2223 As you can see in the goal list on the website, i3 was specifically developed
2224 with support for multiple monitors in mind. This section will explain how to
2225 handle multiple monitors.
2227 When you have only one monitor, things are simple. You usually start with
2228 workspace 1 on your monitor and open new ones as you need them.
2230 When you have more than one monitor, each monitor will get an initial
2231 workspace. The first monitor gets 1, the second gets 2 and a possible third
2232 would get 3. When you switch to a workspace on a different monitor, i3 will
2233 switch to that monitor and then switch to the workspace. This way, you don’t
2234 need shortcuts to switch to a specific monitor, and you don’t need to remember
2235 where you put which workspace. New workspaces will be opened on the currently
2236 active monitor. It is not possible to have a monitor without a workspace.
2238 The idea of making workspaces global is based on the observation that most
2239 users have a very limited set of workspaces on their additional monitors.
2240 They are often used for a specific task (browser, shell) or for monitoring
2241 several things (mail, IRC, syslog, …). Thus, using one workspace on one monitor
2242 and "the rest" on the other monitors often makes sense. However, as you can
2243 create an unlimited number of workspaces in i3 and tie them to specific
2244 screens, you can have the "traditional" approach of having X workspaces per
2245 screen by changing your configuration (using modes, for example).
2247 === Configuring your monitors
2249 To help you get going if you have never used multiple monitors before, here is
2250 a short overview of the xrandr options which will probably be of interest to
2251 you. It is always useful to get an overview of the current screen configuration.
2252 Just run "xrandr" and you will get an output like the following:
2253 -------------------------------------------------------------------------------
2255 Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
2256 VGA1 disconnected (normal left inverted right x axis y axis)
2257 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
2258 1280x800 60.0*+ 50.0
2259 1024x768 85.0 75.0 70.1 60.0
2261 800x600 85.1 72.2 75.0 60.3 56.2
2262 640x480 85.0 72.8 75.0 59.9
2266 --------------------------------------------------------------------------------------
2268 Several things are important here: You can see that +LVDS1+ is connected (of
2269 course, it is the internal flat panel) but +VGA1+ is not. If you have a monitor
2270 connected to one of the ports but xrandr still says "disconnected", you should
2271 check your cable, monitor or graphics driver.
2273 The maximum resolution you can see at the end of the first line is the maximum
2274 combined resolution of your monitors. By default, it is usually too low and has
2275 to be increased by editing +/etc/X11/xorg.conf+.
2277 So, say you connected VGA1 and want to use it as an additional screen:
2278 -------------------------------------------
2279 xrandr --output VGA1 --auto --left-of LVDS1
2280 -------------------------------------------
2281 This command makes xrandr try to find the native resolution of the device
2282 connected to +VGA1+ and configures it to the left of your internal flat panel.
2283 When running "xrandr" again, the output looks like this:
2284 -------------------------------------------------------------------------------
2286 Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 8192 x 8192
2287 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
2288 1280x1024 60.0*+ 75.0
2291 1024x768 75.1 70.1 60.0
2293 800x600 72.2 75.0 60.3 56.2
2294 640x480 72.8 75.0 66.7 60.0
2296 LVDS1 connected 1280x800+1280+0 (normal left inverted right x axis y axis) 261mm x 163mm
2297 1280x800 60.0*+ 50.0
2298 1024x768 85.0 75.0 70.1 60.0
2300 800x600 85.1 72.2 75.0 60.3 56.2
2301 640x480 85.0 72.8 75.0 59.9
2305 -------------------------------------------------------------------------------
2306 Please note that i3 uses exactly the same API as xrandr does, so it will see
2307 only what you can see in xrandr.
2309 See also <<presentations>> for more examples of multi-monitor setups.
2311 === Interesting configuration for multi-monitor environments
2313 There are several things to configure in i3 which may be interesting if you
2314 have more than one monitor:
2316 1. You can specify which workspace should be put on which screen. This
2317 allows you to have a different set of workspaces when starting than just
2318 1 for the first monitor, 2 for the second and so on. See
2319 <<workspace_screen>>.
2320 2. If you want some applications to generally open on the bigger screen
2321 (MPlayer, Firefox, …), you can assign them to a specific workspace, see
2322 <<assign_workspace>>.
2323 3. If you have many workspaces on many monitors, it might get hard to keep
2324 track of which window you put where. Thus, you can use vim-like marks to
2325 quickly switch between windows. See <<vim_like_marks>>.
2326 4. For information on how to move existing workspaces between monitors,
2327 see <<_moving_containers_workspaces_to_randr_outputs>>.
2329 == i3 and the rest of your software world
2331 === Displaying a status line
2333 A very common thing amongst users of exotic window managers is a status line at
2334 some corner of the screen. It is an often superior replacement to the widget
2335 approach you have in the task bar of a traditional desktop environment.
2337 If you don’t already have your favorite way of generating such a status line
2338 (self-written scripts, conky, …), then i3status is the recommended tool for
2339 this task. It was written in C with the goal of using as few syscalls as
2340 possible to reduce the time your CPU is woken up from sleep states. Because
2341 i3status only spits out text, you need to combine it with some other tool, like
2342 i3bar. See <<status_command>> for how to display i3status in i3bar.
2344 Regardless of which application you use to display the status line, you
2345 want to make sure that it registers as a dock window using EWMH hints. i3 will
2346 position the window either at the top or at the bottom of the screen, depending
2347 on which hint the application sets. With i3bar, you can configure its position,
2348 see <<i3bar_position>>.
2350 === Giving presentations (multi-monitor)
2352 When giving a presentation, you typically want the audience to see what you see
2353 on your screen and then go through a series of slides (if the presentation is
2354 simple). For more complex presentations, you might want to have some notes
2355 which only you can see on your screen, while the audience can only see the
2359 ==== Case 1: everybody gets the same output
2360 This is the simple case. You connect your computer to the video projector,
2361 turn on both (computer and video projector) and configure your X server to
2362 clone the internal flat panel of your computer to the video output:
2363 -----------------------------------------------------
2364 xrandr --output VGA1 --mode 1024x768 --same-as LVDS1
2365 -----------------------------------------------------
2366 i3 will then use the lowest common subset of screen resolutions, the rest of
2367 your screen will be left untouched (it will show the X background). So, in
2368 our example, this would be 1024x768 (my notebook has 1280x800).
2370 ==== Case 2: you can see more than your audience
2371 This case is a bit harder. First of all, you should configure the VGA output
2372 somewhere near your internal flat panel, say right of it:
2373 -----------------------------------------------------
2374 xrandr --output VGA1 --mode 1024x768 --right-of LVDS1
2375 -----------------------------------------------------
2376 Now, i3 will put a new workspace (depending on your settings) on the new screen
2377 and you are in multi-monitor mode (see <<multi_monitor>>).
2379 Because i3 is not a compositing window manager, there is no ability to
2380 display a window on two screens at the same time. Instead, your presentation
2381 software needs to do this job (that is, open a window on each screen).