Codebase list i3-gaps / 6a18069
userguide: may → might in most places (thanks Bruce) Quoting https://www.freelists.org/post/i3-discuss/Grammar-check-in-the-doc May inquires only into permission. Might inquires into probability. Can inquires into possibility. Will/shall inquires into certainty. Michael Stapelberg 3 years ago
1 changed file(s) with 14 addition(s) and 14 deletion(s). Raw diff Collapse all Expand all
+14
-14
docs/userguide less more
5353 image:two_terminals.png[Two terminals]
5454
5555 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
5757 for these keys (in +vi+, the keys are shifted to the left by one for
5858 compatibility with most keyboard layouts). Therefore, +$mod+j+ is left, +$mod+k+
5959 is down, +$mod+l+ is up and `$mod+;` is right. So, to switch between the
923923 If your X server supports RandR 1.5 or newer, i3 will use RandR monitor objects
924924 instead of output objects. Run +xrandr --listmonitors+ to see a list. Usually,
925925 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
927927 monitor or the output in i3's configuration. For example, the Dell UP2414Q uses
928928 two scalers internally, so its output names might be “DP1” and “DP2”, but the
929929 monitor name is “Dell UP2414Q”.
10651065 === Popups during fullscreen mode
10661066
10671067 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
10691069 that they are in fullscreen mode (they do not check the corresponding hint).
10701070 There are three things which are possible to do in this situation:
10711071
11751175 === Delaying urgency hint reset on workspace change
11761176
11771177 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
11791179 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
11811181 event.
11821182
11831183 In order to prevent this, you can tell i3 to delay resetting the urgency state
12001200 === Focus on window activation
12011201
12021202 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
12061206 from being focused, see <<no_focus>>.
12071207
12081208 *Syntax*:
16481648
16491649 By default, the width a workspace button is determined by the width of the text
16501650 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.
16521652
16531653 This option specifies the minimum width for workspace buttons. If the name of
16541654 a workspace is too short to cover the button, an additional padding is added on
16581658
16591659 The setting also applies to the current binding mode indicator.
16601660
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
16621662 into more pixels on HiDPI displays.
16631663
16641664 *Syntax*:
24702470 === Jumping to specific windows
24712471
24722472 Often when in a multi-monitor environment, you want to quickly jump to a
2473 specific window. For example, while working on workspace 3 you may want to
2473 specific window. For example, while working on workspace 3 you might want to
24742474 jump to your mail client to email your boss that you’ve achieved some
24752475 important goal. Instead of figuring out how to navigate to your mail client,
24762476 it would be more convenient to have a shortcut. You can use the +focus+ command
25052505 can also prefix this command and display a custom prompt for the input dialog.
25062506
25072507 The additional +--toggle+ option will remove the mark if the window already has
2508 this mark or add it otherwise. Note that you may need to use this in
2508 this mark or add it otherwise. Note that you might need to use this in
25092509 combination with +--add+ (see below) as any other marks will otherwise be
25102510 removed.
25112511
26042604 to the normal and pixel styles.
26052605
26062606 Note that "pixel" refers to logical pixel. On HiDPI displays, a logical pixel
2607 may be represented by multiple physical pixels, so +pixel 1+ might not
2607 is represented by multiple physical pixels, so +pixel 1+ might not
26082608 necessarily translate into a single pixel row wide border.
26092609
26102610 *Syntax*:
28672867
28682868 === Interesting configuration for multi-monitor environments
28692869
2870 There are several things to configure in i3 which may be interesting if you
2870 There are several things to configure in i3 which might be interesting if you
28712871 have more than one monitor:
28722872
28732873 1. You can specify which workspace should be put on which screen. This