3 Michael Stapelberg <michael+i3@stapelberg.de>
6 This document contains all the information you need to configure and use the i3
7 window manager. If it does not, please contact us on IRC (preferred) or post your
8 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 windows (Mod4)
30 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+. To split it horizontally, press
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
75 Only the focused window in the container is displayed. You get a list of
76 windows at the top of the container.
78 The same principle as +stacking+, but the list of windows at the top is only
79 a single line which is vertically split.
81 To switch modes, press +mod+e+ for default, +mod+h+ for stacking and
84 image:modes.png[Container modes]
86 === Toggling fullscreen mode for a window
88 To display a window in fullscreen mode or to go out of fullscreen mode again,
91 There is also a global fullscreen mode in i3 in which the client will span all
94 === Opening other applications
96 Aside from opening applications from a terminal, you can also use the handy
97 +dmenu+ which is opened by pressing +mod+d+ by default. Just type the name
98 (or a part of it) of the application which you want to open. The corresponding
99 application has to be in your +$PATH+ for this to work.
101 Additionally, if you have applications you open very frequently, you can
102 create a keybinding for starting the application directly. See the section
103 <<configuring>> for details.
107 If an application does not provide a mechanism for closing (most applications
108 provide a menu, the escape key or a shortcut like +Control+W+ to close), you
109 can press +mod+Shift+q+ to kill a window. For applications which support
110 the WM_DELETE protocol, this will correctly close the application (saving
111 any modifications or doing other cleanup). If the application doesn’t support
112 the WM_DELETE protocol your X server will kill the window and the behaviour
113 depends on the application.
117 Workspaces are an easy way to group a set of windows. By default, you are on
118 the first workspace, as the bar on the bottom left indicates. To switch to
119 another workspace, press +mod+num+ where +num+ is the number of the workspace
120 you want to use. If the workspace does not exist yet, it will be created.
122 A common paradigm is to put the web browser on one workspace, communication
123 applications (+mutt+, +irssi+, ...) on another one, and the ones with which you
124 work, on the third one. Of course, there is no need to follow this approach.
126 If you have multiple screens, a workspace will be created on each screen at
127 startup. If you open a new workspace, it will be bound to the screen you
128 created it on. When you switch to a workspace on another screen, i3 will set
129 focus to that screen.
131 === Moving windows to workspaces
133 To move a window to another workspace, simply press +mod+Shift+num+ where
134 +num+ is (like when switching workspaces) the number of the target workspace.
135 Similarly to switching workspaces, the target workspace will be created if
136 it does not yet exist.
140 The easiest way to resize a container is by using the mouse: Grab the border
141 and move it to the wanted size.
143 See <<resizingconfig>> for how to configure i3 to be able to resize
144 columns/rows with your keyboard.
146 === Restarting i3 inplace
148 To restart i3 inplace (and thus get into a clean state if there is a bug, or
149 to upgrade to a newer version of i3) you can use +mod+Shift+r+.
153 To cleanly exit i3 without killing your X server, you can use +mod+Shift+e+.
157 Floating mode is the opposite of tiling mode. The position and size of a window
158 are not managed by i3, but by you. Using this mode violates the tiling
159 paradigm but can be useful for some corner cases like "Save as" dialog
160 windows, or toolbar windows (GIMP or similar). Those windows usually set the
161 appropriate hint and are opened in floating mode by default.
163 You can enable floating mode for a window by pressing +mod+Shift+Space+. By
164 dragging the window’s titlebar with your mouse you can move the window
165 around. By grabbing the borders and moving them you can resize the window. You
166 can also do that by using the <<floating_modifier>>.
168 For resizing floating windows with your keyboard, see <<resizingconfig>>.
170 Floating windows are always on top of tiling windows.
174 i3 stores all information about the X11 outputs, workspaces and layout of the
175 windows on them in a tree. The root node is the X11 root window, followed by
176 the X11 outputs, then dock areas and a content container, then workspaces and
177 finally the windows themselve. In previous versions of i3 we had multiple lists
178 (of outputs, workspaces) and a table for each workspace. That approach turned
179 out to be complicated to use (snapping), understand and implement.
181 === The tree consists of Containers
183 The building blocks of our tree are so called +Containers+. A +Container+ can
184 host a window (meaning an X11 window, one that you can actually see and use,
185 like a browser). Alternatively, it could contain one or more +Containers+. A
186 simple example is the workspace: When you start i3 with a single monitor, a
187 single workspace and you open two terminal windows, you will end up with a tree
190 image::tree-layout2.png["layout2",float="right"]
191 image::tree-shot4.png["shot4",title="Two terminals on standard workspace"]
193 === Orientation and Split Containers
197 It is only natural to use so-called +Split Containers+ in order to build a
198 layout when using a tree as data structure. In i3, every +Container+ has an
199 orientation (horizontal, vertical or unspecified). So, in our example with the
200 workspace, the default orientation of the workspace +Container+ is horizontal
201 (most monitors are widescreen nowadays). If you change the orientation to
202 vertical (+mod+v+ in the default config) and *then* open two terminals, i3 will
203 configure your windows like this:
205 image::tree-shot2.png["shot2",title="Vertical Workspace Orientation"]
207 An interesting new feature of the tree branch is the ability to split anything:
208 Let’s assume you have two terminals on a workspace (with horizontal
209 orientation), focus is on the right terminal. Now you want to open another
210 terminal window below the current one. If you would just open a new terminal
211 window, it would show up to the right due to the horizontal workspace
212 orientation. Instead, press +mod+v+ to create a +Vertical Split Container+ (to
213 open a +Horizontal Split Container+, use +mod+h+). Now you can open a new
214 terminal and it will open below the current one:
216 image::tree-layout1.png["Layout",float="right"]
217 image::tree-shot1.png["shot",title="Vertical Split Container"]
221 You probably guessed it already: There is no limit on how deep your hierarchy
226 Let’s stay with our example from above. We have a terminal on the left and two
227 vertically split terminals on the right, focus is on the bottom right one. When
228 you open a new terminal, it will open below the current one.
230 So, how can you open a new terminal window to the *right* of the current one?
231 The solution is to use +focus parent+, which will focus the +Parent Container+ of
232 the current +Container+. In this case, you would focus the +Vertical Split
233 Container+ which is *inside* the horizontally oriented workspace. Thus, now new
234 windows will be opened to the right of the +Vertical Split Container+:
236 image::tree-shot3.png["shot3",title="Focus parent, then open new terminal"]
241 This is where the real fun begins ;-). Most things are very dependant on your
242 ideal working environment so we can’t make reasonable defaults for them.
244 While not using a programming language for the configuration, i3 stays
245 quite flexible in regards to the things you usually want your window manager
248 For example, you can configure bindings to jump to specific windows,
249 you can set specific applications to start on specific workspaces, you can
250 automatically start applications, you can change the colors of i3, and you
251 can bind your keys to do useful things.
253 To change the configuration of i3, copy +/etc/i3/config+ to +\~/.i3/config+
254 (or +~/.config/i3/config+ if you like the XDG directory scheme) and edit it
257 On first start (and on all following starts, unless you have a configuration
258 file), i3 will offer you to create a configuration file. You can tell the
259 wizard to use either Alt (Mod1) or Windows (Mod4) as modifier in the config
260 file. Also, the created config file will use the key symbols of your current
261 keyboard layout. To start the wizard, use the command +i3-config-wizard+.
262 Please note that you must not have +~/.i3/config+, otherwise the wizard will
267 It is possible and recommended to use comments in your configuration file to
268 properly document your setup for later reference. Comments are started with
269 a # and can only be used at the beginning of a line:
278 i3 uses X core fonts (not Xft) for rendering window titles. You can use
279 +xfontsel(1)+ to generate such a font description. To see special characters
280 (Unicode), you need to use a font which supports the ISO-10646 encoding.
282 If i3 cannot open the configured font, it will output an error in the logfile
283 and fall back to a working font.
286 ------------------------------
287 font <X core font description>
288 ------------------------------
291 --------------------------------------------------------------
292 font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
293 --------------------------------------------------------------
297 === Keyboard bindings
299 A keyboard binding makes i3 execute a command (see below) upon pressing a
300 specific key. i3 allows you to bind either on keycodes or on keysyms (you can
301 also mix your bindings, though i3 will not protect you from overlapping ones).
303 * A keysym (key symbol) is a description for a specific symbol, like "a"
304 or "b", but also more strange ones like "underscore" instead of "_". These
305 are the ones you use in Xmodmap to remap your keys. To get the current
306 mapping of your keys, use +xmodmap -pke+.
308 * Keycodes do not need to have a symbol assigned (handy for custom vendor
309 hotkeys on some notebooks) and they will not change their meaning as you
310 switch to a different keyboard layout (when using +xmodmap+).
312 My recommendation is: If you often switch keyboard layouts but you want to keep
313 your bindings in the same physical location on the keyboard, use keycodes.
314 If you don’t switch layouts, and want a clean and simple config file, use
318 ----------------------------------
319 bindsym [Modifiers+]keysym command
320 bindcode [Modifiers+]keycode command
321 ----------------------------------
324 --------------------------------
329 bindsym mod+Shift+r restart
331 # Notebook-specific hotkeys
332 bindcode 214 exec /home/michael/toggle_beamer.sh
333 --------------------------------
337 Mod1-Mod5, Shift, Control::
338 Standard modifiers, see +xmodmap(1)+
341 Unlike other window managers, i3 can use Mode_switch as a modifier. This allows
342 you to remap capslock (for example) to Mode_switch and use it for both: typing
343 umlauts or special characters 'and' having some comfortably reachable key
344 bindings. For example, when typing, capslock+1 or capslock+2 for switching
345 workspaces is totally convenient. Try it :-).
347 [[floating_modifier]]
349 === The floating modifier
351 To move floating windows with your mouse, you can either grab their titlebar
352 or configure the so called floating modifier which you can then press and
353 click anywhere in the window itself to move it. The most common setup is to
354 use the same key you use for managing windows (Mod1 for example). Then
355 you can press Mod1, click into a window using your left mouse button, and drag
356 it to the position you want.
358 When holding the floating modifier, you can resize a floating window by
359 pressing the right mouse button on it and moving around while holding it. If
360 you hold the shift button as well, the resize will be proportional.
363 --------------------------------
364 floating_modifier <Modifiers>
365 --------------------------------
368 --------------------------------
369 floating_modifier Mod1
370 --------------------------------
372 === Orientation for new workspaces
374 New workspaces get a reasonable default orientation: Wide-screen monitors
375 (anything wider than high) get horizontal orientation, rotated monitors
376 (anything higher than wide) get vertical orientation.
378 With the +default_orientation+ configuration directive, you can override that
382 ----------------------------------------------
383 default_orientation <horizontal|vertical|auto>
384 ----------------------------------------------
387 ----------------------------
388 default_orientation vertical
389 ----------------------------
391 === Layout mode for new containers
393 This option determines in which mode new containers on workspace level will
395 ///////////////////////////////
396 See also <<stack-limit>>.
397 //////////////////////////////
400 ---------------------------------------------
401 workspace_layout <default|stacking|tabbed>
402 ---------------------------------------------
403 /////////////////////////////////////////////
404 new_container stack-limit <cols|rows> <value>
405 /////////////////////////////////////////////
408 ---------------------
409 workspace_layout tabbed
410 ---------------------
412 === Border style for new windows
414 This option determines which border style new windows will have.
417 ---------------------------------------------
418 new_window <normal|1pixel|borderless>
419 ---------------------------------------------
422 ---------------------
424 ---------------------
426 === Arbitrary commands for specific windows (for_window)
428 With the +for_window+ command, you can let i3 execute any command when it
429 encounters a specific window. This can be used to set windows to floating or to
430 change their border style, for example.
433 -----------------------------
434 for_window [criteria] command
435 -----------------------------
438 ------------------------------------------------
439 # enable floating mode for all XTerm windows
440 for_window [class="XTerm"] floating enable
442 # Make all urxvts use a 1-pixel border:
443 for_window [class="urxvt"] border 1pixel
445 # A less useful, but rather funny example:
446 # makes the window floating as soon as I change
447 # directory to ~/work
448 for_window [title="x200: ~/work"] floating enable
449 ------------------------------------------------
453 As you learned in the section about keyboard bindings, you will have
454 to configure lots of bindings containing modifier keys. If you want to save
455 yourself some typing and be able to change the modifier you use later,
456 variables can be handy.
464 ------------------------
466 bindsym $m+Shift+r restart
467 ------------------------
469 Variables are directly replaced in the file when parsing. There is no fancy
470 handling and there are absolutely no plans to change this. If you need a more
471 dynamic configuration you should create a little script which generates a
472 configuration file and run it before starting i3 (for example in your
475 === Automatically putting clients on specific workspaces
479 Specific windows can be matched by window class and/or window title. It is
480 recommended that you match on window classes instead of window titles whenever
481 possible because some applications first create their window, and then worry
482 about setting the correct title. Firefox with Vimperator comes to mind. The
483 window starts up being named Firefox, and only when Vimperator is loaded does
484 the title change. As i3 will get the title as soon as the application maps the
485 window (mapping means actually displaying it on the screen), you’d need to have
486 to match on 'Firefox' in this case.
488 You can prefix or suffix workspaces with a `~` to specify that matching clients
489 should be put into floating mode. If you specify only a `~`, the client will
490 not be put onto any workspace, but will be set floating on the current one.
493 ------------------------------------------------------------
494 assign ["]window class[/window title]["] [→] [workspace]
495 ------------------------------------------------------------
498 ----------------------
503 assign "urxvt/VIM" → 3
505 ----------------------
507 Note that the arrow is not required, it just looks good :-). If you decide to
508 use it, it has to be a UTF-8 encoded arrow, not `->` or something like that.
510 === Automatically starting applications on i3 startup
512 By using the +exec+ keyword outside a keybinding, you can configure
513 which commands will be performed by i3 on initial startup. +exec+
514 commands will not run when restarting i3, if you need a command to run
515 also when restarting i3 you should use the +exec_always+
516 keyword. These commands will be run in order.
525 --------------------------------
526 exec i3status | i3bar -d
527 exec_always ~/my_script.sh
528 --------------------------------
532 === Automatically putting workspaces on specific screens
534 If you assign clients to workspaces, it might be handy to put the
535 workspaces on specific screens. Also, the assignment of workspaces to screens
536 will determine which workspace i3 uses for a new screen when adding screens
537 or when starting (e.g., by default it will use 1 for the first screen, 2 for
538 the second screen and so on).
541 ----------------------------------
542 workspace <number> output <output>
543 ----------------------------------
545 The 'output' is the name of the RandR output you attach your screen to. On a
546 laptop, you might have VGA1 and LVDS1 as output names. You can see the
547 available outputs by running +xrandr --current+.
550 ---------------------------
551 workspace 1 output LVDS1
552 workspace 5 output VGA1
553 ---------------------------
557 You can change all colors which i3 uses to draw the window decorations.
560 --------------------------------------------
561 colorclass border background text
562 --------------------------------------------
564 Where colorclass can be one of:
567 A client which currently has the focus.
568 client.focused_inactive::
569 A client which is the focused one of its container, but it does not have
570 the focus at the moment.
572 A client which is not the focused one of its container.
574 A client which has its urgency hint activated.
576 You can also specify the color to be used to paint the background of the client
577 windows. This color will be used to paint the window on top of which the client
581 -----------------------
582 client.background color
583 -----------------------
585 Only clients that do not cover the whole area of this window expose the color
586 used to paint it. If you use a color other than black for your terminals, you
587 most likely want to set the client background color to the same color as your
588 terminal program's background color to avoid black gaps between the rendered
589 area of the termianal and the i3 border.
591 Colors are in HTML hex format (#rrggbb), see the following example:
594 --------------------------------------
595 # class border backgr. text
596 client.focused #2F343A #900000 #FFFFFF
597 --------------------------------------
599 Note that for the window decorations, the color around the child window is the
600 background color, and the border color is only the two thin lines at the top of
603 === Interprocess communication
605 i3 uses unix sockets to provide an IPC interface. This allows third-party
606 programs to get information from i3, such as the current workspaces
607 (to display a workspace bar), and to control i3.
609 The IPC socket is enabled by default and will be created in
610 +/tmp/i3-%u/ipc-socket.%p+ where +%u+ is your UNIX username and +%p+ is the PID
613 You can override the default path through the environment-variable +I3SOCK+ or
614 by specifying the +ipc-socket+ directive.
617 ----------------------------
618 ipc-socket /tmp/i3-ipc.sock
619 ----------------------------
621 You can then use the +i3-msg+ application to perform any command listed in
624 === Focus follows mouse
626 If you have a setup where your mouse usually is in your way (like a touchpad
627 on your laptop which you do not want to disable completely), you might want
628 to disable 'focus follows mouse' and control focus only by using your keyboard.
629 The mouse will still be useful inside the currently active window (for example
630 to click on links in your browser window).
633 ----------------------------
634 focus_follows_mouse <yes|no>
635 ----------------------------
638 ----------------------
639 focus_follows_mouse no
640 ----------------------
642 === Popups during fullscreen mode
644 When you are in fullscreen mode, some applications still open popup windows
645 (take Xpdf for example). This is because these applications may not be aware
646 that they are in fullscreen mode (they do not check the corresponding hint).
647 There are two things which are possible to do in this situation:
649 1. Just ignore the popup (don’t map it). This won’t interrupt you while you are
650 in fullscreen. However, some apps might react badly to this (deadlock until
651 you go out of fullscreen).
652 2. Leave fullscreen mode. This is the default.
655 -------------------------------------------------
656 popup_during_fullscreen <ignore|leave_fullscreen>
657 -------------------------------------------------
660 ------------------------------
661 popup_during_fullscreen ignore
662 ------------------------------
666 === Splitting containers
668 The split command makes the current window a split container. Split containers
669 can contain multiple windows. Every split container has an orientation, it is
670 either split horizontally (a new window gets placed to the right of the current
671 one) or vertically (a new window gets placed below the current one).
673 If you apply this command to a split container with the same orientation,
674 nothing will happen. If you use a different orientation, the split container’s
675 orientation will be changed (if it does not have more than one window).
678 ---------------------------
679 split <vertical|horizontal>
680 ---------------------------
683 ------------------------------
684 bindsym mod+v split vertical
685 bindsym mod+h split horizontal
686 ------------------------------
688 === Manipulating layout
690 Use +layout default+, +layout stacking+ or +layout tabbed+ to change the
691 current container layout to default, stacking or tabbed layout, respectively.
693 To make the current window (!) fullscreen, use +fullscreen+, to make
694 it floating (or tiling again) use +floating enable+ respectively +floating disable+
695 (or +floating toggle+):
699 bindsym mod+s layout stacking
700 bindsym mod+l layout default
701 bindsym mod+w layout tabbed
704 bindsym mod+f fullscreen
706 # Toggle floating/tiling
707 bindsym mod+t floating toggle
710 === Focusing/Moving containers
712 To change the focus, use the focus command: +focus left+, +focus right+, +focus down+ and +focus up+.
714 There are a few special parameters you can use for the focus command:
717 Sets focus to the +Parent Container+ of the current +Container+.
719 The opposite of +focus parent+, sets the focus to the last focused
722 Sets focus to the last focused floating container.
724 Sets focus to the last focused tiling container.
726 Toggles between floating/tiling containers.
728 For moving, use +move left+, +move right+, +move down+ and +move up+.
731 ----------------------
732 # Focus clients on the left, bottom, top, right:
733 bindsym mod+j focus left
734 bindsym mod+k focus down
735 bindsym mod+l focus up
736 bindsym mod+semicolon focus right
738 # Focus parent container
739 bindsym mod+u focus parent
741 # Focus last floating/tiling container
742 bindsym mod+g focus mode_toggle
744 # Move client to the left, bottom, top, right:
745 bindsym mod+j move left
746 bindsym mod+k move down
747 bindsym mod+l move up
748 bindsym mod+semicolon move right
749 ----------------------
751 === Changing workspaces/moving containers to workspaces
753 To change to a specific workspace, use the +workspace+ command, followed by the
754 number or name of the workspace. To move containers to specific workspaces, use
757 You can also switch to the next and previous workspace with the commands
758 +workspace next+ and +workspace prev+, which is handy, for example, if you have
759 workspace 1, 3, 4 and 9 and you want to cycle through them with a single key
763 -------------------------
764 bindsym mod+1 workspace 1
765 bindsym mod+2 workspace 2
768 bindsym mod+Shift+1 move workspace 1
769 bindsym mod+Shift+2 move workspace 2
771 -------------------------
775 === Resizing containers/windows
777 If you want to resize containers/windows using your keyboard, you can use the
778 +resize+ command, I recommend using it inside a so called +mode+:
780 .Example: Configuration file, defining a mode for resizing
781 ----------------------------------------------------------------------
783 # These bindings trigger as soon as you enter the resize mode
785 # They resize the border in the direction you pressed, e.g.
786 # when pressing left, the window is resized so that it has
787 # more space on its left
789 bindsym j resize shrink left
790 bindsym Shift+j resize grow left
792 bindsym k resize grow down
793 bindsym Shift+k resize shrink down
795 bindsym l resize shrink up
796 bindsym Shift+l resize grow up
798 bindsym semicolon resize grow right
799 bindsym Shift+semicolon resize shrink right
801 bindcode 36 mode default
805 bindsym mod+r mode "resize"
806 ----------------------------------------------------------------------
808 === Jumping to specific windows
810 Often when in a multi-monitor environment, you want to quickly jump to a
811 specific window. For example, while working on workspace 3 you may want to
812 jump to your mail client to email your boss that you’ve achieved some
813 important goal. Instead of figuring out how to navigate to your mailclient,
814 it would be more convenient to have a shortcut. You can use the +focus+ command
815 with criteria for that.
818 ----------------------------------------------------
819 [class="class"] focus
820 [title="title"] focus
821 ----------------------------------------------------
824 ------------------------------------------------
825 # Get me to the next open VIM instance
826 bindsym mod+a [class="urxvt" title="VIM"] focus
827 ------------------------------------------------
829 === VIM-like marks (mark/goto)
833 This feature is like the jump feature: It allows you to directly jump to a
834 specific window (this means switching to the appropriate workspace and setting
835 focus to the windows). However, you can directly mark a specific window with
836 an arbitrary label and use it afterwards. You do not need to ensure that your
837 windows have unique classes or titles, and you do not need to change your
840 As the command needs to include the label with which you want to mark the
841 window, you cannot simply bind it to a key. +i3-input+ is a tool created
842 for this purpose: It lets you input a command and sends the command to i3. It
843 can also prefix this command and display a custom prompt for the input dialog.
846 ------------------------------
848 [con_mark="identifier"] focus
849 ------------------------------
851 *Example (in a terminal)*:
852 ------------------------------
854 $ i3-msg '[con_mark="irssi"] focus'
855 ------------------------------
857 ///////////////////////////////////////////////////////////////////
858 TODO: make i3-input replace %s
860 ---------------------------------------
861 # Read 1 character and mark the current window with this character
862 bindsym mod+m exec i3-input -p 'mark ' -l 1 -P 'Mark: '
864 # Read 1 character and go to the window with the character
865 bindsym mod+g exec i3-input -p 'goto ' -l 1 -P 'Goto: '
866 ---------------------------------------
868 Alternatively, if you do not want to mess with +i3-input+, you could create
869 seperate bindings for a specific set of labels and then only use those labels.
870 ///////////////////////////////////////////////////////////////////
872 === Changing border style
874 To change the border of the current client, you can use +border normal+ to use the normal
875 border (including window title), +border 1pixel+ to use a 1-pixel border (no window title)
876 and +border none+ to make the client borderless.
878 There is also +border toggle+ which will toggle the different border styles.
881 ----------------------------
882 bindsym mod+t border normal
883 bindsym mod+y border 1pixel
884 bindsym mod+u border none
885 ----------------------------
889 ///////////////////////////////////////////////////////////////////////////////
890 TODO: not yet implemented
891 === Changing the stack-limit of a container
893 If you have a single container with a lot of windows inside it (say, more than
894 10), the default layout of a stacking container can get a little unhandy.
895 Depending on your screen’s size, you might end up with only half of the title
896 lines being actually used, wasting a lot of screen space.
898 Using the +stack-limit+ command, you can limit the number of rows or columns
899 in a stacking container. i3 will create columns or rows (depending on what
900 you limited) automatically as needed.
903 --------------------------------
904 stack-limit <cols|rows> <value>
905 --------------------------------
909 # I always want to have two window titles in one line
912 # Not more than 5 rows in this stacking container
916 image:stacklimit.png[Container limited to two columns]
917 ///////////////////////////////////////////////////////////////////////////////
919 === Reloading/Restarting/Exiting
921 You can make i3 reload its configuration file with +reload+. You can also
922 restart i3 inplace with the +restart+ command to get it out of some weird state
923 (if that should ever happen) or to perform an upgrade without having to restart
924 your X session. To exit i3 properly, you can use the +exit+ command,
925 however you don’t need to (simply killing your X session is fine as well).
928 ----------------------------
929 bindsym mod+Shift+r restart
930 bindsym mod+Shift+w reload
931 bindsym mod+Shift+e exit
932 ----------------------------
938 As you can see in the goal list on the website, i3 was specifically developed
939 with support for multiple monitors in mind. This section will explain how to
940 handle multiple monitors.
942 When you have only one monitor, things are simple. You usually start with
943 workspace 1 on your monitor and open new ones as you need them.
945 When you have more than one monitor, each monitor will get an initial
946 workspace. The first monitor gets 1, the second gets 2 and a possible third
947 would get 3. When you switch to a workspace on a different monitor, i3 will
948 switch to that monitor and then switch to the workspace. This way, you don’t
949 need shortcuts to switch to a specific monitor, and you don’t need to remember
950 where you put which workspace. New workspaces will be opened on the currently
951 active monitor. It is not possible to have a monitor without a workspace.
953 The idea of making workspaces global is based on the observation that most
954 users have a very limited set of workspaces on their additional monitors.
955 They are often used for a specific task (browser, shell) or for monitoring
956 several things (mail, IRC, syslog, …). Thus, using one workspace on one monitor
957 and "the rest" on the other monitors often makes sense. However, as you can
958 create an unlimited number of workspaces in i3 and tie them to specific
959 screens, you can have the "traditional" approach of having X workspaces per
960 screen by changing your configuration (using modes, for example).
962 === Configuring your monitors
964 To help you get going if you have never used multiple monitors before, here is
965 a short overview of the xrandr options which will probably be of interest to
966 you. It is always useful to get an overview of the current screen configuration.
967 Just run "xrandr" and you will get an output like the following:
968 -------------------------------------------------------------------------------
970 Screen 0: minimum 320 x 200, current 1280 x 800, maximum 8192 x 8192
971 VGA1 disconnected (normal left inverted right x axis y axis)
972 LVDS1 connected 1280x800+0+0 (normal left inverted right x axis y axis) 261mm x 163mm
974 1024x768 85.0 75.0 70.1 60.0
976 800x600 85.1 72.2 75.0 60.3 56.2
977 640x480 85.0 72.8 75.0 59.9
981 --------------------------------------------------------------------------------------
983 Several things are important here: You can see that +LVDS1+ is connected (of
984 course, it is the internal flat panel) but +VGA1+ is not. If you have a monitor
985 connected to one of the ports but xrandr still says "disconnected", you should
986 check your cable, monitor or graphics driver.
988 The maximum resolution you can see at the end of the first line is the maximum
989 combined resolution of your monitors. By default, it is usually too low and has
990 to be increased by editing +/etc/X11/xorg.conf+.
992 So, say you connected VGA1 and want to use it as an additional screen:
993 -------------------------------------------
994 xrandr --output VGA1 --auto --left-of LVDS1
995 -------------------------------------------
996 This command makes xrandr try to find the native resolution of the device
997 connected to +VGA1+ and configures it to the left of your internal flat panel.
998 When running "xrandr" again, the output looks like this:
999 -------------------------------------------------------------------------------
1001 Screen 0: minimum 320 x 200, current 2560 x 1024, maximum 8192 x 8192
1002 VGA1 connected 1280x1024+0+0 (normal left inverted right x axis y axis) 338mm x 270mm
1003 1280x1024 60.0*+ 75.0
1006 1024x768 75.1 70.1 60.0
1008 800x600 72.2 75.0 60.3 56.2
1009 640x480 72.8 75.0 66.7 60.0
1011 LVDS1 connected 1280x800+1280+0 (normal left inverted right x axis y axis) 261mm x 163mm
1012 1280x800 60.0*+ 50.0
1013 1024x768 85.0 75.0 70.1 60.0
1015 800x600 85.1 72.2 75.0 60.3 56.2
1016 640x480 85.0 72.8 75.0 59.9
1020 -------------------------------------------------------------------------------
1021 Please note that i3 uses exactly the same API as xrandr does, so it will see
1022 only what you can see in xrandr.
1024 See also <<presentations>> for more examples of multi-monitor setups.
1026 === Interesting configuration for multi-monitor environments
1028 There are several things to configure in i3 which may be interesting if you
1029 have more than one monitor:
1031 1. You can specify which workspace should be put on which screen. This
1032 allows you to have a different set of workspaces when starting than just
1033 1 for the first monitor, 2 for the second and so on. See
1034 <<workspace_screen>>.
1035 2. If you want some applications to generally open on the bigger screen
1036 (MPlayer, Firefox, …), you can assign them to a specific workspace, see
1037 <<assign_workspace>>.
1038 3. If you have many workspaces on many monitors, it might get hard to keep
1039 track of which window you put where. Thus, you can use vim-like marks to
1040 quickly switch between windows. See <<vim_like_marks>>.
1042 == i3 and the rest of your software world
1044 === Displaying a status line
1046 A very common thing amongst users of exotic window managers is a status line at
1047 some corner of the screen. It is an often superior replacement to the widget
1048 approach you have in the task bar of a traditional desktop environment.
1050 If you don’t already have your favorite way of generating such a status line
1051 (self-written scripts, conky, …), then i3status is the recommended tool for
1052 this task. It was written in C with the goal of using as few syscalls as
1053 possible to reduce the time your CPU is woken up from sleep states. Because
1054 i3status only spits out text, you need to combine it with some other tool, like
1055 i3bar. Use a pipe to connect them: +i3status | i3bar -d+.
1057 Regardless of which application you use to display the status line, you
1058 want to make sure that it registers as a dock window using EWMH hints. i3 will
1059 position the window either at the top or at the bottom of the screen, depending
1060 on which hint the application sets. With i3bar, you can use +-d+ or +-dbottom+
1061 for positioning it at the bottom and +-dtop+ to position it at the top of the
1064 === Giving presentations (multi-monitor)
1066 When giving a presentation, you typically want the audience to see what you see
1067 on your screen and then go through a series of slides (if the presentation is
1068 simple). For more complex presentations, you might want to have some notes
1069 which only you can see on your screen, while the audience can only see the
1073 ==== Case 1: everybody gets the same output
1074 This is the simple case. You connect your computer to the video projector,
1075 turn on both (computer and video projector) and configure your X server to
1076 clone the internal flat panel of your computer to the video output:
1077 -----------------------------------------------------
1078 xrandr --output VGA1 --mode 1024x768 --same-as LVDS1
1079 -----------------------------------------------------
1080 i3 will then use the lowest common subset of screen resolutions, the rest of
1081 your screen will be left untouched (it will show the X background). So, in
1082 our example, this would be 1024x768 (my notebook has 1280x800).
1084 ==== Case 2: you can see more than your audience
1085 This case is a bit harder. First of all, you should configure the VGA output
1086 somewhere near your internal flat panel, say right of it:
1087 -----------------------------------------------------
1088 xrandr --output VGA1 --mode 1024x768 --right-of LVDS1
1089 -----------------------------------------------------
1090 Now, i3 will put a new workspace (depending on your settings) on the new screen
1091 and you are in multi-monitor mode (see <<multi_monitor>>).
1093 Because i3 is not a compositing window manager, there is no ability to
1094 display a window on two screens at the same time. Instead, your presentation
1095 software needs to do this job (that is, open a window on each screen).