More Video
NHL Network
Get NHL.TV
Remain confident despite trailing Capitals heading into Game 4 of Cup Final当前位置：
＞＞＞完型填空（15分） Jennie sat at her window as usual, looking ou..
完型填空（15分） Jennie sat at her window as usual, looking out upon the street, with a look of sadness on her face,“What a long day this is going to be!” Then she saw a little boy running down the street, swinging his schoolbag. Looking up to the window, he took off &&&1&&&hat and bowed with a bright, pleasant smile.“What a nice &&&2&&&,”said Jennie to herself, as the boy ran out of sight.“It seems like having the sunshine. I wish everybody who goes by would look up &&&3&&&smile.” George, the little boy, told his mother about that &&&4&&&girl when he got back home,“She looks so helpless. I wish I could do something for her.”“Why not give her some &&&5&&?”said his mother. George agreed. The next morning, as Jennie &&&6&&&&at he window again, she saw George with a handful of beautiful flowers carefully picking his way across the street. He stopped in front of her window, smiling pleasantly, and said,“Can I come in?”Jennie told him &&&7&&&to get into the house. Opening the door to Jennie’s gentle“Come in”, George said, “I’ve brought you some flowers.”“Are they for me?”said Jennie &&&8&&.“How kind you are,”she continued, as George put the flowers on her lap.“I’ve &&&9&&&received any flower since we moved to the town.”“Did you live in the countryside?”asked George, &&&10&&&&the old, small and empty room.“Yes,”said Jennie. Jennie used to have a happy family and live in a beautiful house in the countryside. However, she lost her right leg in an accident. She &&&11&&&walk like other people any longer. Later, her father died, and her mother was sick &&12&&&&so many years that their money was all gone. They sold the house, and move here to get work to do.George told his parents &&&13&&&. They decided to help her. More and more people in the &&14&&&gave Jennie friendly smiles when they passed by her house. She was greatly cheered up.A few months later, Jennie and her mother &&&15&&&a flower shop. People could always see Jennie sitting in the shop, having a lovely smile on her face.小题1:A．herB．hisC．yourD．my小题2:A．houseB．doorC．smileD．schoolbag小题3:A．andB．butC．asD．or小题4:A．richB．luckyC．badD．poor小题5:A．moneyB．flowersC．clothesD．food小题6:A．dancedB．criedC．satD．laughed小题7:A．howB．whoC．whenD．why小题8:A．angrilyB．easilyC．sadlyD．happily小题9:A．neverB．usuallyC．alwaysD．sometimes小题10:A．looking forB．looking aroundC．looking likeD．looking after小题11:A．shouldn’tB．needn’tC．couldn’tD．mustn’t小题12:A．forB．inC．atD．on小题13:A．somethingB．anythingC．everythingD．nothing小题14:A．countrysideB．townC．villageD．city小题15:A．reachedB．leftC．closedD．opened
题型：完形填空难度：中档来源：不详
小题1:B小题2:C小题3:A小题4:D小题5:B小题6:C小题7:A小题8:D小题9:A小题10:B小题11:C小题12:A小题13:C小题14:B小题15:D试题分析：这篇短文主要描述了一个小男孩设法帮助一个小女孩的故事，最后让这个失去一条腿的女孩重新树立起了生活的信心。从而也让人们懂得了微笑的力量是多么伟大。小题1:联系上文he took off 可知他摘下他的帽子，故选B，他的。小题2:联系上文and bowed with a bright, pleasant smile.及下文描述，可知珍妮是在感叹这个笑容，故选C，笑容，喜色。小题3:结合语境可知look up向上看，和smile微笑，是并列谓语，故选A和，并且。小题4:联系下文“She looks so helpless. I wish I could do something for her.”描述，可知他认为那是个可怜的女孩，故选D，可怜的。小题5:联系下文she saw George with a handful of beautiful flowers 描述，可知此处是提议给她一些花，故选B，花。小题6:联系上文描述可知珍妮又坐在窗前，故选C，坐。小题7:词义辨析。A.怎样；B.谁；C.什么时候；D.为什么。结合语境可知句意为：珍妮告诉他怎样进入房子。故选A。小题8:联系上下文，可知珍妮很高兴。故选D，高兴地。小题9:联系下文可知，自从搬到这儿来以后，她从来没有受到过任何鲜花。故选A，从来没有。小题10:短语辨析。A.寻找；B.向……四周看； C.看起来像……；D.照顾。结合语境可知乔治向四周看了看。故选B。小题11:联系上文可知她不能像其他人那样行走了，故选C，不能。小题12:在表示时间时，for后接一段时间；in表示在一个时间范围；at表示在具体时刻；on表示在具体某一天。联系下文so many years如此多年，可知选A。小题13:联系下文可知乔治把这一切告诉了他的父母，故选C，每件事，一切。小题14:联系上文“I’ve never received any flower since we moved to the town.”可知珍妮现在住在一个小镇上，故选B。小题15:联系上下文，可知珍妮和她的母亲开了一家花店，故选D，开始，营业。点评：这篇短文内容比较简单，理解不难。各小题与上下文联系比较紧密，答题中一定要注意联系上下文。答完后多读几遍，看看是否符合逻辑，适当修改。个别小题可以当做单独的词义辨析题来做，先区分词义，再结合语境选出最能使语句通顺的答案。
马上分享给同学
据魔方格专家权威分析，试题“完型填空（15分） Jennie sat at her window as usual, looking ou..”主要考查你对&&人物传记类阅读，故事类阅读&&等考点的理解。关于这些考点的“档案”如下：
现在没空？点击收藏，以后再看。
因为篇幅有限，只列出部分考点，详细请访问。
人物传记类阅读故事类阅读
人物传记类阅读：本类型选材主要是名人轶事。人物传记的叙述线索也常常以时间为序。内容一般不是一个人的生活流水账，而是选取主人公一些重要的人生阶段或生活片段来展开叙述。阅读时要把握主人公在此阶段发生的事对他本身或他人有什么重要的意义和影响。 故事类阅读：文章一般描述的是某一件具体事情的发生发展或结局，有人物、时间、地点和事件。命题往往从故事的情节、人物或事件的之间的关系、作者的态度及意图、故事前因和后果的推测等方面着手，考查学生对细节的辨认能力以及推理判断能力。阅读这类材料时，同学们一定要根据主要情节掌握文章主旨大意，同时抓住每一个细节，设身处地根据文章内容揣摩作者的态度和意图，根据情节展开想象，即使是碰到深层理解题也可迎刃而解。故事类阅读注意：初中生接触到的阅读材料大都是故事类。阅读故事类的材料，应该抓住人物线索、地点线索、时间线索和情节发展线索。特别注意的是，以上线索往往是并存的。因为情节的发展总是涉及到人物的变化、时间的推移、场景的变换等。而阅读材料后的阅读理解往往会围绕这些内容设计一些事实类的理解题。凡事实类的理解题都可以从阅读材料的表层文字中找到答案。在阅读故事类短文时，应理解文章的深层含义，也就是它的主题。在此需要注意的是，现在的阅读理解题在测试事实类的理解题的同时，往往有一道推理类理解测试题．
发现相似题
与“完型填空（15分） Jennie sat at her window as usual, looking ou..”考查相似的试题有：
273062126579273385147081311217129589i3: i3 User’s Guide
JavaScript must be enabled in your browser to display the table of contents.
This document contains all the information you need to configure and use the i3
window manager. If it does not, please check
first, then contact us on IRC (preferred) or post your question(s) on the
mailing list.
1. Default keybindings
For the " didn’t read" people, here is an overview of the default
keybindings (click to see the full-size image):
Keys to use with $mod (Alt):
Keys to use with Shift+$mod:
The red keys are the modifiers you need to press (by default), the blue keys
are your homerow.
Note that when starting i3 without a config file, i3-config-wizard will offer
you to create a config file in which the key positions (!) match what you see
in the image above, regardless of the keyboard layout you are using. If you
prefer to use a config file where the key letters match what you are seeing
above, just decline i3-config-wizard’s offer and base your config on
/etc/i3/config.
2. Using i3
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 that largely prevents conflicts with
application-defined shortcuts.
2.1. Opening terminals and moving around
One very basic operation is opening a new terminal. By default, the keybinding
for this is $mod+Enter, that is Alt+Enter (Mod1+Enter) in the default
configuration. By pressing $mod+Enter, a new terminal will be opened.
will fill the whole space available on your screen.
If you now open another terminal, i3 will place it next to the current one,
splitting the screen size in half. Depending on your monitor, i3 will put the
created window beside the existing window (on wide displays) or below the
existing window (rotated displays).
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
"window" for a container that actually contains an X11 window (like a terminal
or browser) and "split container" for containers that consist of one or more
TODO: picture of the tree
To split a window vertically, press $mod+v before you create the new window.
To split it horizontally, press $mod+h.
2.2. Changing the container layout
A split container can have one of the following layouts:
splith/splitv
Windows are sized so that every window gets an equal amount of space in the
container. splith distributes the windows horizontally (windows are right next
to each other), splitv distributes them vertically (windows are on top of each
Only the focused window in the container is displayed. You get a list of
windows at the top of the container.
The same principle as stacking, but the list of windows at the top is only
a single line which is vertically split.
To switch modes, press $mod+e for splith/splitv (it toggles), $mod+s for
stacking and $mod+w for tabbed.
2.3. Toggling fullscreen mode for a window
To display a window in fullscreen mode or to go out of fullscreen mode again,
press $mod+f.
There is also a global fullscreen mode in i3 in which the client will span all
available outputs (the command is fullscreen toggle global).
2.4. Opening other applications
Aside from opening applications from a terminal, you can also use the handy
dmenu which is opened by pressing $mod+d by default. Just type the name
(or a part of it) of the application which you want to open. The corresponding
application has to be in your $PATH for this to work.
Additionally, if you have applications you open very frequently, you can
create a keybinding for starting the application directly. See the section
for details.
2.5. Closing windows
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
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
the WM_DELETE protocol your X server will kill the window and the behaviour
depends on the application.
2.6. Using workspaces
Workspaces are an easy way to group a set of windows. By default, you are on
the first workspace, as the bar on the bottom left indicates. To switch to
another workspace, press $mod+num where num is the number of the workspace
you want to use. If the workspace does not exist yet, it will be created.
A common paradigm is to put the web browser on one workspace, communication
applications (mutt, irssi, …) on another one, and the ones with which you
work, on the third one. Of course, there is no need to follow this approach.
If you have multiple screens, a workspace will be created on each screen at
startup. If you open a new workspace, it will be bound to the screen you
created it on.
When you switch to a workspace on another screen, i3 will set
focus to that screen.
2.7. Moving windows to workspaces
To move a window to another workspace, simply press $mod+Shift+num where
num is (like when switching workspaces) the number of the target workspace.
Similarly to switching workspaces, the target workspace will be created if
it does not yet exist.
2.8. Resizing
The easiest way to resize a container is by using the mouse: Grab the border
and move it to the wanted size.
You can also use
to define a mode for resizing via the
keyboard. To see an example for this, look at the
2.9. Restarting i3 inplace
To restart i3 in place (and thus get into a clean state if there is a bug, or
to upgrade to a newer version of i3) you can use $mod+Shift+r.
2.10. Exiting i3
To cleanly exit i3 without killing your X server, you can use $mod+Shift+e.
By default, a dialog will ask you to confirm if you really want to quit.
2.11. Floating
Floating mode is the opposite of tiling mode. The position and size of
a window are not managed automatically by i3, but manually by
you. Using this mode violates the tiling paradigm but can be useful
for some corner cases like "Save as" dialog windows, or toolbar
windows (GIMP or similar). Those windows usually set the appropriate
hint and are opened in floating mode by default.
You can toggle floating mode for a window by pressing $mod+Shift+Space. By
dragging the window’s titlebar with your mouse you can move the window
around. By grabbing the borders and moving them you can resize the window. You
can also do that by using the . Another way to resize
floating windows using the mouse is to right-click on the titlebar and drag.
For resizing floating windows with your keyboard, see the resizing binding mode
provided by the i3 .
Floating windows are always on top of tiling windows.
i3 stores all information about the X11 outputs, workspaces and layout of the
windows on them in a tree. The root node is the X11 root window, followed by
the X11 outputs, then dock areas and a content container, then workspaces and
finally the windows themselves. In previous versions of i3 we had multiple lists
(of outputs, workspaces) and a table for each workspace. That approach turned
out to be complicated to use (snapping), understand and implement.
3.1. The tree consists of Containers
The building blocks of our tree are so-called Containers. A Container can
host a window (meaning an X11 window, one that you can actually see and use,
like a browser). Alternatively, it could contain one or more Containers. A
simple example is the workspace: When you start i3 with a single monitor, a
single workspace and you open two terminal windows, you will end up with a tree
like this:
Figure 1. Two terminals on standard workspace
3.2. Orientation and Split Containers
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
for splith and tabbed). So, in our example with the workspace, the default
layout of the workspace Container is splith (most monitors are widescreen
nowadays). If you change the layout to splitv ($mod+v in the default config)
and then open two terminals, i3 will configure your windows like this:
Figure 2. Vertical Workspace Orientation
An interesting new feature of i3 since version 4 is the ability to split anything:
Let’s assume you have two terminals on a workspace (with splith layout, that is
horizontal orientation), focus is on the right terminal. Now you want to open
another terminal window below the current one. If you would just open a new
terminal window, it would show up to the right due to the splith layout.
Instead, press $mod+v to split the container with the splitv layout (to
open a Horizontal Split Container, use $mod+h). Now you can open a new
terminal and it will open below the current one:
Figure 3. Vertical Split Container
You probably guessed it already: There is no limit on how deep your hierarchy
of splits can be.
3.3. Focus parent
Let’s stay with our example from above. We have a terminal on the left and two
vertically split terminals on the right, focus is on the bottom right one. When
you open a new terminal, it will open below the current one.
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 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:
Figure 4. Focus parent, then open new terminal
3.4. Implicit containers
In some cases, i3 needs to implicitly create a container to fulfill your
One example is the following scenario: You start i3 with a single monitor and a
single workspace on which you open three terminal windows. All these terminal
windows are directly attached to one node inside i3’s layout tree, the
workspace node. By default, the workspace node’s orientation is horizontal.
Now you move one of these terminals down ($mod+Shift+k by default). The
workspace node’s orientation will be changed to vertical. The terminal window
you moved down is directly attached to the workspace and appears on the bottom
of the screen. A new (horizontal) container was created to accommodate the
other two terminal windows. You will notice this when switching to tabbed mode
(for example). You would end up having one tab with a representation of the split
container (e.g., "H[urxvt firefox]") and the other one being the terminal window
you moved down.
4. Configuring i3
This is where -). Most things are very dependent on your
ideal working environment so we can’t make reasonable defaults for them.
While not using a programming language for the configuration, i3 stays
quite flexible in regards to the things you usually want your window manager
For example, you can configure bindings to jump to specific windows,
you can set specific applications to start on specific workspaces, you can
automatically start applications, you can change the colors of i3, and you
can bind your keys to do useful things.
To change the configuration of i3, copy /etc/i3/config to ~/.i3/config
(or ~/.config/i3/config if you like the XDG directory scheme) and edit it
with a text editor.
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
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
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
properly document your setup for later reference. Comments are started with
a # and can only be used at the beginning of a line:
# This is a comment
4.2. Fonts
i3 has support for both X core fonts and FreeType fonts (through Pango) to
render window titles.
To generate an X core font description, you can use xfontsel(1). To see
special characters (Unicode), you need to use a font which supports the
ISO-10646 encoding.
A FreeType font description is composed by a font family, a style, a weight,
a variant, a stretch and a size.
FreeType fonts support right-to-left rendering and contain often more
Unicode glyphs than X core fonts.
If i3 cannot open the configured font, it will output an error in the logfile
and fall back to a working font.
font &X core font description&
font pango:&family list& [&style options&] &size&
font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
font pango:DejaVu Sans Mono 10
font pango:DejaVu Sans Mono, Terminus Bold Semi-Condensed 11
font pango:Terminus 11px
4.3. Keyboard bindings
A keyboard binding makes i3 execute a command (see below) upon pressing a
specific key. i3 allows you to bind either on keycodes or on keysyms (you can
also mix your bindings, though i3 will not protect you from overlapping ones).
A keysym (key symbol) is a description for a specific symbol, like "a"
or "b", but also more strange ones like "underscore" instead of "_". These
are the ones you use in Xmodmap to remap your keys. To get the current
mapping of your keys, use xmodmap -pke. To interactively enter a key and
see what keysym it is configured to, use xev.
Keycodes do not need to have a symbol assigned (handy for custom vendor
hotkeys on some notebooks) and they will not change their meaning as you
switch to a different keyboard layout (when using xmodmap).
My recommendation is: If you often switch keyboard layouts but you want to keep
your bindings in the same physical location on the keyboard, use keycodes.
If you don’t switch layouts, and want a clean and simple config file, use
Some tools (such as import or xdotool) might be unable to run upon a
KeyPress event, because the keyboard/pointer is still grabbed. For these
situations, the --release flag can be used, which will execute the command
after the keys have been released.
bindsym [--release] [&Group&+][&Modifiers&+]&keysym& command
bindcode [--release] [&Group&+][&Modifiers&+]&keycode& command
# Fullscreen
bindsym $mod+f fullscreen toggle
bindsym $mod+Shift+r restart
# Notebook-specific hotkeys
bindcode 214 exec --no-startup-id /home/michael/toggle_beamer.sh
# Simulate ctrl+v upon pressing $mod+x
bindsym --release $mod+x exec --no-startup-id xdotool key --clearmodifiers ctrl+v
# Take a screenshot upon pressing $mod+x (select an area)
bindsym --release $mod+x exec --no-startup-id import /tmp/latest-screenshot.png
Available Modifiers:
Mod1-Mod5, Shift, Control
Standard modifiers, see xmodmap(1)
Group1, Group2, Group3, Group4
When using multiple keyboard layouts (e.g. with setxkbmap -layout us,ru), you
can specify in which XKB group (also called “layout”) a keybinding should be
active. By default, keybindings are translated in Group1 and are active in all
groups. If you want to override keybindings in one of your layouts, specify the
corresponding group. For backwards compatibility, the group “Mode_switch” is an
alias for Group2.
4.4. Mouse bindings
A mouse binding makes i3 execute a command upon pressing a specific mouse
button in the scope of the clicked container (see ). You
can configure mouse bindings in a similar way to key bindings.
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
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.
# The middle button over a titlebar kills the window
bindsym --release button2 kill
# The middle button and a modifer over any part of the window kills the window
bindsym --whole-window $mod+button2 kill
# The right button toggles floating
bindsym button3 floating toggle
bindsym $mod+button3 floating toggle
# The side buttons move the window around
bindsym button9 move left
bindsym button8 move right
4.5. Binding modes
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
order to make maintenance easier. Below is an example of how to use a binding
Note that it is advisable to define bindings for switching back to the default
Note that it is possible to use
for binding modes, but you
need to enable it explicitly by passing the --pango_markup flag to the mode
definition.
# config directive
mode [--pango_markup] &name&
mode &name&
# 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"
4.6. The floating modifier
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
use the same key you use for managing windows (Mod1 for example). Then
you can press Mod1, click into a window using your left mouse button, and drag
it to the position you want.
When holding the floating modifier, you can resize a floating window by
pressing the right mouse button on it and moving around while holding it. If
you hold the shift button as well, the resize will be proportional (the aspect
ratio will be preserved).
floating_modifier &Modifier&
floating_modifier Mod1
4.7. Constraining floating window size
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
floating_maximum_size is undefined, or specified as 0, i3 will use a default
value to constrain the maximum size. floating_minimum_size is treated in a
manner analogous to floating_maximum_size.
floating_minimum_size &width& x &height&
floating_maximum_size &width& x &height&
floating_minimum_size 75 x 50
floating_maximum_size -1 x -1
4.8. Orientation for new workspaces
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.
With the default_orientation configuration directive, you can override that
default_orientation horizontal|vertical|auto
default_orientation vertical
4.9. Layout mode for new containers
This option determines in which mode new containers on workspace level will
workspace_layout default|stacking|tabbed
workspace_layout tabbed
4.10. Default border style for new windows
This option determines which border style new windows will have. The default is
normal. Note that default_floating_border applies only to windows which are starting out as
floating windows, e.g., dialog windows, but not windows that are floated later on.
default_border normal|none|pixel
default_border normal|pixel &px&
default_floating_border normal|none|pixel
default_floating_border normal|pixel &px&
Please note that new_window and new_float have been deprecated in favor of the above options
and will be removed in a future release. We strongly recommend using the new options instead.
default_border pixel
The "normal" and "pixel" border styles support an optional border width in
# The same as default_border none
default_border pixel 0
# A 3 px border
default_border pixel 3
4.11. Hiding borders adjacent to the screen edges
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. The "smart" setting hides borders on
workspaces with only one window visible, but keeps them on workspaces with
multiple windows visible. Default is none.
hide_edge_borders none|vertical|horizontal|both|smart
hide_edge_borders vertical
4.12. Arbitrary commands for specific windows (for_window)
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.
for_window &criteria& &command&
# enable floating mode for all XTerm windows
for_window [class="XTerm"] floating enable
# Make all urxvts use a 1-pixel border:
for_window [class="urxvt"] border pixel 1
# A less useful, but rather funny example:
# makes the window floating as soon as I change
# directory to ~/work
for_window [title="x200: ~/work"] floating enable
The valid criteria are the same as those for commands, see .
4.13. Don’t focus window upon opening
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 .
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
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.
no_focus &criteria&
no_focus [window_role="pop-up"]
4.14. Variables
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,
variables can be handy.
set $&name& &value&
set $m Mod1
bindsym $m+Shift+r restart
Variables are directly replaced in the file when parsing. Variables expansion
is not recursive so it is not possible to define a variable with a value
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).
to learn how to create variables based on resources
loaded from the X resource database.
4.15. X resources
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.
set_from_resource $&name& &resource_name& &fallback&
# 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
4.16. Automatically putting clients on specific workspaces
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 . It is recommended that you match on window classes
(and instances, when appropriate) instead of window titles whenever possible
because some applications first create their window, and then worry about
setting the correct title. Firefox with Vimperator comes to mind. The window
starts up being named Firefox, and only when Vimperator is loaded does the
title change. As i3 will get the title as soon as the application maps the
window (mapping means actually displaying it on the screen), you’d need to have
to match on Firefox in this case.
You can also assign a window to show up on a specific output. You can use RandR
names such as VGA1 or names relative to the output with the currently focused
workspace such as left and down.
Assignments are processed by i3 in the order in which they appear in the config
file. The first one which matches the window wins and later assignments are not
considered.
assign &criteria& [→] [workspace] [number] &workspace&
assign &criteria& [→] output left|right|up|down|primary|&output&
# Assign URxvt terminals to workspace 2
assign [class="URxvt"] 2
# Same thing, but more precise (exact match instead of substring)
assign [class="^URxvt$"] 2
# Same thing, but with a beautiful arrow :)
assign [class="^URxvt$"] → 2
# Assignment to a named workspace
assign [class="^URxvt$"] → work
# Assign to the workspace with number 2, regardless of name
assign [class="^URxvt$"] → number 2
# You can also specify a number + name. If the workspace with number 2 exists, assign will skip the text part.
assign [class="^URxvt$"] → number "2: work"
# Start urxvt -name irssi
assign [class="^URxvt$" instance="^irssi$"] → 3
# Assign urxvt to the output right of the current one
assign [class="^URxvt$"] → output right
# Assign urxvt to the primary output
assign [class="^URxvt$"] → output primary
Note that you might not have a primary output configured yet. To do so, run:
xrandr --output &output& --primary
Also, the arrow is not required, it just looks good :-). If you decide to
use it, it has to be a UTF-8 encoded arrow, not -& or something like that.
To get the class and instance, you can use xprop. After clicking on the
window, you will see the following output:
WM_CLASS(STRING) = "irssi", "URxvt"
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 ). 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
workspace, but you don’t want to assign all instances of it permanently, you
can make use of i3’s startup-notification support (see ) in your config
file in the following way:
Start iceweasel on workspace 3 (once):
# Start iceweasel on workspace 3, then switch back to workspace 1
# (Being a command-line utility, i3-msg does not support startup notifications,
hence the exec --no-startup-id.)
# (Starting iceweasel with i3’s exec command is important in order to make i3
create a startup notification context, without which the iceweasel window(s)
cannot be matched onto the workspace on which the command was started.)
exec --no-startup-id i3-msg 'workspace 3; workspace 1'
4.17. Automatically starting applications on i3 startup
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
also when restarting i3 you should use the exec_always
keyword. These commands will be run in order.
for details on the special meaning of ; (semicolon)
and , (comma): they chain commands together in i3, so you need to use quoted
strings (as shown in ) if they appear in your command.
exec [--no-startup-id] &command&
exec_always [--no-startup-id] &command&
exec chromium
exec_always ~/my_script.sh
# Execute the terminal emulator urxvt, which is not yet startup-notification aware.
exec --no-startup-id urxvt
The flag --no-startup-id is explained in .
4.18. Automatically putting workspaces on specific screens
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
or when starting (e.g., by default it will use 1 for the first screen, 2 for
the second screen and so on).
workspace &workspace& output &output&
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
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:
workspace 1 output LVDS1
workspace 5 output VGA1
workspace "2: vim" output VGA1
4.19. Changing colors
You can change all colors which i3 uses to draw the window decorations.
&colorclass& &border& &background& &text& &indicator& &child_border&
Where colorclass can be one of:
client.focused
A client which currently has the focus.
client.focused_inactive
A client which is the focused one of its container, but it does not have
the focus at the moment.
client.unfocused
A client which is not the focused one of its container.
client.urgent
A client which has its urgency hint activated.
client.placeholder
Background and text color are used to draw placeholder window contents
(when restoring layouts). Border and indicator are ignored.
client.background
Background color which will be used to paint the background of the
client window on top of which the client will be rendered. Only clients
which do not cover the whole area of this window expose the color. Note
that this colorclass only takes a single color.
Colors are in HTML hex format (#rrggbb), see the following example:
Examples (default colors):
backgr. text
indicator child_border
client.focused
#4c #ffffff #2e9ef4
client.focused_inactive #f676a #ffffff #484e50
client.unfocused
client.urgent
#2f343a #900000 #ffffff #900000
client.placeholder
#c0c0c #ffffff #000000
client.background
Note that for the window decorations, the color around the child window is the
"child_border", and "border" color is only the two thin lines around the
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
single windows within a split container, which are otherwise indistinguishable
from single windows outside of a split container.
4.20. Interprocess communication
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.
The IPC socket is enabled by default and will be created in
/tmp/i3-%u.XXXXXX/ipc-socket.%p where %u is your UNIX username, %p is
the PID of i3 and XXXXXX is a string of random characters from the portable
filename character set (see mkdtemp(3)).
You can override the default path through the environment-variable I3SOCK or
by specifying the ipc-socket directive. This is discouraged, though, since i3
does the right thing by default. If you decide to change it, it is strongly
recommended to set this to a location in your home directory so that no other
user can create that directory.
ipc-socket ~/.i3/i3-ipc.sock
You can then use the i3-msg application to perform any command listed in
the next section.
4.21. Focus follows mouse
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).
focus_follows_mouse yes|no
focus_follows_mouse no
4.22. Mouse warping
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.
With the mouse_warping option, you can control when the mouse cursor should
be warped. none disables warping entirely, whereas output is the default
behavior described above.
mouse_warping output|none
mouse_warping none
4.23. Popups during fullscreen mode
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).
There are three things which are possible to do in this situation:
Display the popup if it belongs to the fullscreen application only. This is
the default and should be reasonable behavior for most users.
Just ignore the popup (don’t map it). This won’t interrupt you while you are
in fullscreen. However, some apps might react badly to this (deadlock until
you go out of fullscreen).
Leave fullscreen mode.
popup_during_fullscreen smart|ignore|leave_fullscreen
popup_during_fullscreen smart
4.24. Focus wrapping
By default, when in a container with several windows or child containers, the
opposite window will be focused when trying to move the focus over the edge of
a container (and there are no other containers in that direction) — the focus
If desired, you can disable this behavior by setting the focus_wrapping
configuration directive to the value no.
When enabled, focus wrapping does not occur by default if there is another
window or container in the specified direction, and focus will instead be set
on that window or container. This is the default behavior so you can navigate
to all your windows without having to use focus parent.
If you want the focus to always wrap and you are aware of using focus
parent to switch to different containers, you can instead set focus_wrapping
to the value force.
focus_wrapping yes|no|force
# Legacy syntax, equivalent to "focus_wrapping force"
force_focus_wrapping yes
# Disable focus wrapping
focus_wrapping no
# Force focus wrapping
focus_wrapping force
4.25. Forcing Xinerama
As explained in-depth in , 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
reconfiguring your screens on the fly (they are read only once on startup and
that’s it).
For people who cannot modify their ~/.xsession to add the
--force-xinerama commandline parameter, a configuration option is provided:
force_xinerama yes|no
force_xinerama yes
Also note that your output names are not descriptive (like HDMI1) when using
Xinerama, instead they are counted up, starting at 0: xinerama-0, xinerama-1, …
4.26. Automatic back-and-forth when switching to the current workspace
This configuration directive enables automatic workspace back_and_forth (see
) when switching to the workspace that is currently focused.
For instance: Assume you are on workspace "1: www" and switch to "2: IM" using
mod+2 because somebody sent you a message. You don’t need to remember where you
came from now, you can just press $mod+2 again to switch back to "1: www".
workspace_auto_back_and_forth yes|no
workspace_auto_back_and_forth yes
4.27. Delaying urgency hint reset on workspace change
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
may make it unnecessarily hard to tell which window originally raised the
In order to prevent this, you can tell i3 to delay resetting the urgency state
by a certain time using the force_display_urgency_hint directive. Setting the
value to 0 disables this feature.
The default is 500ms.
force_display_urgency_hint &timeout& ms
force_display_urgency_hint 500 ms
4.28. Focus on window activation
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 .
focus_on_window_activation smart|urgent|focus|none
The different modes will act as follows:
This is the default behavior. If the window requesting focus is on an active
workspace, it will receive the focus. Otherwise, the urgency hint will be set.
The window will always be marked urgent, but the focus will not be stolen.
The window will always be focused and not be marked urgent.
The window will neither be focused, nor be marked urgent.
4.29. Drawing marks on window decoration
If activated, marks (see ) 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.
show_marks yes|no
show_marks yes
4.30. Line continuation
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.
Commented lines are not continued.
bindsym Mod1+f \
fullscreen toggle
# this line is not continued \
bindsym Mod1+F fullscreen toggle
5. Configuring i3bar
The bar at the bottom of your monitor is drawn by a separate process called
i3bar. Having this part of "the i3 user interface" in a separate process has
several advantages:
It is a modular approach. If you don’t need a workspace bar at all, or if
you prefer a different one (dzen2, xmobar, maybe even gnome-panel?), you can
just remove the i3bar configuration and start your favorite bar instead.
It follows the UNIX philosophy of "Make each program do one thing well".
While i3 manages your windows well, i3bar is good at displaying a bar on
each monitor (unless you configure it otherwise).
It leads to two separate, clean codebases. If you want to understand i3, you
don’t need to bother with the details of i3bar and vice versa.
That said, i3bar is configured in the same configuration file as i3. This is
because it is tightly coupled with i3 (in contrary to i3lock or i3status which
are useful for people using other window managers). Therefore, it makes no
sense to use a different configuration place when we already have a good
configuration infrastructure in place.
Configuring your workspace bar starts with opening a bar block. You can have
multiple bar blocks to use different settings for different outputs (monitors):
status_command i3status
5.1. i3bar command
By default i3 will just pass i3bar and let your shell handle the execution,
searching your $PATH for a correct version.
If you have a different i3bar somewhere or the binary is not in your $PATH you can
tell i3 what to execute.
The specified command will be passed to sh -c, so you can use globbing and
have to have correct quoting etc.
i3bar_command &command&
i3bar_command /home/user/bin/i3bar
5.2. Statusline command
i3bar can run a program and display every line of its stdout output on the
right hand side of the bar. This is useful to display system information like
your current IP address, battery status or date/time.
The specified command will be passed to sh -c, so you can use globbing and
have to have correct quoting etc. Note that for signal handling, depending on
your shell (users of dash(1) are known to be affected), you have to use the
shell’s exec command so that signals are passed to your program, not to the
status_command &command&
status_command i3status --config ~/.i3status.conf
# For dash(1) users who want signal handling to work:
status_command exec ~/.bin/my_status_command
5.3. Display mode
You can either have i3bar be visible permanently at one edge of the screen
(dock mode) or make it show up when you press your modifier key (hide mode).
It is also possible to force i3bar to always stay hidden (invisible
mode). The modifier key can be configured using the modifier option.
The mode option can be changed during runtime through the bar mode command.
On reload the mode will be reverted to its configured value.
The hide mode maximizes screen space that can be used for actual windows. Also,
i3bar sends the SIGSTOP and SIGCONT signals to the statusline process to
save battery power.
Invisible mode allows to permanently maximize screen space, as the bar is never
shown. Thus, you can configure i3bar to not disturb you by popping up because
of an urgency hint or because the modifier key is pressed.
In order to control whether i3bar is hidden or shown in hide mode, there exists
the hidden_state option, which has no effect in dock mode or invisible mode. It
indicates the current hidden_state of the bar: (1) The bar acts like in normal
hide mode, it is hidden and is only unhidden in case of urgency hints or by
pressing the modifier key (hide state), or (2) it is drawn on top of the
currently visible workspace (show state).
Like the mode, the hidden_state can also be controlled through i3, this can be
done by using the bar hidden_state command.
The defau in hide mode, the default modifier is Mod4 (usually
the windows key). The default value for the hidden_state is hide.
mode dock|hide|invisible
hidden_state hide|show
modifier &Modifier&|none
hidden_state hide
modifier Mod1
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.
5.4. Mouse button commands
Specifies a command to run when a button was pressed on i3bar to override the
default behavior. This is useful, e.g., for disabling the scroll wheel action
or running scripts that implement custom behavior for these buttons.
A button is always named button&n&, where 1 to 5 are default buttons as follows and higher
numbers can be special buttons on devices offering more buttons:
Left mouse button.
Middle mouse button.
Right mouse button.
Scroll wheel up.
Scroll wheel down.
Please note that the old wheel_up_cmd and wheel_down_cmd commands are deprecated
and will be removed in a future release. We strongly recommend using the more general
bindsym with button4 and button5 instead.
bindsym [--release] button&n& &command&
# disable clicking on workspace buttons
bindsym button1 nop
# Take a screenshot by right clicking on the bar
bindsym --release button3 exec --no-startup-id import /tmp/latest-screenshot.png
# execute custom script when scrolling downwards
bindsym button5 exec ~/.i3/scripts/custom_wheel_down
5.5. Bar ID
Specifies the bar ID for the configured bar instance. If this option is missing,
the ID is set to bar-x, where x corresponds to the position of the embedding
bar block in the config file (bar-0, bar-1, …).
id &bar_id&
5.6. Position
This option determines in which edge of the screen i3bar should show up.
The default is bottom.
position top|bottom
position top
5.7. Output(s)
You can restrict i3bar to one or more outputs (monitors). The default is to
handle all outputs. Restricting the outputs is useful for using different
options for different outputs by using multiple bar blocks.
To make a particular i3bar instance handle multiple outputs, specify the output
directive multiple times.
output primary|&output&
# big monitor: everything
# The display is connected either via HDMI or via DisplayPort
output HDMI2
output DP2
status_command i3status
# laptop monitor: bright colors and i3status with less modules.
output LVDS1
status_command i3status --config ~/.i3status-small.conf
background #000000
statusline #ffffff
# show bar on the primary monitor and on HDMI2
output primary
output HDMI2
status_command i3status
Note that you might not have a primary output configured yet. To do so, run:
xrandr --output &output& --primary
5.8. Tray output
i3bar by default provides a system tray area where programs such as
NetworkManager, VLC, Pidgin, etc. can place little icons.
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
tray_output none|primary|&output&
# disable system tray
tray_output none
# show tray icons on the primary monitor
tray_output primary
# show tray icons on the big monitor
tray_output HDMI2
Note that you might not have a primary output configured yet. To do so, run:
xrandr --output &output& --primary
Note that when you use multiple bar configuration blocks, either specify
tray_output primary in all of them or explicitly specify tray_output none
in bars which should not display the tray, otherwise the different instances
might race each other in trying to display tray icons.
5.9. Tray padding
The tray is shown on the right-hand side of the bar. By default, a padding of 2
pixels is used for the upper, lower and right-hand side of the tray area and
between the individual icons.
tray_padding &px& [px]
# Obey Fitts's law
tray_padding 0
5.10. Font
Specifies the font to be used in the bar. See .
font &font&
font -misc-fixed-medium-r-normal--13-120-75-75-C-70-iso10646-1
font pango:DejaVu Sans Mono 10
5.11. Custom separator symbol
Specifies a custom symbol to be used for the separator as opposed to the vertical,
one pixel thick separator.
separator_symbol &symbol&
separator_symbol ":|:"
5.12. Workspace buttons
Specifies whether workspace buttons should be shown or not. This is useful if
you want to display a statusline-only bar containing additional information.
The default is to show workspace buttons.
workspace_buttons yes|no
workspace_buttons no
5.13. Strip workspace numbers
Specifies whether workspace numbers should be displayed within the workspace
buttons. This is useful if you want to have a named workspace that stays in
order on the bar according to its number without displaying the number prefix.
When strip_workspace_numbers is set to yes, any workspace that has a name of
the form "[n]:[NAME]" will display only the name. You could use this, for
instance, to display Roman numerals rather than digits by naming your
workspaces to "1:I", "2:II", "3:III", "4:IV", …
The default is to display the full name within the workspace button.
strip_workspace_numbers yes|no
strip_workspace_numbers yes
5.14. Binding Mode indicator
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. See
to learn what
modes are and how to use them.
The default is to show the mode indicator.
binding_mode_indicator yes|no
binding_mode_indicator no
5.15. Colors
As with i3, colors are in HTML hex format (#rrggbb). The following colors can
be configured at the moment:
background
Background color of the bar.
statusline
Text color to be used for the statusline.
Text color to be used for the separator.
focused_background
Background color of the bar on the currently focused monitor output. If
not used, the color will be taken from background.
focused_statusline
Text color to be used for the statusline on the currently focused
monitor output. If not used, the color will be taken from statusline.
focused_separator
Text color to be used for the separator on the currently focused
monitor output. If not used, the color will be taken from separator.
focused_workspace
Border, background and text color for a workspace button when the workspace
has focus.
active_workspace
Border, background and text color for a workspace button when the workspace
is active (visible) on some output, but the focus is on another one.
You can only tell this apart from the focused workspace when you are
using multiple monitors.
inactive_workspace
Border, background and text color for a workspace button when the workspace
does not have focus and is not active (visible) on any output. This
will be the case for most workspaces.
urgent_workspace
Border, background and text color for a workspace button when the workspace
contains a window with the urgency hint set.
binding_mode
Border, background and text color for the binding mode indicator. If not used,
the colors will be taken from urgent_workspace.
background &color&
statusline &color&
separator &color&
&colorclass& &border& &background& &text&
Example (default colors):
background #000000
statusline #ffffff
separator #666666
focused_workspace
#4c #ffffff
active_workspace
#f676a #ffffff
inactive_workspace #
urgent_workspace
#2f343a #900000 #ffffff
binding_mode
#2f343a #900000 #ffffff
6. List of commands
Commands are what you bind to specific keypresses. You can also issue commands
at runtime without pressing a key by using the IPC interface. An easy way to
do this is to use the i3-msg utility:
# execute this on your shell to make the current container borderless
i3-msg border none
Commands can be chained by using ; (a semicolon). So, to move a window to a
specific workspace and immediately switch to that workspace, you can configure
the following keybinding:
bindsym $mod+x move container to workspace 3; workspace 3
Furthermore, you can change the scope of a command - that is, which containers
should be affected by that command, by using various criteria. The criteria
are specified before any command in a pair of square brackets and are separated
When using multiple commands, separate them by using a , (a comma) instead of
a semicolon. Criteria apply only until the next semicolon, so if you use a
semicolon to separate commands, only the first one will be executed for the
matched window(s).
# if you want to kill all windows which have the class Firefox, use:
bindsym $mod+x [class="Firefox"] kill
# same thing, but case-insensitive
bindsym $mod+x [class="(?i)firefox"] kill
# kill only the About dialog from Firefox
bindsym $mod+x [class="Firefox" window_role="About"] kill
# enable floating mode and move container to workspace 4
for_window [class="^evil-app$"] floating enable, move container to workspace 4
# move all floating windows to the scratchpad
bindsym $mod+x [floating] move scratchpad
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
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
instance as the currently focused window.
window_role
Compares the window role (WM_WINDOW_ROLE). Use the special value
__focused__ to match all windows having the same window role as the
currently focused window.
window_type
Compare the window type (_NET_WM_WINDOW_TYPE). Possible values are
normal, dialog, utility, toolbar, splash, menu, dropdown_menu,
popup_menu, tooltip and notification.
Compares the X11 window ID, which you can get via xwininfo for example.
Compares the X11 window title (_NET_WM_NAME or WM_NAME as fallback).
Use the special value __focused__ to match all windows having the
same window title as the currently focused window.
Compares the urgent state of the window. Can be "latest" or "oldest".
Matches the latest or oldest urgent window, respectively.
(The following aliases are also available: newest, last, recent, first)
Compares the workspace name of the workspace the window belongs to. Use
the special value __focused__ to match all windows in the currently
focused workspace.
Compares the marks set for this container, see . A
match is made if any of the container’s marks matches the specified
Compares the i3-internal container ID, which you can get via the IPC
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.
The criteria class, instance, role, title, workspace and mark are
actually regular expressions (PCRE). See pcresyntax(3) or perldoc perlre for
information on how to use them.
6.1. Executing applications (exec)
What good is a window manager if you can’t actually start any applications?
The exec command starts an application by passing the command you specify to a
shell. This implies that you can use globbing (wildcards) and programs will be
searched in your $PATH.
for details on the special meaning of ; (semicolon)
and , (comma): they chain commands together in i3, so you need to use quoted
strings (as shown in ) if they appear in your command.
exec [--no-startup-id] &command&
# Start the GIMP
bindsym $mod+g exec gimp
# Start the terminal emulator urxvt which is not yet startup-notification-aware
bindsym $mod+Return exec --no-startup-id urxvt
The --no-startup-id parameter disables startup-notification support for this
particular exec command. With startup-notification, i3 can make sure that a
window appears on the workspace on which you used the exec command. Also, it
will change the X11 cursor to watch (a clock) while the application is
launching. So, if an application is not startup-notification aware (most GTK
and Qt using applications seem to be, though), you will end up with a watch
cursor for 60 seconds.
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:
# 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:
# Execute a command with a comma, semicolon and internal quotes
bindsym $mod+p exec "notify-send \\"Hello, i3; from $USER\\""
6.2. Splitting containers
The split command makes the current window a split container. Split containers
can contain multiple windows. Depending on the layout of the split container,
new windows get placed to the right of the current one (splith) or new windows
get placed below the current one (splitv).
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).
The toggle option will toggle the orientation of the split container if it
contains a single window. Otherwise it makes the current window a split
container with opposite orientation compared to the parent container.
Use layout toggle split to change the layout of any split container from
splitv to splith or vice-versa. You can also define a custom sequence of layouts
to cycle through with layout toggle, see .
split vertical|horizontal|toggle
bindsym $mod+v split vertical
bindsym $mod+h split horizontal
bindsym $mod+t split toggle
6.3. Manipulating layout
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
fullscreen toggle (or fullscreen toggle global).
Likewise, to make the current window floating (or tiling again) use floating
enable respectively floating disable (or floating toggle):
layout default|tabbed|stacking|splitv|splith
layout toggle [split|all]
layout toggle [split|tabbed|stacking|splitv|splith] [split|tabbed|stacking|splitv|splith]…
bindsym $mod+s layout stacking
bindsym $mod+l layout toggle split
bindsym $mod+w layout tabbed
# Toggle between stacking/tabbed/split:
bindsym $mod+x layout toggle
# Toggle between stacking/tabbed/splith/splitv:
bindsym $mod+x layout toggle all
# Toggle between stacking/tabbed/splith:
bindsym $mod+x layout toggle stacking tabbed splith
# Toggle between splitv/tabbed
bindsym $mod+x layout toggle splitv tabbed
# Toggle between last split layout/tabbed/stacking
bindsym $mod+x layout toggle split tabbed stacking
# Toggle fullscreen
bindsym $mod+f fullscreen toggle
# Toggle floating/tiling
bindsym $mod+t floating toggle
6.4. Focusing containers
To change focus, you can use the focus command. The following options are
available:
&criteria&
Sets focus to the conta