# i3 config file (v4)+
X-Git-Url: https://git.sur5r.net/?a=blobdiff_plain;f=docs%2Fuserguide.html;h=d2e4c3a8fa1a701b642ece3bbb532686fa859c0c;hb=895bc822df60023d95df2ebc9e6286e3524f8897;hp=1985111c4a630acc73001c0b3add81765ba8a99c;hpb=f6ac7e334743f04fa3bbc7c1ad713762d4076c73;p=i3%2Fi3.github.io diff --git a/docs/userguide.html b/docs/userguide.html index 1985111..d2e4c3a 100644 --- a/docs/userguide.html +++ b/docs/userguide.html @@ -22,7 +22,7 @@ document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); a
@@ -41,8 +41,9 @@ document.addEventListener("DOMContentLoaded", function(){asciidoc.footnotes(); aThis document contains all the information you need to configure and use the i3 -window manager. If it does not, please check http://faq.i3wm.org/ first, then -contact us on IRC (preferred) or post your question(s) on the mailing list.
Throughout this guide, the keyword $mod will be used to refer to the -configured modifier. This is the Alt key (Mod1) by default, with the Windows -key (Mod4) being a popular alternative.
One very basic operation is opening a new terminal. By default, the keybinding -for this is $mod+Enter, that is Alt+Enter in the default configuration. By -pressing $mod+Enter, a new terminal will be opened. It will fill the whole -space available on your screen.
To move the focus between the two terminals, you can use the direction keys which you may know from the editor vi. However, in i3, your homerow is used for these keys (in vi, the keys are shifted to the left by one for -compatibility with most keyboard layouts). Therefore, $mod+J is left, $mod+K -is down, $mod+L is up and $mod+; is right. So, to switch between the -terminals, use $mod+K or $mod+L. Of course, you can also use the arrow keys.
At the moment, your workspace is split (it contains two terminals) in a specific direction (horizontal by default). Every window can be split horizontally or vertically again, just like the workspace. The terminology is @@ -170,7 +171,7 @@ create a keybinding for starting the application directly. See the section
If an application does not provide a mechanism for closing (most applications -provide a menu, the escape key or a shortcut like Control+W to close), you +provide a menu, the escape key or a shortcut like Control+w to close), you can press $mod+Shift+q to kill a window. For applications which support the WM_DELETE protocol, this will correctly close the application (saving any modifications or doing other cleanup). If the application doesnât support @@ -202,8 +203,10 @@ it does not yet exist.
The easiest way to resize a container is by using the mouse: Grab the border and move it to the wanted size.
See [resizingconfig] for how to configure i3 to be able to resize -columns/rows with your keyboard.
You can also use [binding_modes] to define a mode for resizing via the +keyboard. To see an example for this, look at the +default config provided +by i3.
For resizing floating windows with your keyboard, see [resizingconfig].
For resizing floating windows with your keyboard, see the resizing binding mode +provided by the i3 default config.
Floating windows are always on top of tiling windows.
It is only natural to use so-called Split Containers in order to build a +
It is only natural to use so-called Split Containers in order to build a layout when using a tree as data structure. In i3, every Container has an orientation (horizontal, vertical or unspecified) and the orientation depends on the layout the container is in (vertical for splitv and stacking, horizontal @@ -307,7 +311,7 @@ of splits can be.
So, how can you open a new terminal window to the right of the current one? -The solution is to use focus parent, which will focus the Parent Container of +The solution is to use focus parent ($mod+a by default), which will focus the Parent Container of the current Container. In this case, you would focus the Vertical Split Container which is inside the horizontally oriented workspace. Thus, now new windows will be opened to the right of the Vertical Split Container:
On first start (and on all following starts, unless you have a configuration file), i3 will offer you to create a configuration file. You can tell the -wizard to use either Alt (Mod1) or Windows (Mod4) as modifier in the config +wizard to use either Alt (Mod1) or Windows (Mod4) as modifier in the config file. Also, the created config file will use the key symbols of your current keyboard layout. To start the wizard, use the command i3-config-wizard. Please note that you must not have ~/.i3/config, otherwise the wizard will exit.
Since i3 4.0, a new configuration format is used. i3 will try to automatically +detect the format version of a config file based on a few different keywords, +but if you want to make sure that your config is read with the new format, +include the following line in your config file:
# i3 config file (v4)+
It is possible and recommended to use comments in your configuration file to @@ -486,7 +498,7 @@ can configure mouse bindings in a similar way to key bindings.
Syntax:
bindsym [--release] [--border] [--whole-window] [<Modifiers>+]button<n> command+
bindsym [--release] [--border] [--whole-window] [--exclude-titlebar] [<Modifiers>+]button<n> command
By default, the binding will only run when you click on the titlebar of the window. If the --release flag is given, it will run when the mouse button @@ -494,6 +506,8 @@ is released.
If the --whole-window flag is given, the binding will also run when any part of the window is clicked, with the exception of the border. To have a bind run when the border is clicked, specify the --border flag.
If the --exclude-titlebar flag is given, the titlebar will not be considered +for the keybinding.
Examples:
You can have multiple sets of bindings by using different binding modes. When +you switch to another binding mode, all bindings from the current mode are +released and only the bindings defined in the new mode are valid for as long as +you stay in that binding mode. The only predefined binding mode is default, +which is the mode i3 starts out with and to which all bindings not defined in a +specific binding mode belong.
Working with binding modes consists of two parts: defining a binding mode and +switching to it. For these purposes, there are one config directive and one +command, both of which are called mode. The directive is used to define the +bindings belonging to a certain binding mode, while the command will switch to +the specified mode.
It is recommended to use binding modes in combination with [variables] in +order to make maintenance easier. Below is an example of how to use a binding +mode.
Note that it is advisable to define bindings for switching back to the default +mode.
Note that it is possible to use [pango_markup] for binding modes, but you +need to enable it explicitly by passing the --pango_markup flag to the mode +definition.
Syntax:
# config directive +mode [--pango_markup] <name> + +# command +mode <name>+
Example:
# Press $mod+o followed by either f, t, Escape or Return to launch firefox, +# thunderbird or return to the default mode, respectively. +set $mode_launcher Launch: [f]irefox [t]hunderbird +bindsym $mod+o mode "$mode_launcher" + +mode "$mode_launcher" { + bindsym f exec firefox + bindsym t exec thunderbird + + bindsym Escape mode "default" + bindsym Return mode "default" +}+
To move floating windows with your mouse, you can either grab their titlebar or configure the so called floating modifier which you can then press and click anywhere in the window itself to move it. The most common setup is to @@ -536,7 +597,7 @@ ratio will be preserved).
The maximum and minimum dimensions of floating windows can be specified. If either dimension of floating_maximum_size is specified as -1, that dimension will be unconstrained with respect to its maximum value. If either dimension of @@ -557,7 +618,7 @@ floating_maximum_size -1 x -1
New workspaces get a reasonable default orientation: Wide-screen monitors (anything wider than high) get horizontal orientation, rotated monitors (anything higher than wide) get vertical orientation.
This option determines in which mode new containers on workspace level will start.
Syntax:
This option determines which border style new windows will have. The default is normal. Note that new_float applies only to windows which are starting out as floating windows, e.g., dialog windows, but not windows that are floated later on.
You can hide vertical borders adjacent to the screen edges using +
You can hide container borders adjacent to the screen edges using hide_edge_borders. This is useful if you are using scrollbars, or do not want -to waste even two pixels in displayspace. Default is none.
Syntax:
hide_edge_borders none|vertical|horizontal|both+
hide_edge_borders none|vertical|horizontal|both|smart
Example:
With the for_window command, you can let i3 execute any command when it +
With the for_window command, you can let i3 execute any command when it encounters a specific window. This can be used to set windows to floating or to change their border style, for example.
Syntax:
The valid criteria are the same as those for commands, see [command_criteria].
When a new window appears, it will be focused. The no_focus directive allows preventing -this from happening and can be used in combination with [command_criteria].
When a new window appears, it will be focused. The no_focus directive allows preventing +this from happening and must be used in combination with [command_criteria].
Note that this does not apply to all cases, e.g., when feeding data into a running application causing it to request being focused. To configure the behavior in such cases, refer to [focus_on_window_activation].
no_focus will also be ignored for the first window on a workspace as there shouldn’t be +a reason to not focus the window in this case. This allows for better usability in +combination with workspace_layout.
Syntax:
As you learned in the section about keyboard bindings, you will have to configure lots of bindings containing modifier keys. If you want to save yourself some typing and be able to change the modifier you use later, @@ -702,10 +768,39 @@ containing another variable. There is no fancy handling and there are absolutely no plans to change this. If you need a more dynamic configuration you should create a little script which generates a configuration file and run it before starting i3 (for example in your ~/.xsession file).
Also see [xresources] to learn how to create variables based on resources +loaded from the X resource database.
[variables] can also be created using a value configured in the X resource +database. This is useful, for example, to avoid configuring color values within +the i3 configuration. Instead, the values can be configured, once, in the X +resource database to achieve an easily maintainable, consistent color theme +across many X applications.
Defining a resource will load this resource from the resource database and +assign its value to the specified variable. A fallback must be specified in +case the resource cannot be loaded from the database.
Syntax:
set_from_resource $<name> <resource_name> <fallback>+
Example:
# The ~/.Xresources should contain a line such as +# *color0: #121212 +# and must be loaded properly, e.g., by using +# xrdb ~/.Xresources +# This value is picked up on by other applications (e.g., the URxvt terminal +# emulator) and can be used in i3 like this: +set_from_resource $black i3wm.color0 #000000+
To automatically make a specific window show up on a specific workspace, you +
To automatically make a specific window show up on a specific workspace, you can use an assignment. You can match windows by using any criteria, see [command_criteria]. It is recommended that you match on window classes (and instances, when appropriate) instead of window titles whenever possible @@ -753,7 +848,7 @@ window, you will see the following output:
The first part of the WM_CLASS is the instance ("irssi" in this example), the second part is the class ("URxvt" in this example).
Should you have any problems with assignments, make sure to check the i3 -logfile first (see http://i3wm.org/docs/debugging.html). It includes more +logfile first (see https://i3wm.org/docs/debugging.html). It includes more details about the matching process and the windowâs actual class, instance and title when starting up.
Note that if you want to start an application just once on a specific @@ -773,7 +868,7 @@ exec --no-startup-id i3-msg 'workspace 3; exec iceweasel; workspace 1'
By using the exec keyword outside a keybinding, you can configure which commands will be performed by i3 on initial startup. exec commands will not run when restarting i3, if you need a command to run @@ -781,7 +876,7 @@ also when restarting i3 you should use the exec_always keyword. These commands will be run in order.
See [command_chaining] for details on the special meaning of ; (semicolon) and , (comma): they chain commands together in i3, so you need to use quoted -strings if they appear in your command.
Syntax:
The flag --no-startup-id is explained in [exec].
If you assign clients to workspaces, it might be handy to put the workspaces on specific screens. Also, the assignment of workspaces to screens will determine which workspace i3 uses for a new screen when adding screens @@ -814,6 +909,16 @@ the second screen and so on).
The output is the name of the RandR output you attach your screen to. On a laptop, you might have VGA1 and LVDS1 as output names. You can see the available outputs by running xrandr --current.
If your X server supports RandR 1.5 or newer, i3 will use RandR monitor objects +instead of output objects. Run xrandr --listmonitors to see a list. Usually, +a monitor object contains exactly one output, and has the same name as the +output; but should that not be the case, you may specify the name of either the +monitor or the output in i3’s configuration. For example, the Dell UP2414Q uses +two scalers internally, so its output names might be âDP1â and âDP2â, but the +monitor name is âDell UP2414Qâ.
(Note that even if you specify the name of an output which doesn’t span the +entire monitor, i3 will still use the entire area of the containing monitor +rather than that of just the output’s.)
If you use named workspaces, they must be quoted:
Examples:
You can change all colors which i3 uses to draw the window decorations.
Syntax:
<colorclass> <border> <background> <text> <indicator>+
<colorclass> <border> <background> <text> <indicator> <child_border>
Where colorclass can be one of:
Examples (default colors):
# class border backgr. text indicator -client.focused #4c7899 #285577 #ffffff #2e9ef4 -client.focused_inactive #333333 #5f676a #ffffff #484e50 -client.unfocused #333333 #222222 #888888 #292d2e -client.urgent #2f343a #900000 #ffffff #900000 -client.placeholder #000000 #0c0c0c #ffffff #000000 +# class border backgr. text indicator child_border +client.focused #4c7899 #285577 #ffffff #2e9ef4 #285577 +client.focused_inactive #333333 #5f676a #ffffff #484e50 #5f676a +client.unfocused #333333 #222222 #888888 #292d2e #222222 +client.urgent #2f343a #900000 #ffffff #900000 #900000 +client.placeholder #000000 #0c0c0c #ffffff #000000 #0c0c0c client.background #ffffff
Note that for the window decorations, the color around the child window is the -background color, and the border color is only the two thin lines at the top of -the window.
The indicator color is used for indicating where a new window will be opened. For horizontal split containers, the right border will be painted in indicator color, for vertical split containers, the bottom border. This only applies to @@ -910,7 +1015,7 @@ single windows within a split container, which are otherwise indistinguishable from single windows outside of a split container.
i3 uses Unix sockets to provide an IPC interface. This allows third-party programs to get information from i3, such as the current workspaces (to display a workspace bar), and to control i3.
By default, window focus follows your mouse movements. However, if you have a -setup where your mouse usually is in your way (like a touchpad on your laptop -which you do not want to disable completely), you might want to disable focus -follows mouse and control focus only by using your keyboard. The mouse will -still be useful inside the currently active window (for example to click on -links in your browser window).
By default, window focus follows your mouse movements as the mouse crosses +window borders. However, if you have a setup where your mouse usually is in your +way (like a touchpad on your laptop which you do not want to disable +completely), you might want to disable focus follows mouse and control focus +only by using your keyboard. The mouse will still be useful inside the +currently active window (for example to click on links in your browser window).
Syntax:
By default, when switching focus to a window on a different output (e.g. focusing a window on workspace 3 on output VGA-1, coming from workspace 2 on LVDS-1), the mouse cursor is warped to the center of that window.
When you are in fullscreen mode, some applications still open popup windows (take Xpdf for example). This is because these applications may not be aware that they are in fullscreen mode (they do not check the corresponding hint). @@ -1007,7 +1112,7 @@ Leave fullscreen mode.
When being in a tabbed or stacked container, the first container will be focused when you use focus down on the last container — the focus wraps. If however there is another stacked/tabbed container in that direction, focus will @@ -1029,8 +1134,8 @@ will always wrap.
As explained in-depth in http://i3wm.org/docs/multi-monitor.html, some X11 +
As explained in-depth in https://i3wm.org/docs/multi-monitor.html, some X11 video drivers (especially the nVidia binary driver) only provide support for Xinerama instead of RandR. In such a situation, i3 must be told to use the inferior Xinerama API explicitly and therefore donât provide support for @@ -1052,7 +1157,7 @@ thatâs it).
This configuration directive enables automatic workspace back_and_forth (see [back_and_forth]) when switching to the workspace that is currently focused.
For instance: Assume you are on workspace "1: www" and switch to "2: IM" using @@ -1070,7 +1175,7 @@ came from now, you can just press $mod+2 again to switch back to "1: www".
If an application on another workspace sets an urgency hint, switching to this workspace may lead to immediate focus of the application, which also means the window decoration color would be immediately reset to client.focused. This @@ -1092,8 +1197,8 @@ value to 0 disables this feature.
If a window is activated, e.g., via google-chrome www.google.com, it may request +
If a window is activated, e.g., via google-chrome www.google.com, it may request to take focus. Since this may not preferable, different reactions can be configured.
Note that this may not affect windows that are being opened. To prevent new windows from being focused, see [no_focus].
If activated, marks on windows are drawn in their window decoration. However, -any mark starting with an underscore in its name (_) will not be drawn even if -this option is activated.
If activated, marks (see [vim_like_marks]) on windows are drawn in their window +decoration. However, any mark starting with an underscore in its name (_) will +not be drawn even if this option is activated.
The default for this option is yes.
Syntax:
Config files support line continuation, meaning when you end a line in a backslash character (\), the line-break will be ignored by the parser. This -feature can be used to create more readable configuration files.
Examples:
bindsym Mod1+f \ -fullscreen toggle+fullscreen toggle + +# this line is not continued \ +bindsym Mod1+F fullscreen toggle
mode dock|hide|invisible hidden_state hide|show -modifier <Modifier>+modifier <Modifier>|none
Example:
Available modifiers are Mod1-Mod5, Shift, Control (see xmodmap(1)).
Available modifiers are Mod1-Mod5, Shift, Control (see xmodmap(1)). You can +also use "none" if you don’t want any modifier to trigger this behavior.
Syntax:
output <output>+
output primary|<output>
Example:
Note that you might not have a primary output configured yet. To do so, run:
xrandr --output <output> --primary+
You can configure on which output (monitor) the icons should be displayed or you can turn off the functionality entirely.
You can use multiple tray_output directives in your config to specify a list +of outputs on which you want the tray to appear. The first available output in +that list as defined by the order of the directives will be used for the tray +output.
Syntax:
Specifies whether the current binding mode indicator should be shown or not. This is useful if you want to hide the workspace buttons but still be able -to see the current binding mode indicator. -For an example of a mode definition, see [resizingconfig].
The default is to show the mode indicator.
Syntax:
+ Background color of the bar on the currently focused monitor output. If + not used, the color will be taken from background. +
++ Text color to be used for the statusline on the currently focused + monitor output. If not used, the color will be taken from statusline. +
++ Text color to be used for the separator on the currently focused + monitor output. If not used, the color will be taken from separator. +
+The criteria which are currently implemented are:
Compares the window class (the second part of WM_CLASS). Use the - special value focused to match all windows having the same window + special value __focused__ to match all windows having the same window class as the currently focused window.
Compares the window instance (the first part of WM_CLASS). Use the - special value focused to match all windows having the same window + special value __focused__ to match all windows having the same window instance as the currently focused window.
Compares the window role (WM_WINDOW_ROLE). Use the special value - focused to match all windows having the same window role as the + __focused__ to match all windows having the same window role as the currently focused window.
Compare the window type (_NET_WM_WINDOW_TYPE). Possible values are normal, dialog, utility, toolbar, splash, menu, dropdown_menu, - popup_menu and tooltip. + popup_menu, tooltip and notification.
Compares the X11 window title (_NET_WM_NAME or WM_NAME as fallback). - Use the special value focused to match all windows having the + Use the special value __focused__ to match all windows having the same window title as the currently focused window.
Compares the workspace name of the workspace the window belongs to. Use - the special value focused to match all windows in the currently + the special value __focused__ to match all windows in the currently focused workspace.
- Compares the mark set for this container, see [vim_like_marks]. + Compares the marks set for this container, see [vim_like_marks]. A + match is made if any of the container’s marks matches the specified + mark.
Compares the i3-internal container ID, which you can get via the IPC - interface. Handy for scripting. + interface. Handy for scripting. Use the special value __focused__ + to match only the currently focused window. +
++ Only matches floating windows. This criterion requires no value. +
++ Only matches tiling windows. This criterion requires no value.
See [command_chaining] for details on the special meaning of ; (semicolon) and , (comma): they chain commands together in i3, so you need to use quoted -strings if they appear in your command.
Syntax:
If the command to be executed contains a ; (semicolon) and/or a , (comma), +the entire command must be quoted. For example, to have a keybinding for the +shell command notify-send Hello, i3, you would add an entry to your +configuration file like this:
Example:
# Execute a command with a comma in it +bindsym $mod+p exec "notify-send Hello, i3"+
If however a command with a comma and/or semicolon itself requires quotes, you +must escape the internal quotation marks with double backslashes, like this:
Example:
# Execute a command with a comma, semicolon and internal quotes +bindsym $mod+p exec "notify-send \\"Hello, i3; from $USER\\""+
If you apply this command to a split container with the same orientation, nothing will happen. If you use a different orientation, the split containerâs -orientation will be changed (if it does not have more than one window). Use -layout toggle split to change the layout of any split container from splitv -to splith or vice-versa.
Syntax:
split vertical|horizontal+
split vertical|horizontal|toggle
Example:
bindsym $mod+v split vertical -bindsym $mod+h split horizontal+bindsym $mod+h split horizontal +bindsym $mod+t split toggle
Use layout toggle split, layout stacking, layout tabbed, layout splitv or layout splith to change the current container layout to splith/splitv, stacking, tabbed layout, splitv or splith, respectively.
Specify up to four layouts after layout toggle to cycle through them. Every +time the command is executed, the layout specified after the currently active +one will be applied. If the currently active layout is not in the list, the +first layout in the list will be activated.
To make the current window (!) fullscreen, use fullscreen enable (or fullscreen enable global for the global mode), to leave either fullscreen mode use fullscreen disable, and to toggle between these two states use @@ -1911,7 +2113,8 @@ enable respectively floating disable (or floating toggle)
layout default|tabbed|stacking|splitv|splith -layout toggle [split|all]+layout toggle [split|all] +layout toggle [split|tabbed|stacking|splitv|splith] [split|tabbed|stacking|splitv|splith]â¦
Examples:
focus left|right|down|up focus parent|child|floating|tiling|mode_toggle -focus output left|right|up|down|<output>+focus output left|right|up|down|primary|<output>
Examples:
Note that you might not have a primary output configured yet. To do so, run:
xrandr --output <output> --primary
Two containers can be swapped (i.e., move to each other’s position) by using +the swap command. They will assume the position and geometry of the container +they are swapped with.
The first container to participate in the swapping can be selected through the +normal command criteria process with the focused window being the usual +fallback if no criteria are specified. The second container can be selected +using one of the following methods:
+The X11 window ID of a client window. +
++The i3 container ID of a container. +
++A container with the specified mark, see [vim_like_marks]. +
+Note that swapping does not work with all containers. Most notably, swapping +floating containers or containers that have a parent-child relationship to one +another does not work.
Syntax:
swap container with id|con_id|mark <arg>+
Examples:
# Swaps the focused container with the container marked »swapee«. +swap container with mark swapee + +# Swaps container marked »A« and »B« +[con_mark="^A$"] swap container with mark B+
If you want a window to stick to the glass, i.e., have it stay on screen even if you switch to another workspace, you can use the sticky command. For example, this can be useful for notepads, a media player or a video chat @@ -2088,10 +2362,12 @@ for_window [instance=notepad] sticky enable
To change to a specific workspace, use the workspace command, followed by the -number or name of the workspace. To move containers to specific workspaces, use -move container to workspace.
To move containers to specific workspaces, use move container to workspace.
You can also switch to the next and previous workspace with the commands workspace next and workspace prev, which is handy, for example, if you have workspace 1, 3, 4 and 9 and you want to cycle through them with a single key @@ -2100,6 +2376,9 @@ next_on_output and workspace prev_on_output. Similarly, you can us container to workspace next, move container to workspace prev to move a container to the next/previous workspace and move container to workspace current (the last one makes sense only when used with criteria).
workspace next cycles through either numbered or named workspaces. But when it +reaches the last numbered/named workspace, it looks for named workspaces after +exhausting numbered ones and looks for numbered ones after exhausting named ones.
See [move_to_outputs] for how to move a container/workspace to a different RandR output.
Workspace names are parsed as @@ -2113,11 +2392,11 @@ workspace using move container to workspace back_and_forth.
workspace next|prev|next_on_output|prev_on_output workspace back_and_forth -workspace <name> -workspace number <name> +workspace [--no-auto-back-and-forth] <name> +workspace [--no-auto-back-and-forth] number <name> -move [window|container] [to] workspace <name> -move [window|container] [to] workspace number <name> +move [--no-auto-back-and-forth] [window|container] [to] workspace <name> +move [--no-auto-back-and-forth] [window|container] [to] workspace number <name> move [window|container] [to] workspace prev|next|current
Examples:
Workspaces are identified by their name. So, instead of using numbers in the workspace command, you can use an arbitrary name:
Example:
You can rename workspaces. This might be useful to start with the default numbered workspaces, do your work, and rename the workspaces afterwards to reflect whatâs actually on them. You can also omit the old name to rename @@ -2192,23 +2471,37 @@ i3-msg 'rename workspace "1: www" to "10: www"' i3-msg 'rename workspace to "2: mail"' bindsym $mod+r exec i3-input -F 'rename workspace to "%s"' -P 'New name: '
If you want to rename workspaces on demand while keeping the navigation stable, +you can use a setup like this:
Example:
bindsym $mod+1 workspace number "1: www" +bindsym $mod+2 workspace number "2: mail" +...+
If a workspace does not exist, the command workspace number "1: mail" will +create workspace "1: mail".
If a workspace with number 1 does already exist, the command will switch to this +workspace and ignore the text part. So even when the workspace has been renamed +to "1: web", the above command will still switch to it.
See [move_to_outputs] for how to move a container/workspace to a different RandR output.
To move a container to another RandR output (addressed by names like LVDS1 or +
To move a container to another RandR output (addressed by names like LVDS1 or VGA1) or to a RandR output identified by a specific direction (like left, right, up or down), there are two commands:
Syntax:
move container to output left|right|down|up|<output> -move workspace to output left|right|down|up|<output>+
move container to output left|right|down|up|current|primary|<output> +move workspace to output left|right|down|up|current|primary|<output>
Examples:
To move a container to another container with a specific mark (see [vim_like_marks]), -you can use the following command.
The window will be moved right after the marked container in the tree, i.e., it ends up -in the same position as if you had opened a new window when the marked container was -focused. If the mark is on a split container, the window will appear as a new child -after the currently focused child within that container.
Syntax:
move window|container to mark <mark>+
Note that you might not have a primary output configured yet. To do so, run:+
xrandr --output <output> --primary
=== Moving containers/windows to marks + +To move a container to another container with a specific mark (see <<vim_like_marks>>), +you can use the following command. + +The window will be moved right after the marked container in the tree, i.e., it ends up +in the same position as if you had opened a new window when the marked container was +focused. If the mark is on a split container, the window will appear as a new child +after the currently focused child within that container. + +*Syntax*:
Example:
for_window [instance="tabme"] move window to mark target
If you want to resize containers/windows using your keyboard, you can use the resize command:
Syntax:
I recommend using the resize command inside a so called mode:
mode "resize" { - # These bindings trigger as soon as you enter the resize mode - - # Pressing left will shrink the windowâs width. - # Pressing right will grow the windowâs width. - # Pressing up will shrink the windowâs height. - # Pressing down will grow the windowâs height. - bindsym j resize shrink width 10 px or 10 ppt - bindsym k resize grow height 10 px or 10 ppt - bindsym l resize shrink height 10 px or 10 ppt - bindsym semicolon resize grow width 10 px or 10 ppt - - # same bindings, but for the arrow keys - bindsym Left resize shrink width 10 px or 10 ppt - bindsym Down resize grow height 10 px or 10 ppt - bindsym Up resize shrink height 10 px or 10 ppt - bindsym Right resize grow width 10 px or 10 ppt - - # back to normal: Enter or Escape - bindsym Return mode "default" - bindsym Escape mode "default" -} - -# Enter resize mode -bindsym $mod+r mode "resize"-
Example 2 - setting urxvt size to 640x480:
It is recommended to define bindings for resizing in a dedicated binding mode. +See [binding_modes] and the example in the i3 +default config for more +context.
Example:
for_window [class="urxvt"] resize set 640 480
Often when in a multi-monitor environment, you want to quickly jump to a specific window. For example, while working on workspace 3 you may want to jump to your mail client to email your boss that youâve achieved some @@ -2316,8 +2596,8 @@ bindsym $mod+a [class="urxvt" title="VIM"] focus
This feature is like the jump feature: It allows you to directly jump to a +
This feature is like the jump feature: It allows you to directly jump to a specific window (this means switching to the appropriate workspace and setting focus to the windows). However, you can directly mark a specific window with an arbitrary label and use it afterwards. You can unmark the label in the same @@ -2329,26 +2609,37 @@ window, you cannot simply bind it to a key. i3-input is a tool created for this purpose: It lets you input a command and sends the command to i3. It can also prefix this command and display a custom prompt for the input dialog.
The additional --toggle option will remove the mark if the window already has -this mark, add it if the window has none or replace the current mark if it has -another mark.
Refer to show_marks if you don’t want marks to be shown in the window decoration.
By default, a window can only have one mark. You can use the --add flag to +put more than one mark on a window.
Refer to [show_marks] if you don’t want marks to be shown in the window decoration.
Syntax:
mark [--toggle] <identifier> +mark [--add|--replace] [--toggle] <identifier> [con_mark="identifier"] focus unmark <identifier>
Example (in a terminal):
$ i3-msg mark irssi -$ i3-msg '[con_mark="irssi"] focus' -$ i3-msg unmark irssi+
# marks the focused container +mark irssi + +# focus the container with the mark "irssi" +'[con_mark="irssi"] focus' + +# remove the mark "irssi" from whichever container has it +unmark irssi + +# remove all marks on all firefox windows +[class="(?i)firefox"] unmark
By default, i3 will simply print the X11 window title. Using title_format, this can be customized by setting the format to the desired output. This directive supports @@ -2360,11 +2651,26 @@ and the following placeholders which will be replaced:
- The X11 window title (_NET_WM_NAME or WM_NAME as fallback). -%class: + For normal windows, this is the X11 window title (_NET_WM_NAME or WM_NAME + as fallback). When used on containers without a window (e.g., a split + container inside a tabbed/stacked layout), this will be the tree + representation of the container (e.g., "H[xterm xterm]"). +
+The X11 window class (second part of WM_CLASS). This corresponds to the class criterion, see [command_criteria]. -%instance: +
+The X11 window instance (first part of WM_CLASS). This corresponds to the instance criterion, see [command_criteria].
@@ -2391,11 +2697,14 @@ for_window [class="(?i)firefox"] title_format "<span foreground='red'>%titTo change the border of the current client, you can use border normal to use the normal border (including window title), border pixel 1 to use a 1-pixel border (no window title) and border none to make the client borderless.
There is also border toggle which will toggle the different border styles.
Note that "pixel" refers to logical pixel. On HiDPI displays, a logical pixel +may be represented by multiple physical pixels, so pixel 1 might not +necessarily translate into a single pixel row wide border.
Syntax:
As described in http://i3wm.org/docs/debugging.html, i3 can log to a shared +
As described in https://i3wm.org/docs/debugging.html, i3 can log to a shared memory buffer, which you can dump using i3-dump-log. The shmlog command allows you to enable or disable the shared memory logging at runtime.
Note that when using shmlog <size_in_bytes>, the current log will be @@ -2441,7 +2750,7 @@ i3-msg shmlog $((50*1024*1024))
The debuglog command allows you to enable or disable debug logging at runtime. Debug logging is much more verbose than non-debug logging. This command does not activate shared memory logging (shmlog), and as such is most @@ -2459,7 +2768,7 @@ bindsym $mod+x debuglog toggle
You can make i3 reload its configuration file with reload. You can also restart i3 inplace with the restart command to get it out of some weird state (if that should ever happen) or to perform an upgrade without having to restart @@ -2474,7 +2783,7 @@ bindsym $mod+Shift+e exit
There are two commands to use any existing window as scratchpad window. move scratchpad will move a window to the scratchpad workspace. This will make it invisible until you show it again. There is no way to open that workspace. @@ -2509,7 +2818,7 @@ bindsym mod4+s [title="^Sup ::"] scratchpad show
There is a no operation command nop which allows you to override default behavior. This can be useful for, e.g., disabling a focus change on clicks with the middle mouse button.
There are two options in the configuration of each i3bar instance that can be changed during runtime by invoking a command through i3. The commands bar hidden_state and bar mode allow setting the current hidden_state @@ -2563,7 +2872,7 @@ bindsym $mod+Shift+b bar mode invisible bar-1
As you can see in the goal list on the website, i3 was specifically developed with support for multiple monitors in mind. This section will explain how to @@ -2586,7 +2895,7 @@ create an unlimited number of workspaces in i3 and tie them to specific screens, you can have the "traditional" approach of having X workspaces per screen by changing your configuration (using modes, for example).
To help you get going if you have never used multiple monitors before, here is a short overview of the xrandr options which will probably be of interest to you. It is always useful to get an overview of the current screen configuration. @@ -2649,7 +2958,7 @@ only what you can see in xrandr.
See also [presentations] for more examples of multi-monitor setups.
There are several things to configure in i3 which may be interesting if you have more than one monitor:
For information on how to move existing workspaces between monitors, - see [_moving_containers_workspaces_to_randr_outputs]. + see [move_to_outputs].
A very common thing amongst users of exotic window managers is a status line at some corner of the screen. It is an often superior replacement to the widget approach you have in the task bar of a traditional desktop environment.
When giving a presentation, you typically want the audience to see what you see on your screen and then go through a series of slides (if the presentation is simple). For more complex presentations, you might want to have some notes which only you can see on your screen, while the audience can only see the slides.
This is the simple case. You connect your computer to the video projector, turn on both (computer and video projector) and configure your X server to clone the internal flat panel of your computer to the video output:
This case is a bit harder. First of all, you should configure the VGA output somewhere near your internal flat panel, say right of it: