53 | 53 |
image:two_terminals.png[Two terminals]
|
54 | 54 |
|
55 | 55 |
To move the focus between the two terminals, you can use the direction keys
|
56 | |
which you may know from the editor +vi+. However, in i3, your homerow is used
|
|
56 |
which you might know from the editor +vi+. However, in i3, your homerow is used
|
57 | 57 |
for these keys (in +vi+, the keys are shifted to the left by one for
|
58 | 58 |
compatibility with most keyboard layouts). Therefore, +$mod+j+ is left, +$mod+k+
|
59 | 59 |
is down, +$mod+l+ is up and `$mod+;` is right. So, to switch between the
|
|
923 | 923 |
If your X server supports RandR 1.5 or newer, i3 will use RandR monitor objects
|
924 | 924 |
instead of output objects. Run +xrandr --listmonitors+ to see a list. Usually,
|
925 | 925 |
a monitor object contains exactly one output, and has the same name as the
|
926 | |
output; but should that not be the case, you may specify the name of either the
|
|
926 |
output; but should that not be the case, you can specify the name of either the
|
927 | 927 |
monitor or the output in i3's configuration. For example, the Dell UP2414Q uses
|
928 | 928 |
two scalers internally, so its output names might be “DP1” and “DP2”, but the
|
929 | 929 |
monitor name is “Dell UP2414Q”.
|
|
1065 | 1065 |
=== Popups during fullscreen mode
|
1066 | 1066 |
|
1067 | 1067 |
When you are in fullscreen mode, some applications still open popup windows
|
1068 | |
(take Xpdf for example). This is because these applications may not be aware
|
|
1068 |
(take Xpdf for example). This is because these applications might not be aware
|
1069 | 1069 |
that they are in fullscreen mode (they do not check the corresponding hint).
|
1070 | 1070 |
There are three things which are possible to do in this situation:
|
1071 | 1071 |
|
|
1175 | 1175 |
=== Delaying urgency hint reset on workspace change
|
1176 | 1176 |
|
1177 | 1177 |
If an application on another workspace sets an urgency hint, switching to this
|
1178 | |
workspace may lead to immediate focus of the application, which also means the
|
|
1178 |
workspace might lead to immediate focus of the application, which also means the
|
1179 | 1179 |
window decoration color would be immediately reset to +client.focused+. This
|
1180 | |
may make it unnecessarily hard to tell which window originally raised the
|
|
1180 |
might make it unnecessarily hard to tell which window originally raised the
|
1181 | 1181 |
event.
|
1182 | 1182 |
|
1183 | 1183 |
In order to prevent this, you can tell i3 to delay resetting the urgency state
|
|
1200 | 1200 |
=== Focus on window activation
|
1201 | 1201 |
|
1202 | 1202 |
If a window is activated, e.g., via +google-chrome www.google.com+, it may request
|
1203 | |
to take focus. Since this may not be preferable, different reactions can be configured.
|
1204 | |
|
1205 | |
Note that this may not affect windows that are being opened. To prevent new windows
|
|
1203 |
to take focus. Since this might not be preferable, different reactions can be configured.
|
|
1204 |
|
|
1205 |
Note that this might not affect windows that are being opened. To prevent new windows
|
1206 | 1206 |
from being focused, see <<no_focus>>.
|
1207 | 1207 |
|
1208 | 1208 |
*Syntax*:
|
|
1648 | 1648 |
|
1649 | 1649 |
By default, the width a workspace button is determined by the width of the text
|
1650 | 1650 |
showing the workspace name. If the name is too short (say, one letter), then the
|
1651 | |
workspace button may look too small.
|
|
1651 |
workspace button might look too small.
|
1652 | 1652 |
|
1653 | 1653 |
This option specifies the minimum width for workspace buttons. If the name of
|
1654 | 1654 |
a workspace is too short to cover the button, an additional padding is added on
|
|
1658 | 1658 |
|
1659 | 1659 |
The setting also applies to the current binding mode indicator.
|
1660 | 1660 |
|
1661 | |
Note that the specified pixels refer to logical pixels, which may translate
|
|
1661 |
Note that the specified pixels refer to logical pixels, which might translate
|
1662 | 1662 |
into more pixels on HiDPI displays.
|
1663 | 1663 |
|
1664 | 1664 |
*Syntax*:
|
|
2487 | 2487 |
=== Jumping to specific windows
|
2488 | 2488 |
|
2489 | 2489 |
Often when in a multi-monitor environment, you want to quickly jump to a
|
2490 | |
specific window. For example, while working on workspace 3 you may want to
|
|
2490 |
specific window. For example, while working on workspace 3 you might want to
|
2491 | 2491 |
jump to your mail client to email your boss that you’ve achieved some
|
2492 | 2492 |
important goal. Instead of figuring out how to navigate to your mail client,
|
2493 | 2493 |
it would be more convenient to have a shortcut. You can use the +focus+ command
|
|
2522 | 2522 |
can also prefix this command and display a custom prompt for the input dialog.
|
2523 | 2523 |
|
2524 | 2524 |
The additional +--toggle+ option will remove the mark if the window already has
|
2525 | |
this mark or add it otherwise. Note that you may need to use this in
|
|
2525 |
this mark or add it otherwise. Note that you might need to use this in
|
2526 | 2526 |
combination with +--add+ (see below) as any other marks will otherwise be
|
2527 | 2527 |
removed.
|
2528 | 2528 |
|
|
2621 | 2621 |
to the normal and pixel styles.
|
2622 | 2622 |
|
2623 | 2623 |
Note that "pixel" refers to logical pixel. On HiDPI displays, a logical pixel
|
2624 | |
may be represented by multiple physical pixels, so +pixel 1+ might not
|
|
2624 |
is represented by multiple physical pixels, so +pixel 1+ might not
|
2625 | 2625 |
necessarily translate into a single pixel row wide border.
|
2626 | 2626 |
|
2627 | 2627 |
*Syntax*:
|
|
2884 | 2884 |
|
2885 | 2885 |
=== Interesting configuration for multi-monitor environments
|
2886 | 2886 |
|
2887 | |
There are several things to configure in i3 which may be interesting if you
|
|
2887 |
There are several things to configure in i3 which might be interesting if you
|
2888 | 2888 |
have more than one monitor:
|
2889 | 2889 |
|
2890 | 2890 |
1. You can specify which workspace should be put on which screen. This
|